On 24.02.2011 08:45, Michaël Michaud wrote: > In a new class, I would have to duplicate 90% of current MultiInputDialog > class. > That has already been done in MultiInputDialogWithoutCancel class and that's > exactly what I wanted to avoid. > The public API of my new MultiInputDialog is so close to the old one that all > the plugins using MultiInputDialog should work except : > - the one using setInsets (only 3 or 4 plugins use it and I don't thing > you'll see the difference. I wanted to eliminate it for simplification, but I > can easily add it again if anybody observe serious compatibility issues) > - startNewColumn : removed because it is now the role of > DualPaneMultiInputDialog to display a two-pane dialog. Only two plugins were > concerned in the core (affine transformation and layer validation plugins). > But there maybe other external plugins. They will need two small changes to > be fixed)
Keeping the MultiInputDialog would not break any plugins, wouldn't it? You could mark the source(-documentation) as depreciated so we could remove it later. Alternatively, I'd prefer a solution where users using the old style plugins do not receive an error stack but a nice messagebox, telling them to contact the list innstead, so the plugin can be fixed. ..ede ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
