Also, have you noticed the @UiField(provided=true) and @UiFactory
annotations? They allow you to take charge of factory duties, instead of
relying on the default GWT.create() behavior.
On Fri, Aug 28, 2009 at 7:30 AM, Joel Webber wrote:
> It may not be a perfect solution to what you want to do,
It may not be a perfect solution to what you want to do, but because those
are native DOM Elements, which subtype JavaScriptObject, you can cast them
to any other JSO subtype you like. For example:
@UiField Element elem;
MyWidget() {
// ...
// If your element subclasses Element:
((MyLabelEl
No - more like (for example), when it hits a it always creates
a Google LabelElement - say I want to create a MyLabelElement instead
(which does some extra thing, which in my case it does). I can't do it
without hacking it (which I have done). Happy to file an Issue on
this...
On Aug 27, 11:49 p
On Thu, Aug 27, 2009 at 7:49 AM, Joel Webber wrote:
> On Thu, Aug 27, 2009 at 5:29 AM, Richard Vowles
> wrote:
>
>> I wouldn't mind some convincing urls to backup this viewpoint if you
>> have any :-) The entire rest of the team here is saying "id id id",
>> "class bad, id good". Searching for "
On Thu, Aug 27, 2009 at 5:29 AM, Richard Vowles wrote:
> I wouldn't mind some convincing urls to backup this viewpoint if you
> have any :-) The entire rest of the team here is saying "id id id",
> "class bad, id good". Searching for "html id brittle" wasn't very
> enlightening :-)
>
It's fairly
I wouldn't mind some convincing urls to backup this viewpoint if you
have any :-) The entire rest of the team here is saying "id id id",
"class bad, id good". Searching for "html id brittle" wasn't very
enlightening :-)
I have also found that there seems to be no way of overriding the
class that
