It says already in the deprecation statement of PluggableImport that the
Import class has no registration method so it should come as no
surprise.
How the registration and interfaces are to work in general is described
in the Cookbook chapter 4.1. See also the description on how the new
module loader works, Cookbook section 5.19.2.
The details on the Import interface and registration are not decided. If
it were, the registration method would most likely be there.
/Linus
> -----Original Message-----
> From: Tom Morris [mailto:[EMAIL PROTECTED]
> Sent: den 23 september 2006 22:13
> To: [email protected]
> Subject: [argouml-dev] What replaces PluggableImport and Generator2?
(and
> other language module questions)
>
> We're trying to implement support in ArgoEclipse for reverse
engineering
> which means that we need to deal with the PluggableImport interface.
It
> doesn't really make sense to modify that interface because it is
> deprecated,
> but I can't figure out what replaces it. The comments say to register
> with
> org.argouml.uml.reveng.Import, but that class has no registration
method.
> Additionally, it itself depends on the deprecated PluggableImport
> interface.
>
> On the code generation side of things, Generator2 has been deprecated
in
> favor of CodeGenerator, but they don't appear to have equivalent
> functionality, so I don't understand how this is meant to work.
>
> Are there examples of modules which have been converted to the new
> structure? Is there a design discussion somewhere which describes how
to
> convert old style modules to new style modules?
>
> A related issue is GUI independence. I don't really see any reason
that
> the
> language modules need to be dependent on a GUI. They really only need
to
> know about source modules, the UML model, and some configuration
settings.
> The settings that they need are pretty simple (things like boolean
values,
> integers, strings), so it seems like overkill to make them construct
their
> own settings dialogs. This also unnecessarily couples them to the
GUI.
>
> Who's working on this stuff? I'm happy to help if I can get an idea
of
> what
> the design direction is.
>
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
