First of all, thanks a lot for you answers.
> So overall I would save "massive performance loss" is clearly overstating
> and I am pretty sure you don't have numbers to correct me ;-)
>
You're right, that's only what i've read in many places about the topic.
> Well and as you said the most
Hi all,
i was thinking of ways to break a big large GWT application into multiple
modules to be able to develop modules independently.
I've read some things in the forum and in the documentation but I'm still
quite confused.
The ideal solution:
Have a core/main shell module with the menu and one
Hi Jens,
An easy fix for GWT without implementing the appearance pattern would be to
> let cell widgets use a resource bundle factory. That factory can then be
> replaced with deferred binding.
thanks for the hint.
--
You received this message because you are subscribed to the Google Groups
Hi Rogelio,
thanks for you response.
I know that I can pass a custom resources instance to the constructor. I've
done this many times and works fine.
What I was trying to do is to create a seprate module that contains all my
styles, let's say a *theme*, and simply by inheriting this module in m
Hi everyone,
I'm trying to write my own theme to inherit in my gwt applications.
I started out replicating the structure below the
"com.google.gwt.user.theme.standard" package in a project under
"com.mytheme" and editing some css rules in stanrdard.css. Exported all
this in a jar and inherited
