Andreas Rückert schrieb:
[...]
org.argouml.uml.reveng.Import in line 403 reads:
// TODO: Update configPanelExtension with extension settings
// for new language
looks like the point to do something like
setupOptionPane(selectedModule)
which does
selectedModule.getImportSettings()
and build the editors for these settings.
But you have to call this somehow in the actionPerformed method, so the
extension is displayed when the c++ language is selected (as an example),
but disappears, when a different language is selected.
setting up the gui-elements once should be enough.
[...]
maybe tom morris can enlighten this process, especially where splitting
between awt- and swt-components happens.
Not here. As I see it, ImportCommon is the base class for both versions
(Swing and Swt). In Import, we are already in the Swing version. There would
be an alternative ImportSwt class or so, with the same functionality, but based
on Swt.
does the term "there would be" imply, that it doesn't exist?
so we have a ImportSettings-interface that's implemented as a dialog, we
have Settings we don't use and we have two more interfaces to make it
work for java.
any misses?
regards,
alexander
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
