scriptHelper / Blog: Recent posts

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

Fix the package declarations for the import(...) methods not working correctly for the RubyScriptWrapper
Fix the package declarations for the import(...) methods not working correctly for the PythonScriptWrapper

Fix the package declarations for the import(...) methods not working correctly for the JSScriptWrapper

Add a DefaultSwingScriptLoggerArea class allowing to show the log in a component which can be integrated in another GUI
Allow to reset the associated wrapper when the user dispose of the error window in the SwingExceptionListener.
In this case, add a "dismiss" option when quitting the error window to allow the user not to see this popup again
Fix the exception lines being off by one when there is a custom ScriptHelper

Allow to use the SwingExceptionListener with exceptions not originating from a script
Avoid to throw an NPE when getting the invocable methods if there is no script associated to a wrapper
Fix the direct invocation of script methods the Groovy, Javascript, and Python being too strict about the method signature

Use docJGenerator 1.4.17.5
Don't add in Ruby the stdlib directory if it does not exist
Allow to invoke directly a method in the wrapper
Add a getMIME() method for all script wrappers
The script can be created from a String content, added the notion of a Script source
Allow to manage properties and functions at the Javascript level in the JSScriptWrapper
Fix the error lines in Javascript being off by one
Fix the Javascript wrapper throwing an exception when installing the script if the script used global variables
Add two methods in each wrapper implementation allowing to know if the associated scripting library is available
Allow the framework to accept functions declaration at the Javascript level rather than only methods declaration

Use Groovy 3.0.3
Use JRuby 9.2.11.0
Fix the Ruby stdlib not loaded in the Ruby wrapper
Allow the Ruby stdlib to be loaded with a default path or to be set in the wrapper

Use JEditor 1.2.6
Fixed an exception which was thrown when creating a debug session with fields declaration
Improve the return type for the "/" expression in the debugger breakpoint properties
Fixed the XOR expression in the debugger breakpoint properties
Handle correctly the compilation exceptions in the debugger
Fix the exception message for compilation errors in the script which contained erroneous line numbers
Fix the SwingDebugScriptWindow not handling clicking on exceptions stacktraces hyperlinks

Add the echo(message, htmlcolor) and echo(number, htmlcolor) methods in the ScriptContext interface

Fix variables declarations in Groovy not taken into account in debug parsing in some generics cases
Make sure that there is a debug step before each block
Fix the exception lines which were incorrect in Debug sessions
Fix the steps line numbers which were incorrect in some cases
Fix the breakpoint properties not taking correctly into account the parenthesis in some cases
Handle breakpoint properties expressions methods with arguments
Silently swallow exceptions from incorrect breakpoint expressions
Show incorrect breakpoint expressions in red in the Swing Debug Script window

Use Jython 2.7.2
Use Groovy 3.0.2
Fix an exception which would occur in the SwingDebugScriptWindow if one of the values for the step variables was null
Add highlight on breakpoint lines in the SwingDebugScriptWindow
Add the jEditor.jar library which was forgotten in the binary distrib
Present the elements of arrays in the Swing debug mode variables tab
Present the types of variables in the Swing debug mode variables tab
Present correctly null values in the Swing debug mode variables tab
Put the VarNode and DebugVar classes in a new core package rather than in the swing package to allow to reuse them
Take correctly into account generics in variables declarations in the Groovy debug parser
Take correctly into account arrays in variables declarations in the Groovy debug parser
Add a method in the DebugSession to check if there is a Breakpoint on a specified line
Fix some cases where the step lines positions where incorrect in the Groovy debug session