Child pages
  • New in 7.4

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • SVY-4448 Added support for related find/search
  • SVY-4989 Enhanced the debug mode of the Mobile Client to read the Solution design live from Servoy Developer, which means that the Mobile Debug Client can be refreshed by refreshing the browser
    Since Servoy 7.3 code changes made while debugging are synced between the debug client and Servoy Developer. However, if the debug session would end and then restarted, the debug client would not have the latests code. In Servoy 7.4 the debug client reads the latest code from developer when launched, so it will always have the latest code, instead of having to do a full export if there is was a codechange made since the last export
  • SVY-5336SVY-5164 Improved the Mobile Export Wizard
    The Mobile Solution Export Wizard to remember PhoneGap accountshas been improved by remembering all settings of the previous export and allowing to press the Finish button on the first page of the Wizard if there was a previously successful export that can be repeated based on the stored settings. 
  • Switched to JQuery Mobile virtual click events to work around the standard 300ms delay for click events on mobile browsers
  • Improvements to ListView performance
  • SVY-5406 Added option to configure the order of inclusion for additional JS & CSS resources 
    SVY-5528 More finegrained control over first sync See  the Mobile Solution Export Wizard
  • SVY-5528 Added option to not auto-sync on first login
    If the first form of the Mobile solution is not bound to a datasource, then the Mobile Client will not automatically perform a sync if the Solution is started for the first time. It is then up to the developer to call the sync method before accessing data. This way, the developer has control over how and when to perform synchronization and error handling in case of issues during the sync.
     

Servoy Developer

  • SVY-3659 HTML-based Form Editor (currently only in use for Servoy Mobile)
    By default Servoy Mobile Forms  will still open in the existing Form Editor. To enable the HTML-based form Editor, go to Window > Preferences > Servoy > Form Editor  and uncheck the "Use classic form editor for mobile forms" checkbox.
    Note that by default the browser provided by the operating system is used as internal browser in Servoy Developer. For the best experience it is advised to replace the default browser with the Mozilla XulRunner browser component. See Install Mozilla XulRunner as internal browser for the steps involved.
  • SVY-5742 Made Mozilla XulRunner available as plugin to replace the OS-specific browser using as internal browser inside Servoy Developer
    See Install Mozilla XulRunner as internal browser for the installation steps.
  • SVY-3518 Upgraded to Eclipse 4.3.1
    • Color preview on hover over color declarations in the CSS Editor
    • SVY-5252 Support for CSS3 in the CSS Editor: this does not enable CSS3 usage in StyleSheets used on Forms, but allows setting a CSS3 Profile on .css files stored in the media library.
      To set the CSS Profile, open the Navigator View, locate the .ccs file, select 'Properties' from the context menu > Web Content Settings > select desired CSS Profile)
  • SVY-170 Added support to group Forms together in the Solution Explorer
    The context the forms node of the Solution Explorer provides an entry to "Add working set". Through this option a 'folder' can be created, into which Forms can be dragged and dropped.
    The  folders or working sets are stored in the Resources project and thus can be shared with other developers through the team provider used
  • SVY-5033 Added ability to drag and drop media entries around folders inside the media library
  • SVY-5202 Grouped layout related properties in the Properties View
  • SVY- 4448SVY-5195 Improved deleting of User Groups by allowing multi-select
  • SVY-375 Improved the "Select Dataprovider" dialog with option to create new scope variables
  • SVY-5145 Exposed encapsulation and deprecation properties in the ValueList and Relation Editors
  • SVY-3149 Ability to locate scopes using the Servoy Locator
  • SVY-132 Implemented Search for References on entries in the Media Library
  • SVY-5257 Better indication of what type of update is available through the auto-update mechanism
    The Servoy Developer entry in the overview of available updates will have a version that includes details on whether the update is a release candidate or final and similar information is provided in the Description area of the overview.
    Additionally, the non-final updates are exposed through a different update site, which is disabled by default and should be enabled to receive updates for release candidate updates (see Window > Preferences > Install/Update > Available software Sites).
  • SVY-5194 Improved handling of error reporting when attempting to work on Solutions that are created/modified using a newer version of Servoy Developer

...

  • SVY-5210 Improved display of Excepted vs. Actual in case of failing UnitTests run inside Servoy Developer
  • SVY-3630 Support exporting to .servoy files from both the Export wizard in Servoy Developer as well as the command-line exporter, based on the .dbi files in the workspace, ignoring the actual database structure
    This feature is especially helpfull helpful when doing automated exports through the command-line, for example in a software factory setup
  • SVY-5195 Fixed initialization of Solution when relaunching Debug Smart Client
    Prior to this fix, in certain scenarios not all variables in scopes were initialized again in the newly launched Debug Smart Client
  • SVY-5613 Support for debugging self-executing functions (IIFE) assigned to variables
    Self-executing functions (or IIFE's) are functions that immediatly execute themselves. This can be used to do initialization when a scope loads for example.

    Code Block
    var init = (function(){
       //your code here
    }())

    Note that the outer parenthesis are not needed, but are considered a proper code convention for IIFE's 

...