scriptHelper Blog

Fix a deployment problem in the zipped Jar files which could lead to an exception while executing the scripts, remove the intermediary distrib directory which only caused problems

Add an option when aborting a script to not notify the listeners of the abort, and not show anything on the console
Fix a case where the ScripErrorLogger would throw an exception if the file of the exception was null
Fix the file for scripts exceptions not correctly set
Add dialogs for the swing helper to allow to set a file or a directory

Fix a deployment problem in the zipped Jar files which could lead to an exception while executing the scripts

Fix the link to the stack element class being wrongly set to the main script when encountering exceptions on additional scripts in Groovy
Fix the link to the stack element class being wrongly set to the main script when encountering exceptions on additional scripts in Ruby
Fix the link to the stack element class being wrongly set to the main script when encountering exceptions on additional scripts in Python, when using context
Fix the line numbers of additional scripts which were incorrect
Fix the file and the line of the script exceptions which would be incorrect for additional scripts

Use JEditor 1.2.30
Allow additional scripts to use the context and the helper
Add methods in the context to get the main loaded script and the additional scripts
Add a script configuration for the library

Use JEditor 1.2.27
Allow to use additional scripts in scripts (currently not supported with Javascript)
Fix the Python scripts emitting an exception when using the swing logger

Use JEditor 1.2.26
Use JRuby 9.4.12.0
Use Groovy 4.0.26
Add another class to allow to edit a Script as a component which can be integrated in a Swing architecture
Allow to create the script editor component without a script, and set the script later
Add a default script context for swing

Fix some cases where the swing logger area could hang when there are a lot of errors in a script
Add methods in the context to get the logger tab as a text (useful when saving a file)
Add a method in the logger to set the progress bar message of the logger area frame in swing
Add a class to allow to edit a Script
Fix cases where the swing property editor did not work correctly, emitting a NPE when asking for a property

Use docJGenerator 1.6.8.1.1
Use JEditor 1.2.25
Use Groovy 4.0.25
Add a method in the logger interface to set the title of the logger window

Use JEditor 1.2.23
Use Rhino 1.7.15
Use JRuby 9.4.9.0
Use Groovy 4.0.23. It makes the execution of Groovy scripts compatible with Java 23

Fix the parser for the Groovy debugger which did not detect some methods correctly
Fix the parser for the Groovy debugger which did not detect variable declarations before the first method
Fix the SwingDebugScriptWindow incorrectly always settings the initial height of the script source component to 0
Show explicitly compile errors happening in debug sessions in the error window title
Fix the debug session not using the specified logger defined for the wrapper when the logger is specified
Fix the debug window throwing an exception when clicking on an error message
Add a DefaultScriptHelper class
Add a capability in the ant build to get or delete each library separately
Add a method in the ScriptLogger interface to print a StackTrace in the console
Fix groovy compilation exceptions having a wrong message (including the Groovy StackTrace which is of no interest there) and the wrong line number
Allow to add additional helper classes in the script

Use Jython 2.7.3
Now the script libraries are downloaded and not in the repo anymore
Fix the creation of multiple error windows in some cases when there are more than one error in the script
Add a mechanism to handle hyperlinks in the logger
Add the logger field in scripts

Use Netbeans 12.5 for the development
Use docJGenerator 1.6.5.8
Use jDependency 1.4.6.3
Use JEditor 1.2.15
Use Groovy 4.0.16
Use Rhino 1.7.14
Use JRuby 9.4.5.0
Update the JRuby wrapper to replace the "import" by the "java_import" declaration to take into account changes on JRuby 9.4

Go back to Groovy 3.0.7
Use JRuby 9.2.17.0
Fix the Class-Path property in the framework manifest which could prevent the project to be built on Mac OS X or Linux

Add an abstract ScriptExceptionListener
Add a method in the SwingExceptionListener and the DefaultExceptionListener which return true if the script has been aborted or encountered an error

Fix some case where the message for Groovy compilation exception was much too long
Allow to link to the exception line for compilation exceptions which have a corresponding line
Use JRuby 9.2.16.0

Add a method to clear the import declarations for a ScriptWrapper
Fix the addImports methods removing the old imports in the ScriptWrapper

Use Groovy 3.0.7
Use JRuby 9.2.14.0
Use docJGenerator 1.5.2
Fix some cases where the line number corresponding to an exception was off from one

Use Groovy 3.0.5
Use Rhino 1.7.13
Use JRuby 9.2.13.0
Fix the definition of functions properties when there is more than one executor in Javascript

Fix some cases where the direct invocation of Javascript script methods would call the default interface method rather than the specified one

Fix the RubyScriptWrapper and PythonScriptWrapper throwing a StringIndexOutOfBoundsException if the script do not have any extension
Fix the direct invocation of Python scripts which did not work correctly with methods not declared in the Java interface
Wrap exceptions linked to not finding the method in the invokeMethod method in a ScriptRuntimeException, and support their logging if the appropriate wrapper configuration has been specified

Use Groovy 3.0.4
Avoid to open a new error window if there is still another one present
Fix the keys for invoking methods being too strict

Fix closing the SwingExceptionListener which was throwing an NPE in some cases
Fix some cases where the line number of Javascript script exceptions was not found
Improve the message for some Javascript script exceptions
Fix the Rhino error messages which were always emitted in French (at least on French platforms) even if the Locale of the Context was explicitly set. Now the Rhino error messages are always in English at their default

Avoid to set for Javascript the Rhino context more than once
Check the arguments arity in the JSScriptWrapper when setCompilerIsStrict(boolean) method is set to true

Fix the layout of the error window which was incorrect in some cases
Allow to define an array of classes to be accessible in the context of the JSScriptWrapper
Reduce the length of the error message if a Groovy script does not implement the script interface
Reduce the length of the error message if a Python script does not implement the script interface
Reduce the length of the error message if a Ruby script does not implement the script interface
Allow the library to be used in any ClassLoader architecture
Add a setOptimizationLevel(String level) method to the script wrapper to allow to set the optimization level of scripting languages which have this kind of option
Add a set setCompilerIsStrict(boolean) method in the JSScriptWrapper to throw an exception if a method defined in the interface is not implemented