Hi, It seems that the load/save dataset design has been revisited in the early stage of OpenJUMP and is now a little bit confused.
There is 3 PlugIn available for loading file datasets and 3 others to save them ex. .../workbench/datasource/SaveDatsetAsFilePlugIn .../workbench/datasource/SaveDatsetAsPlugIn .../workbench/ui/plugin/SaveDatasetAsPlugIn The last one, directly derived from ThreadedBasePlugIn seems no more used (I deactivated it in my source repositiry and noticed no difference). Probably needs to be removed after some more tests. SaveDatasetAs opens a dialogbox to choose a format in a combobox, then a file extension and eventually a config file. The second is more simple with just a combobox for the file extension. I thing that the first one (SaveDatasetAs) can also be used for non-file datasources (the first postgis plugin used it, may be also Larry's SDE driver), but now, there is also a separate menu for datastore connexions. I recently wrote a driver for a file format using the datasource api. My driver works with LoadDataset and SaveDatasetAs, but is buggy with LoadDatasetFromFile and SaveDatasetAsFile (I get an NPE). Before I spend time to debug my driver, I'd like to know if any of you has a clear vision about the data source UI. I feel like there are too many ways to do things. Michaël ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Jump-pilot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
