Page History

...

Limitations:

Workarounds:

JSDoc Typing infosupport

• Support for typed Arrays: 

  • Wiki Markup

  Support for typed Arrays:

  • @type String\[\]

  or

  •  

  • @type Array\<String\>
• Support for typing JSFoundSets and JSRecord to be of a specific datasource: JSFoundset 
  • @type JSFoundset\<datasource\
  > or JSRecord
  • > 
  • @type JSRecord\<datasource\>
    (a datasource string is build up like this: "
  Wiki Markup
  • db:/{serverName}/{tableName}",
  • so
  • for
  • example
  • "
  • db:/udm/contacts")
• Support for rest paramers: if a function can handle an unlimited number of parameters of the same type, instead of having to hard-code a fixed number of parameters, the last parameter can be specified as a rest parameter, indicating     

Misc.

• Better support for advanced JavaScript code structures
• Better support for inline Java code
• Automatic JSDoc @type setting on global and Form variables 
• a3: Fixed expand/collapse behavior when saving the Script Editor after adding new variables or functions
• a3: Added support for putting comments in script files (.js files) outside functions and outside JSDoc tags linked to variables and functions. Note that the comments are lost in the following scenario's:
  • When using Servoy Repository for team development: The Servoy Repository stores individual variables and functions, so anything else in the .js file is lost. Solution: use SVN instead which is file-based
  • When exporting the Solution to a .servoy file: just like the Servoy Repository, the .servoy export format only contains the individual variables and functions. When the .servoy file is used to move a Solution from development into test/Q&A/production, there should be no issue loosing the comments. However, if the .servoy export is going to be used to transport the source into another workspace/development environment, the loss of the extra information could be unwanted. In this case the solution would be:
    1. Share sourcecode between different developers by allowing (anonymous) checkout from the source repository used (for example SVN). 
    2. Use the native Eclipse Archive file export/import functionality to export and later import an entire Eclipse project (a.k.a. Servoy Solution) 
• Fixed indentation of code when moving code modes from using the "Move Sample" and "Move Code" buttons in the Solution Explorer view
• Fixed indentation of code when pasting code into the Script editor

Still to be done

• Investigate if the "Paste to JavaScript console" option in the Context menu of the Script Editor can be removed or made to work
• Investigate if the "Run as ..." and "Debug as ..." options in the Context menu of the Script Editor can be removed or made to work
• Bring back support for the old way to type a foundset or records to belong to a certain database and table

CSS Editor

A new CSS StyleSheet editor has been incorporated into Servoy Developer, with the following features:

...