On Monday, January 6, 2014 6:24:05 PM UTC+1, Magnus wrote:
Hi Thomas,
ok, but what about that general rule that you shouldn't extend existing
widgets but rather compose/wrap them within Composite or IsWidget?
This sounds interesting to me...
It's just the good old favor composition over
With your answer i've solved.. But now i have another question.. I've a lot
of tables in my project and i need to view all borders of the flextable and
grid though some cells are empty.. I've tried to add a css
.FlexTable td{
border: thin groove;
}
But it add the border only if the cell is filled
Why exactly are GWT widgets often labeled as heavy?
I understand that it has to do with the attached event (in the
Widget.onAttach() method), and that a Widget should only be used in case
you need DOM events, but what are exactly the heavy parts (details?) of a
Widget that make them heavy?
--
I am having the same problem. Did you get to solve it?
On Tuesday, December 3, 2013 9:05:08 PM UTC+1, umesh shaw wrote:
I am having this error. tried all the option to delete gwt cache, temp
folder, etc from online. but still no luck
Please help..
[ERROR] Exception in thread
Try gwtSdkFirstInClasspathtrue/gwtSdkFirstInClasspath in your
gwt-maven-plugin configuration.
Maybe you have libraries in your project that interference with embedded
libraries in gwt-dev.jar.
-- J.
--
You received this message because you are subscribed to the Google Groups
Google Web
Several ways to skin this cat
1. You can implement both the ValidationProvider and ValidatorFactory
interfaces directly and use defferred binding to replace them.
2. You could just create versions of the ConstraintValidatorFactory,
TraversableResolver and MessageInterpolator that delegate
The NPAPI is being deprecated by the Chrome team this year. You might look
into super-dev mode instead, since you are having trouble anyways.
http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html
http://www.gwtproject.org/articles/superdevmode.html
On Saturday,
I see this issue when something modifies the gwt-unitCache while run time.
This could include:
Manually running GWT compile while running in hosted mode.
Modifying a file during debug that is compiled to JS while runtime is
paused using a break point.
Juno and GWT really sucked. Indigo and
If we have an Editor with LeafValue subeditor.
We can implement the interface ValueAwareEditor. with this interface with
can implement a flush and a setValue.
But the setValue is called after the driver set all values in sub editor.
How can we execute code before the driver set values in sub
On Tuesday, January 7, 2014 1:41:14 PM UTC+1, Ed wrote:
Why exactly are GWT widgets often labeled as heavy?
I understand that it has to do with the attached event (in the
Widget.onAttach() method), and that a Widget should only be used in case
you need DOM events, but what are exactly the
You could try storing the child widget in a private member variable and
then in onAttach() actually add the child widget to its parent. This is the
approach I have taken when using UiChild.
On Friday, January 3, 2014 9:16:23 AM UTC-5, Ben Cuthbert wrote:
Hi All,
I have created a custom
Thanks Jens and Thomas. I have it clear now. It would be nice to have the
interface support. But it is already very cool to have class polymorphism
over the wire.
On Sun, Jan 5, 2014 at 8:27 PM, Thomas Broyer t.bro...@gmail.com wrote:
On Sunday, January 5, 2014 6:06:00 PM UTC+1, Jens wrote:
@Thomas: thanks for the insight, exactly what I was looking for. I wasn't
aware that DOM manipulations could have such a cost.
It's could to be more aware of this during development, especially for
mobile apps.
--
You received this message because you are subscribed to the Google Groups
Google
@Thomas: thanks for the insight, exactly what I was looking for. I wasn't
aware that DOM manipulations could have such a cost.
It's could to be more aware of this during development, especially for
mobile apps.
This DOM manipulation cost greatly depends on the browser! If you target
@Jens: hm thanks, nice to know this details, as it's often (in my case
at least) possible to ensure to first attach all the widgets/elements
before adding it to the parent.. Interesting... thanks...
--
You received this message because you are subscribed to the Google Groups
Google Web
One issue with many simple built-in widgets in GWT is that they register
event handlers even when you
don't handle any event yourself, just to be able to update the styles
(focus, hover, etc.)
I never really understood why they always add a listener. So I suppose
this will change in the near
I see the problem here: I don't consider GWT just a web framework (and
maybe I'm wrong about that). I consider it a platform on which web
frameworks are built (like Vaadin, GXT, Errai and so on). It involves
compiler, language, tooling *and* a web framework. And assuming it as a
platform, I
17 matches
Mail list logo
