While planning a new Application I'm trying to figure out how to best
design it to get the most out of the whole ClientBundle thing.
But I'm trying to figure out how to use the bundles in ways that they
(1) were intended to be and (2) that fit my needs;
* Is the goal to have a single Resource class at the top-level
that inherits all the resources used by that application?
Is there some penalty to having separate resources created with
GWT.create?
* For CSS, should my app inject the CSS or should the users of
the resource do that themselves using #ensureInjected() ?
* Is there a good way of styling a Widget in different ways,
but still using a single top-level resource?
Think a WindowPanel and a DialogPanel, both inherits a popup
panel but wants to style it differently;
interface WindowResources extends PopupResources {
}
interface DialogResources extends PopupResources {
}
interface AppResources extends WindowResources,
DialogResources {
...
}
If a top-level resource like AppResource can't inherit
both WindowResources and DialogResources, how would one
structure the resources so that WindowPanel and DialogPanel
can have their separate looks?
* If you want to style your application differently than
the default GWT look, you fork the theme module and alter
the CSS to fit your needs. Possible you add some extra
style-names to some of your widgets. All and all, it's
quite simple to change the appearance of the standard
widgets.
How will this work with client bundles in the future?
Will all standard Widgets accept a Resource class as
first constructor argument? And if you want a different
look to your application, you need always to pass
resources around?
Thanks
Johan
--
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.
