hi list, i would need some help / suggestions concerning how to plan layout and dependencies of modules. for the sake of this, i will use the following example:
on the server, there is a service providing access to a repository of content, including authentication and authorization. it has a number of methods to get the actual content objects etc. in the client, there is a base ui that provides. in general, what i want to achieve has two parts. the first is that the client should be able to chose an editor widget based on the type of the content being edited - but i don't want them all to be built into one module. i want to be able to deploy additional modules, that can register themselves and can then be chosen by the core. think eclipse - which will, for example, open ".xml" files with the XML editor by default - but, as we know, although it is bundled with the normal distribution, this editor is just a plugin. it declares to be extendending certain extension points and thus the core knows about it. as far as my example is concerned, the same might be necessary on the server side (like, some plugin might also need additional functionality on the server side, while at the same time also using some functionality from the "core" (especially authentication, of course)). now my question is mostly about the concepts of the modules in gwt. i have read a couple of things, but i don't quite understand yet how different modules can interact and what touching points i have to consider when designing a plugin interface for my application. any pointers would be appreciated ... thank you .rm -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
