On Fri, Mar 13, 2009 at 12:00 PM, Andreas Karlsson <[email protected]>wrote:
> What I (plan) to do is to automatically recompile the whole > application when a client-plugin is added. > > So I keep a plugin registry on the server side and when I enable/add a > plugin I generate some glue files and recompile + redeploy the whole > GWT-client automatically, this to get the most benefits from GWT > optimizations. > I am in the design phase of a application that will be deployed on different offices, each one with almost equal workflows, automatizing, staff and requisites. Yeah, that "almost" sucks. The idea is to get one big common or default subset, build some kind of plugin / extension / delegation system for the specific and deploy different builds without forking the codebase. That forking should be a nightmare. So, your way was the initial idea, and in our project fits. But some kind of dynamic plugin loading and upgrading, without touching the core install is ideal, and a very powerful tool. For example, you can do per user plugin configs. So, Rosh, what do you think about doing a small prototype? I see appropriate contact via private mail, work on that and publish the results pointing problems and wait for feedback. We can be days talking about the idea, but only the code can prove it can work, and looks like anybody has done something similar. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
