Folke is right on the point. You will create a module with its own gwt.xml. This gwt.xml will not have entry point. You will distribute your module(widgets) as a package. Who ever wants to use this widget lib will include your .jar file and inherit the module(using inherit tag in his/her gwt.xml. Remember one thing, when you package your widget library module, do not exclude the source java files(source files) as they will be required at the time of target application build process.
You might also want to create a demo for your widget, do so in a different package(with a different gwt.xml, client, public and server) and inherit your widget library's gwt.xml in it. Happy widgeting! :) Rakesh Wagh On Sep 6, 2: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 -~----------~----~----~----~------~----~------~--~---
