Page 1 of 1

Servoy 8.3 release candidate 1

PostPosted: Tue Apr 10, 2018 3:26 pm
by jcompagner
We are pleased to announce the availability of Servoy 8.3 release candidate (releasenumber 3201)

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


issues fixed see our wiki: 8.3 RC1 release notes

or read the 8.3 Whats new page

8.3 will superseed 8.2.3 when released. So there will not be a 8.2.4

We will release updated web packages shortly, first also a version still compatible with 8.2.3, after that some packages will be 8.3 only

known regression: https://support.servoy.com/browse/SVY-11603 (if you see suddenly a lot more "variable 'x' hides a property")

Re: Servoy 8.3 release candidate 1

PostPosted: Thu Apr 12, 2018 11:08 am
by Harjo
the wiki, about this release, also points to a link that does not work (or not public)

https://wiki.servoy.com/display/DOCS/Ja ... martClient

Re: Servoy 8.3 release candidate 1

PostPosted: Fri Apr 13, 2018 12:21 pm
by sjoerd1337768711
I'm testing version 8.3 RC.

First impression is that everything is working OK.

There is something changed with override methods.
Hundreds of warnings: "Reference to undeclared variable or property _super".

Previous versions of Servoy:
function onShowForm_ready(_firstShow, _event) {
return _super.onShowForm_ready(_firstShow, _event)
}


Version 8.3 RC is not adding the code "return _super.onShowForm_ready(_firstShow, _event)" when overriding a method from parent_form.
/**
* @param {Boolean} _firstShow
* @param {JSEvent} _event
* @override
*
* @properties={typeid:24,uuid:"5F9246C7-0F4C-4547-83D7-3ECCADF35894"}
*/
function onShowForm_ready(_firstShow, _event) {
application.output('test')
}


I see the extra @override in JSDOC.
First child-method is executed and then parent-method.

Is this a bug in 8.3 RC?

Re: Servoy 8.3 release candidate 1

PostPosted: Fri Apr 13, 2018 12:39 pm
by patrick
Regarding the first problem of all those warnings: I ran into that as well and it is fixed already. Not sure another RC will be created, but it should be fine with any next release.