Hi Ede, Just committed an early wizard for save as DataStore.
There are still some methods I must complete. But I must first understand what they are for and when they are called. There is also something I don't know how to manage properly : The pluginContext seems to be initialized too early to be used to get the selected layer, so that I have to get the workbenchContext first. It is possible, but I completely loose the interest of the PlugInContext and this is a bit confusing. Did I miss something or did you get the same problem? Michaël Le 28/07/2016 à 16:26, edgar.sol...@web.de a écrit : > On 25.07.2016 23:32, Michaël Michaud wrote: >> Hi Ede, >> >> I had a quick look to see how your new plugin should be used. >> >> Should we use SaveFileWizard for all file-based savers and add a new >> wizard for database savers ? > yepp, new wizardgroup per datasource type > >> Some file-based savers have options (currently, gml, dxf and csv drivers >> have write-options). I suppose that the idea is to replace the "south >> panel" currently used in the traditional saver by a "next" panel to set >> the options ? Or have you another idea ? > yepp, similar as we do in the OpenWizard already > >> Is it supposed to accept "save as image or svg" in the future ? > if we implement those as JUMPWriter or the other datasource type , then why > not? > >> Currently, the plugin is grayed for raster layerables, but if we add new >> wizards, I think the plugin will have to accept more types of layers, >> and the wizards should be grayed out depending on the selected layer and >> the wizard capabilities? Is it possible to activate/deactivate wizards >> depending on the datasource ? > will have to be implemented into the WizardDialog. i imagine some solution > based on the EnableChecked interface. can you commit an early wizard for > databases implementing EnableChecked? i would hack the necessary dialog check > then. > >> Can we add a wizard to deal with multiple layers (and maybe replace the >> plugin "save layers without datasource") ? > for now i feel that saving one dataset into one format and replacing the > datasource for that layer is enough. handling multiple layers, specifying > multiple dataformats to save to sounds complicated and bloated to me. > > ..ede > > > ------------------------------------------------------------------------------ > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > ------------------------------------------------------------------------------ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
