Servoy 2020.06 release candidate 2

Announcements
1

We are pleased to announce the availability of Servoy 2020.06 release candidate 2 (release number 3581)

See rc1 for info about the first rc.

If you update from RC1 to RC2 through the update site then this fix:SVY-15100 will not be seen.
That is only visible in a fresh install or an update from 2020.03

For Windows the installer: exe
and for the MacOSX we have an native dmg
for linux it is still the tar.gz

For windows we also still have just the zip

The all in one installer is not created anymore.

An installation (coming from the normal installer or from a platform specific archive) is shipping with with a Java VM (Java 14.0.1)

So for the platform specific archives you don’t need to install or java have on your system.

The developer can be updated by the http://download.servoy.com/developer/la … ecandidate update site url.
This is in our “latest” release stream (03,06,09,12) if you want to stick the the lts release then disable that releasecandidate url and stick to the urls with “lts” in the name
If you update to this release you have to do a new install of 201903_lts to go back to an the LTS release branch

An LTS release based on 2020.03 (so 2020.03.1_LTS) will be released shortly after the final of 2020.06, this release will have many of the fixes that also 2020.06, but not the feature changes and improvements.

If you do update from a bit older version (then 09) then it could be that there is a left over driver in the drivers dir that has 0 bytes. Make sure you delete that one, and if you make war exports from this make sure you don’t include this 0 byte driver jar. That will result in errors when deploying.

See whats new for the global changes

See the issues list for a complete overview of all the cases including the update for this rc2 release

We will release also new component and service packages shortly, they are still work in progress because of the added feature and refactoring we did on them for the 2020.06 release (like showing them by category)

2

Anxiously awaiting 2020.03.1_LTS. The broken OAuth redirection with war deployment is holding up a customers Office365 integration.
Personally, I think the LTS releases should happen before the feature releases.

3

No that is a bad idea.
LTS releases should have fixes that should already be out there for a while (like tested in 06 and later in 09 and 12)

its kind of exactly what https://www.jenkins.io/download/ does… LTS is split of of a much older “latest” release with back ported fixes of later releases.

4

Yes, but they do releases much more often. They have weekly release builds, and major releases once a month or so. So its usually under 30 days to get a fix for a major bug on LTS. With Servoy’s quarterly release cycle, its almost 4 months to get a fix to LTS.

5

and having an lts release that last a month is a bit weir
But anyway a lts release for us will mean that most fixes in there are tested by a quarterly release to make the lts release as stable as possible

If you really want to get already the build that would have been the lts release if we released it you can get that update zip if you want: https://build.servoy.com/latest/servoy_ … update.zip

6

jcompagner:
If you really want to get already the build that would have been the lts release if we released it you can get that update zip if you want: https://build.servoy.com/latest/servoy_ … update.zip

That works for me. thanks.

7

We’re happy to invite you to our tech webinar series next week , with two short webinars to cover the 2020.06 launch. Come explore the ins-and-outs of the latest release, including the latest updates to the platform and its suite of extension packages.

Part 1 - Tuesday: Release Overview

We’ll review the many enhancements that ship with Servoy 2020.06 and cover the ins-and-outs of the update process. This webinar is for Servoy experts and newbies alike. You will learn

Key enhancements and changes to be aware of
How to handle the update process

Part 2 - Thursday: Extension Packages Overview

Next we will go over all the updates to Servoy’s extension packages, including Web Components, plugins and modules.

Register Here

All webinars:
8am Los Angeles (PST)
11am New York (EST)
16h Amsterdam (CET)

8

A quick correction, the CET time for the webinars is 17h
Sorry for the confusion

9

Part 2 - Thursday June 25 - NG Grids Update

Part 2 of this webinar series covers the many enhancements to Servoy’s NG Grid components. This powerful, feature-rich component package is used in nearly every Servoy project. So it makes sense that it deserves its own update webinar. Whether you’re a grid expert or just getting started, there’s a lot to learn in this webinar.

Register Here

All webinars:
8am Los Angeles (PST)
11am New York (EST)
17h Amsterdam (CET)

If you missed Part 1 of this series, you can stream it from our archives

10

When are you going to announce the availability of Servoy 2020.06 final release in https://forum.servoy.com/viewforum.php?f=16?

Thanks!
JC

11

very likely tomorrow afternoon or the morning after that.

12

Part 1 & 2 recordings of our webinar launch series are both posted and can be viewed on the tech webinar archives:

https://servoy.com/webinars/tech-series/

13

Hi,
further to webinars about 2020.06 and the move to ‘deprecate’ usage of ‘Servoy Default’ components, I asked if there would be a way to show which forms in a solution had them easily and it was suggested, as there was no option for that, to search in Workspace.
Having just played around with a solution that only had ‘NG’ compliant forms, I purposely added a ‘Servoy Default’ component to a form and looked at it in a text editor and there is nothing to show it was from the default set, other than possibly the ‘type ID’…
Obviously there is something that new version of Servoy is doing/seeing in the form to show/hide the default components on a form in the editor, so could you advise what that is, or somehow expose that so we can easily upgrade our solutions to be ‘pure’ (& lightweight) for NG??
Thanks
Rafi

14

Hi Rafi,

I guess you would be searching for something that doesn’t exist “typeName” in those forms.
I wonder why you ask? What you would do with that info? Are you looking to automate an upgrade?

I guess you could do something with solution model if you made some assumptions.
You could loop over forms–>components and check

JSComponent instanceof JSWebComponent

If it hits false, then you have a form with a legacy component.

15

sean:
Hi Rafi,
I guess you would be searching for something that doesn’t exist “typeName” in those forms.

I might try that…

I wonder why you ask? What you would do with that info? Are you looking to automate an upgrade?
I guess you could do something with solution model if you made some assumptions.
You could loop over forms–>components and check

JSComponent instanceof JSWebComponent

If it hits false, then you have a form with a legacy component.

…or that
I was just thinking that it might be nice to clean up a solution that is totally NG client to only use the correct components, so it is as optimised for the web as possible?
(or maybe a new colour/style icon for form in ‘Solution Explorer’ ?? )
Thanks

16

Hi Rafi,

Well if you are starting “clean”, then it will already be using only modern components, and the legacy will not be avaialable.
It’s more a question about migration; taking an older solution and dealing with legacy components.
In that case, you can go form-by-form.

17

sean:
Hi Rafi,
Well if you are starting “clean”, then it will already be using only modern components, and the legacy will not be avaialable.
It’s more a question about migration; taking an older solution and dealing with legacy components.
In that case, you can go form-by-form.

I would, of course, keep new solutions ‘clean’, but it was really for taking my ‘older’ NG solutions & cleaning them up…
I guess I will do it form by form ;-)
Thx

18

There is no quick fix for this (especially for grids / legacy “table-view” forms)
However, it’s conceivable that you could automate some of it with solution model if you make some assumptions. For example, if you created a mapping from legacy to modern component types; button:button, field:[text-box,type-ahead,combobox, etc(depending on input type)]
…after which, you call ServoyDeveloper.save() then persist your changes (only after you are satisfied with the runtime result)

That could get you a good part of the way…

19

Thanks Sean