Servoy 8.4 release candidate 1

[jcompagner]

We are pleased to announce the availability of Servoy 8.4 release candidate 1 (release number 3400)

This version is available through the jar or exe
The update site is: http://download.servoy.com/developer/8x ... candidate/

Release notes of this release 8.4 whats new

issues fixed see our wiki: 8.4 RC1 release notes

After this we plan to do a RC2 before the end of this month and a final release in the beginning of January 2019

8.4 will succeed the 833 release, so there will not be a 834 release.

Edit: Also released 2 packages that are showing 2 new features of 84:

12grid 1.2.0: for the new css positioned container in a responsive form
Servoy Extra 1.7.0: Now has the ListFormComponent component for repeating a form components ui for the foundsets records.

[sean]

Thanks Johan! To celebrate, we'll be doing a 3-part webinar series next week to introduce the latest features.
This release focuses on form design, styling and data access. You don't want to miss it.

Register today for this mini-series.

Build better UIs Part 1
New in 8.4, Servoy’s “Simple Layout” makes positioning components more powerful, yet remains simple to use. Get the dynamic UI you want with less effort.

Build better UIs Part 2:
Styling your application just got easier. Servoy 8.4 ships with “CSS-Less” styling ability.
This means that whether you are a CSS pro, or you don’t want to know anything about CSS, in Servoy 8.4, you can implement the style you want with less effort.

Performance Enhancements
Servoy 8.4 comes with enhancements to allow some data screens to become even faster. The new “View Foundset” allows developers to optimize data access for complex data structures.

[Peter de Groot]

Wow,great...

[mboegem]

Nice, looking forward to the webinars next week!

I like your choice of words by the way...

"CSS-Less" styling... implement the style you want with less effort

[alex1544084874]

Nice work!

Looking forward to the webinars!

Quick question, will it be possible to update from RC1 to RC2 and final release without reinstalling 8.4?

[jcompagner]

Quick question, will it be possible to update from RC1 to RC2 and final release without reinstalling 8.4?

yes that should be fine

even updating from 8.3.x to an 8.4rc (or final) should work

But do remember that some stuff like log configuration is changed then, and the config is not in the servoy.properties file anymore

[rafig]

I'm trying out this new release candidate, but seem to be having a problem.
If I choose to 'extend' a form, or create a new sub-form from a form, I cannot access any of the methods in that 'base' form for linking to actions or buttons etc.
The list of sub/base methods appears on the lower left side panel (Solution Explorer?), but are not available in method picker under 'Form' node (actual form methods are though, as are scope methods)
Has anyone else experienced this? (or is this know about, because it would seem to be a rather big bug to have gotten thru QA )
Thanks
Rafi

[cp]

So - does anyone else have issues running 8.4 rc1?

I've tried - in vain - to update, clean install - on OSX and Win - Java 8 and 11 - but always getting blank views and errors like:

Could not create the view: com.servoy.eclipse.ui.views.SolutionExplorerView

Could not create the view: com.servoy.eclipse.ui.views.solutionexplorer.FormHierarchyView

Am I missing something?

[jcompagner]

that should all work fine
so you have the same issues on Windows and OSX and also using different vm's on both?

I think something else goes wrong under the hood very quickly, what error do you have in the developer/eclipse log?
(workspace/.metadata/.log)

[cp]

Hi Johan,

In the .log file i have a lot of loggings. Mainly entries like:

!ENTRY org.eclipse.core.runtime 4 0 2018-12-12 13:58:18.525
!MESSAGE Invalid input url:platform:/plugin/org.tigris.subversion.subclipse.ui/icons/full/cview16/annotate_view.gif
!STACK 0
java.io.IOException: Unable to resolve plug-in "platform:/plugin/org.tigris.subversion.subclipse.ui/icons/full/cview16/annotate_view.gif".

OR

!ENTRY org.eclipse.jface 4 0 2018-12-12 13:35:38.737
!MESSAGE Unable to resolve plug-in "platform:/plugin/com.servoy.eclipse.profiler/icons/profiler_view.png".
!STACK 0
java.io.IOException: Unable to resolve plug-in "platform:/plugin/com.servoy.eclipse.profiler/icons/profiler_view.png"

I don't know if you can read anything from this - but could send the files?

And yes - same issues. I cannot rule out that something from one installation have not sneaked its way to another...

[jcompagner]

do send the files to me, (can be by private message)
but it see subversion for example a clean install shouldn't have that
So a clean install with in a new directory and in a new workspace (so don't use an existing one)

[rafig]

Johan
I did a clean (mac) install and new workspace
What about my problem? (Form inheritance methods)

[jcompagner]

Johan
I did a clean (mac) install and new workspace
What about my problem? (Form inheritance methods)

I was just told that that is a bug that is already fixed
Problem is that i guess you have a base form and then a sub form (so 2 forms)
that specific setup had a problem because we have a new feature that you really can pick from a super form and also create directly in the base a method if you want.
So it is now differently shown..

[cp]

do send the files to me, (can be by private message)
but it see subversion for example a clean install shouldn't have that
So a clean install with in a new directory and in a new workspace (so don't use an existing one)

Hi Johan,
Took you up on that and did a clean-clean install (new directory) - and it seems to work.
Thanks though.

/Claus

[rafig]

Johan
I did a clean (mac) install and new workspace
What about my problem? (Form inheritance methods)

I was just told that that is a bug that is already fixed
Problem is that i guess you have a base form and then a sub form (so 2 forms)
that specific setup had a problem because we have a new feature that you really can pick from a super form and also create directly in the base a method if you want.
So it is now differently shown..

When will the bug fix version be available?
In the mean time, is there a simple work-around?