Hi Jumpers, I've started to add a big feature for OJ : capability to record macros.
I did not find a way to implement it without the need to revisit each plugin, but I tried to adopt a design - which does not break existing plugins - where adaptation to make a plugin recordable in a macro is minimal The general idea is : - make plugins persistable along with its parameters - make plugins runnable from a map of parameters (instead of an interactive dialog box) To achieve that in a simple way, plugins must be able to store/access their parameters through a simple Map<String,Object> Usually, to make a plugin recordable : - you must put parameters gathered from a MultiInputDialog into a map - refactor the code so that it accepts the map values as parameters instead of named plugin attributes (see changes in BufferPlugIn) I have tested the concept with several different tools : - DisposeSelectedLayerPlugIn - BufferPlugIn - ViewSchemaPlugIn - DataSourceFileLayerLoader Some are easy to adapt (ex. DisposeSelectedLayerPlugIn), other are difficult (ex. ViewSchemaPlugIn) Any comment about the design is welcome Any help to make all our plugins recordable is welcome Michaël ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
