• Add a new preference to skip copy of programs to linked folders when there are build or style check errors
• Use default ProvideX executable when NOMADS Alternate executable is invalid or cannot be found
• When full build is triggered at launch and output folder exists, only build modified files
• Additional log messages when updating outline, dictionary, and library DOM data
• New builder option to disable scan for duplicate function and variable names (Error 24)
• Add support for encrypted password values (requires ProvideX v9.20 or newer)
• Improve error 24 scan logic for class declaration
  • Support full function definition within the class declaration section
  • Ignore LOCAL within a function definition
• Add new project-specific property 'AltExe_EnvironmentPropertyFile'
  • Set the name of a properties file containing name/value pairs to use to set environment variables when initializing the build process; when property is set force build process to use the alternate executable flow.
  • This format of this file:
    • one name/value pair per line in the format name=value
    • a line starting with '#' is considered to be a comment
    • blank lines are ignored

    # Example Name/Value pairs
    my_app_title=Application Fantastic
    my_app_debug=1

• The Convert programs to text process has changed to use the source file in the original location rather than move the file to the output folder. This will reduce issues with source control systems where the move to the output folder was tracked as an intentional change.

• Add a new preference, and associated logic, to skip copy of programs to linked folders when there are build or style check errors

Several new preferences have been added to the "Builder Options" preference page:

• Skip copy of programs with errors to linked folders

  When enabled, programs containing errors will not get copied to any linked folders.

• Ignore FULL Build for existing projects triggered when starting Eclipse

  As part of the startup of Eclipse full builds are sometimes triggered for all projects in a workspace. When this preference is enabled the plug-in will ignore the full build request; full builds can still be triggered from the Project menu.

• Simple scan for duplicate function/variable names (Error 24)

  When disabled, the simple scan for duplicate function/variable names is skipped

• The process to convert ProvideX programs to text has changed.

  Old Import/Convert Process

  The old process moved the file from the source folder to the output folder and then converted the file in the output folder to create a new text version of the program in the source folder. One of the primary issues with this approach is the impact it has when using version control - all history is lost on the original file and there is a potential that the file moved to the output folder may now be tracked by the version control process.

  New Import/Convert Process

  The new process leaves the source file in the source folder. If the option Always add source file extension when converting programs to text is enabled, the convert process will create the text file in the source folder and then delete the original source file. If this option is not enabled, the text version of the program will have the same name as the original program. The convert process creates a temporary file for the text version of the program and replaces the original program with this temporary file. If the convert to text fails, the original source file has not changed.

  
  This has a number of benefits:
  • reduces potential loss of original source file if conversion process fails
  • more accurate and complete history when tracking changes in version control
  • no longer have a file in the output folder that may be tracked by version control

• Additional debug messages to track (rare) issue where NOMADS library information is not loaded
• Fix for null pointer exception when processing file annotations
• Identification of keywords to highlight will now stop when followed by one of the characters: < > - * /
• Updated Constants and Functions

• Contributed Tools List
  • The Configure button on the Contributed Tools list is disabled when a configuration action has not been implemented
• Writing a Contributed Tool
  • A new example to show how to use a panel for configuration options and the progress view to show messages as the tool performs actions.
• Save Window Position
  • Save the new position of the window for a contributed tool if it is moved. For more information, see Preferences - Appearance in the Plug-in Documentation.

This is a contributed tool to encrypt a simple text password value. The encrypted password can be copied and used in:

• The password field on a program properties page
• The list of known passwords on the Import/Convert Preference page
• The project properties file, property 'appendPreferenceS._ProgramPasswordList' to include the list of known passwords for a specific project.
  
  
  
  

• New substitution tags for code blocks
  • Add substitution tag %PvxCode2()% to add ProvideX code sample to replace the tag in line
  • Add substitution tags %PvxCodeBegin% / %PvxCodeEnd% to define blocks of code spanning multiple lines
• Allow parameter documentation to span multiple lines
  • When parameter documentation text starts with plus (+) character, add the remaining text to previous line to allow parameter description to span multiple lines
• Enhanced Documentation Generation Parameters

  Several new options have been added to the document generation setup page.

  
  
  
  • Option to override the method used to link to content pages from menu
  • Option to set modification date/time stamp to match source file
  
  

• Display additional field information

  Update to display additional information from the dictionary for each field:
  print format

A number of enhancements have been made to the Style Check contributed tool:

• Check search value against list of keywords

  Define a rule to check the search value against list of keywords for each line.

• Detailed Log of Issues

  The Style Check process will now create a detailed log of the issues discovered during the scan process; this log can be viewed by clicking new Details button once the scan process is complete.

• A new contributed tool to replace special tags in a source file with a substitution value before creating the output file. The tags and substitution values are defined in a properties file built-in to the plug-in.
• Additional user-defined tags and substitution values can be defined in a tagSubstitution.properties files in the folder configured for user keywords and external observers on the Contributed Extensions/Tools preference page.
• The original source file is not changed; changes will appear in the compiled program(s).
• The logic will search for the tags in the following formats, there can be an optional colon after the keyword:
  • $keyword$
  • %keyword%
  • %(keyword)%
  • %{keyword}%
• The format of the properties file is:
  keyword = substitution text or string expression
• The string expression can use any ProvideX code to create the expression to use as the substitution value. The following variables are also available to include in the expression:
  • cOutputFilename$
  • cSourceLastModDate$
  • cSourceLastModTimestamp$
  • cSourceLastModYear$
• The built-in tags and substitution values (some are formatted to be similar to the keyword substitution performed when using Subversion):
  

  Copyright = "(c) " + dte(0:"%Yl") +" The Sage Group plc or its licensors. All rights reserved."
  Header = "$Id: " + cOutputFilename$ + " " + cSourceLastModTimestamp$ + " $"
  Id = "$Id: " + cOutputFilename$ + " " + cSourceLastModTimestamp$ + " $"
  Revision = "$Revision: " + cSourceLastModDate$ + " $"

• The secondary properties file used for the user defined substitution tags can override the definitions of the built-in tags as well as create new tags.

Override NOMADS preference page settings for a project.

• NOMADS_AltExe

  A full path to a ProvideX executable to be used for all NOMADS sessions launched for a resource in the project; (Use "/" characters in the path). The path will be verified to be a valid ProvideX executable before it is used. If the validation fails, the first executable found from the following list will be used:

  • NOMADS executable for the workspace
  • ProvideX executable for the project
  • ProvideX executable used by the workbench
  
  
• NOMADS_ExtDictDir

  Specify a folder that is outside of the project workspace as the location of the ProvideX data dictionary files. The file 'PROVIDEX.DDF' must exist in this folder, otherwise, the value of this property will not be used.