We are pleased to announce the immediate availability of Servoy 7.1 (releaseNumber 2009).
This version is available through the download option on the Servoy website and auto-update.
Always make a backup of your current Servoy installation (directory and database) before installing/upgrading.
To update a Servoy eclipse open “Check for updates” via help menu.
The issues addressed, since Servoy 7.0.1 and Servoy 6.1.5:
WebClient changes
[enh] SVY-4036 replace “loading…” indicator with busy cursor
MobileClient changes
[fix] SVY-4282 Login name cannot contain spaces or special chars
[fix] SVY-4250 Related list shows 6 lines if it is empty
[fix] SVY-4284 Back button on Android device has different behavior than function “history.back”
[fix] SVY-4296 Unable to access foundset on mobile client when no records are pushed from the service solution
Developer changes
[fix] SVY-4293 Missing jsdoc end tag
[fix] SVY-4161 Quiting eclipse will hang eclipse when debug client is still open
[fix] SVY-4233 relations do not show in solution explorer from shared mobile solution
[fix] SVY-4265 re ordering a mobile bean doesn’t seem to work
Plugins changes
[enh] SVY-3327 Toolbar on any smartclient window
At the last Servoy 7 webinar Servoy announced a new versioning scheme with shorter iterations.
If I remember correctly then 7.x.x will be releases with changes only in Developer. 7.x versions will be releases where Servoy server/client/etc have changes.
That last type of releases will also have full installers. Developer-only releases will only be updatable via Eclipse.
Roll over image and cursor are not supported in Smart client tableview/listview forms.
I’m have a lot of these errors on a new system that I’m using to test 7.1.0 and just want to switch them off as the system will be WebClient only. However, this error is not listed under Preferences/Servoy/Errors/Warnings - started looking in 'Form Problems" and have gone through all the other categories without finding anything that will match.
Am I missing something obvious - I do like to keep my “Problems” section neat and tidy with nothing in it -
You are right (of course!) - once I set solution type to Web-Client they all disappeared. That logic makes good sense so I don’t see any need to make it customizable.
@Graham:
In case you do like it more configurable (which I think is a must)
Please vote for the case I already created a couple of weeks ago: https://support.servoy.com/browse/SVY-4424
I had looked to see if this had been reported but missed your case. I’m comfortable with the current setup (now that I’ve rediscovered the WebClient only switch) as it could create problems if you switch off the warning and then someone wants to open up a desktop client.
grahamg:
as it could create problems if you switch off the warning and then someone wants to open up a desktop client.
It’s just that it isn’t supported, but it won’t cause problems.
If you have a hybrid solution and you want to use images in a table on the web, you will end up with a lot of build markers which are warnings on something you already know.
That really distracts from build markers that DO cause a problem.
Seems like that Warning should only show if the Solution Type is set to “Smart Client Only”, so we don’t have these types of problems on hybrid solutions.
Servoy 7.1.0 build 2009 on Windows 7 in Parallels Desktop 8 on Mac OS X 10.8.3.
We have a solution working OK in smart client, but would like to deploy in web client too in 7.1.0. One issue we’ve come across is rather serious for our users. A list of names is rendered differently in web client from smart client. This has been true on earlier versions of Servoy too.
Web client
[attachment=0]Rendered-web-client.png[/attachment]
In the list we have two elements: a button and a name field. The button is not connected to an onRender event. The name field is so connected. The rendering depends on whether the record has been selected and whether or not the person has been omitted from consideration. A button at the top of the list shows H or S to hide or show the omitted people.
The smart client shows the names of omitted people coloured with a pink background. The web client shows them rendered with the generic rendering of the form. There is no difference in the background colour to indicate that a person has been omitted. Our users really do need to refine their lists by evaluating those they have selected and those they have omitted, combing through their lists until they have optimised their selection. That is why we like to show the complete list with currently omitted people clearly identified; and why we also show the list with omitted people removed - by clicking on the H button (Hide). The problem with the lack of background colour change in web client is that the users cannot see who in the list of people has already been omitted.
We have a stylesheet associated with the form. The button is linked to the default style; the name field is linked to ‘gridcell’ style.
In the onRender event the background colour is returned using the following code:
// Return appropriate colour
if (selected&&!omitted) _element.bgcolor = globals.nav_list_selected_colour;
if (selected&&omitted) _element.bgcolor = globals.bg_colour_omit_selected;
if (!selected&&omitted) _element.bgcolor = globals.bg_colour_omit;
if (!selected&&!omitted) _element.bgcolor = globals.core_color_defaultBgColor;
The code is good in smart client, but clearly not in web client. Should I regard this difference between smart and web clients as a feature of 7.1, or is the difference unintended? Does anyone know of a workaround for web client?
My apologies if I have failed to track down comments on this topic elsewhere.
juan.cristobo:
In v6.0 roll over image and cursor work in smart client, why won’t they work in v7??
It’s only about table/listviews.
In that case the rolloverimage would only show when the actual button it was assigned to, was clicked.
This isn’t real rolloverimage behaviour anymore, so I guess that’s the reason why it was pulled.
