> how about not splitting the class (i.e. avoiding to break anything), but
> just add the second class for programmatical access? Maybe this could
> even go into the core.apitools package.


 yes, important to make no backward incompatible changes to
LoadDatasetPlugIn.

If you feel like creating such a class, I can add it.
>

good chance to me to contribute some code ;)


First step is to extract dataset loading with DataSource from
LoadDatasetPlugIn into a
new class called DataSourceTools (or so) in org.openjump.core.apitools.

--Benjamin
------------------------------------------------------------------------------

_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to