Split up the project into a core module, a widget library module, and an application module. Make your widget library inherit the core module, the application module then inherits both and possibly other widget/extension libraries.
Look at GWT's User module: http://code.google.com/p/google-web-toolkit/source/browse/releases/1.5/user/src/com/google/gwt/user/User.gwt.xml Module XML format: http://code.google.com/docreader/#p=google-web-toolkit-doc-1-5&s=google-web-toolkit-doc-1-5&t=DevGuideModuleXml CSS file injection: http://code.google.com/docreader/#p=google-web-toolkit-doc-1-5&s=google-web-toolkit-doc-1-5&t=DevGuideAutomaticResourceInjection On Sep 6, 9:22 am, Rosh PR <[EMAIL PROTECTED]> wrote: > I'm developing a framework where i can browse and add widgets > dynamically. > > Problems I'm facing > * The widget developer use the framework for developing the widgets. > While compiling gwt dumps all the > widget and framework code into one directory. How will I differentiate > between the framework output and > widget out put so that i can package the widget separately for use by > framework. > > * If the widget developer has a css file to be included in his package > how can that be done, because > the widget developer will be using the framework gwt.xml file while > developing, Can we specify separate > gwt.xml file for a widget class or is there anyway i can associate a > css file for a class. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
