Servoy 2022.3.1

Announcements
1

We are pleased to announce the availability of Servoy 2022.3.1 (release number 3743)

Look at the whats new for more info about the 2022.03.x changes
For all fixes and updates in this release see issues list.

This version is available through the the download site

We ship only installers, so for windows an exe file and for osx a dmg, for linux we have a archive tar file.

The full installers/archives are only for new installs, never use that to update/overwrite an existing install, existing installations should always be updated through the “check for updates”.
This release can be updated by using the “latest” url: http://download.servoy.com/developer/latest/ (when you come from 2019.03 or higher)
This release is build on Eclipse 2021.12 (4.22)

If check for updates says there are no updates, then it could be a caching problem of eclipse, please restart the developer once and try again.

We ship a java with our installation (Java 17.0.3). So there doesn’t need to be a java installed on the system anymore.
Also with a next update, we can update the java version with it so no need to keep it up to date yourself anymore.

This is a release in our quarterly release cycle, but this one will be promoted to LTS (2022.3.2 LTS)
if you want to stay on the LTS path you need to stick to 2021.03.1 LTS and enabled only the lts update site.
This release will be promoted to an LTS release later this year (so for example 2022.3.1 LTS)

2

This release was also demonstrated at ServoyWorld we used this component: https://github.com/Servoy/servoyworld_component to explain how to convert NG1 Component to a NG Titanium Component.

That git repo has a master which is just the NG1 component and a TiNG branch which is the fully converted one.

3

Important notice for users of the svyExcelUtils: Servoy has updated some libraries that also requires the POI (extra) libraries to be updated.

I have uploaded a new collection of additional libraries to the Wiki here: https://github.com/Servoy/svyUtils/wiki … 1-or-later

4

The list of issues fixed includes SVYX-428 (Jasper reports localization). That ticket says that it will be fixed in the next release of Jasper Reports but there has not been a new release with 2022.3.1 - is this still to come?

Thanks
Steve

5

SVYX-428 is fixed in the latest jasper plugin (2022.3_6.19.1) that you can use with Servoy 2022.3.1 (but also should work fine with Servoy 2022.3.0)

6

That’s great - thanks for the clarification.

7

sorry, just re-checked, for the SVYX-428 fix you really need to use servoy 2022.3.1 (the latest jasper plugin 2022.3_6.19.1 works also with servoy 2022.3.0, just that particular fix needs 2022.3.1)

8

jcompagner:
This release was also demonstrated at ServoyWorld we used this component: https://github.com/Servoy/servoyworld_component to explain how to convert NG1 Component to a NG Titanium Component.

That git repo has a master which is just the NG1 component and a TiNG branch which is the fully converted one.

In the instructions that are given in the README.MD for the NG2 component (only visible when you switch to the ting branch - took me a while to realise this!) it says:

After the conversion you should first do

"npm install"

in the root of the component package (which holds the package.json file)

Can you clarify which directory this is as when I convert the NG1 component using the Upgrade option on the right click I end up with a package.json in the root of the original NG1 component and also one in the /project subdirectory which I assume is the root of the NG2 components in the package (also the case with the ting branch of the example component). Do I run the “npm install” in both?

Thanks
Steve

9

no never run npm install in the projects dir (that package.json is purely for packaging the component)

the root is for developing the component.

10

Thanks for the swift response.

Will carry on with my experimenting!

11

OK - got my first component converted and have the following questions/observations:

  1. My component has a text property that is used with an i18N string. In the NG1 editor the string is shown with the i18N value, but in the NG2 editor it shows only the i18N key (runtime works fine). I have confirmed that this is the same behaviour with the standard Servoy label. Should I report this as an issue with the NG2 editor?
  2. Normal practice with angular component development seems to be to use encapsulated CSS within the component itself by using the styleUrls directive:
@Component({
    selector: 'mycomponents-sample,
    templateUrl: './sample.html',
    styleUrls: ['./sample.css'],
    changeDetection: ChangeDetectionStrategy.OnPush
})

The standard Servoy libraries take a different approach and either have a single CSS file with the package name or an assets directory with multiple files in. Which strategy does Servoy recommend we use for our own components?

  1. Finally, the readme on the servoyworld component says to run “npm run build_debug” in the target directory. Is that only if you are editing/developing the component in a separate editor such as Visual Studio Code or do we need to run it when devlopeing using Eclipse as well?

Thanks
Steve

12

1> yes make a case

2> problem with that encapsulated css that it is then very hard to override… even with a solution.css that wants to set stuff (so that css that is loaded later), so thats why we have global assets file so we can always override.

3> for developing components (and you have it added as a source package) you always need to run “npm run build_debug” in the target folder, because no matter what editor you use (i use eclipse itself through the WWD plugin)if you save then we notice that you changed the file and make sure it is copied also to the right build dir (that target dir) and then the angular compiler that is run by that command in watch mode will recompile Titanum NGClient

13

  1. Case SVY-17187 has been created for the editor issue.

  2. Great explanation thanks. However, I moved my CSS from an encapsulated file to the styles.css that was generated in the component package and now the CSS is not being applied. I have checked the file that is sent to the browser and none of my styles are in it. My ng-package.json has:

{
  "$schema": "../node_modules/ng-packagr/ng-package.schema.json",
  "dest": "../dist/",
     "assets": [
        "styles.css"
    ],
  "lib": {
    "entryFile": "src/public-api.ts"
  },
  "allowedNonPeerDependencies": []
}

The styles.css file is listed in the assets section so I assume it should be included (I have removed the styleUrls directive from the compnent.ts file). Any ideas?

  1. Understood - another good explanation thanks.
14

you also need to tells us about that file: https://github.com/Servoy/bootstrapcomp … FEST.MF#L5

besides making sure that it is packaged (when you make a release)

https://github.com/Servoy/bootstrapcomp … ge.json#L5

15

That’s all working fine now thanks Johan. When I finish all my experimenting I will put together a cheat sheet and post it on the forum for others.

One further question though, I have an AngularJS component that does not have an Angular equivalent so I need to find a different one that does the same job for the NG2 client. I think I have found what I need but the new component has some additional properties that I would like to utilise. Is there a way to specify properties in the .spec file and flag them as NG2 only (so they only show up in the NG2 form editor)? As a follow up, is it possible to have a component package of only NG2 components?

16

no we don’t have a flag that says this is TiNG only (only deprecate to deprecate a ng1 property)

TiNG only components kind of means that they don’t have a definition reference/file in the spec: https://github.com/Servoy/bootstrapcomp … ox.spec#L2 compare to: https://github.com/Servoy/bootstrapcomp … ox.spec#L7

17

In the forms editor, I can’t find the Tabless panel (css layout) in the palette anymore. There is Split Pane, and TabPanel component available, but not the Tabless panel component. Where to find it?

Thanks,

18

look under form containers and then “FormContainer”

19

So the component Form Containers > Form container is the successor of the WebComponent > Tabless Panel [bootstrapcomponents-tablesspanel]?

20

huber:
So the component Form Containers > Form container is the successor of the WebComponent > Tabless Panel [bootstrapcomponents-tablesspanel]?

Yes, it is.