action classes that can be loaded in the background in order to speed up the first download of JGraphpad when used online.

The layout and description of the GUI buttons launching those actions is defined in the Graphpad.properties file.

You can easily override any of those action by registering an alternative custom class for it in the properties file.

In order to speed up the startup, we avoid loading those actions eagerly. We rather dynamically instanciate them when they are triggered. A fiew of those action files also describe their GUI. In that case, they should be eagerly loaded. That's why there are two packages: 'eager' and 'lazy'.

Beware of using threads or even the SwingWorker if you want to launch a GUI non blocking resource intensive action through that pattern.