[gwt-contrib] Re: Comment on DataBackedWidgetsDesign in google-web-toolkit

[codesite-noreply]

Comment by daniel.florey:

I'd like to see annotation based model description. It is less verbose.
See:
http://code.google.com/p/google-web-toolkit-incubator/wiki/TreeTable
For some compiler reason my approach is working in dev-mode but fails in  
compiled output :-(



For more information:
http://code.google.com/p/google-web-toolkit/wiki/DataBackedWidgetsDesign

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: r7517 committed - Adding RegExp to public GWT (native version, pure Java version, tests)

[Thomas Broyer]

On Feb 1, 9:33 pm, John Tamplin  wrote:
> On Mon, Feb 1, 2010 at 3:09 PM, Thomas Broyer  wrote:
> > Isn't translatable code generally going into /trunk/user/super, and
> > the subpackage being called "translatable" rather than "super"?
>
> Those are JRE and infrastructure super-source -- this is more user-level
> code.

Oh, OK.

> Also, if you put them under user/super, you couldn't have a separate
> module to import to pull it in, and RegExp would essentially be part of
> Core.

I don't understand how user/src/com/google/gwt/regexp/super is any
different from user/super/com/google/gwt/regexp/translatable, it's
just a matter of including user/super in the classpath (which it
already is).

> > But actually I'm concerned that this hasn't been discussed at all on
> > the list, ...
>
> This is code that was being used internally getting migrated to GWT itself.
>  Most Googlers are used to working with internal tools and lists/waves, but
> certainly we need to do a better job keeping the discussion in the open.

Understood.

> ...and particularly that RegExp isn't a JSO so you cannot use
>
> > the more performant JS literal notation to initialize a RegExp:
> >   public native RegExp myRegExp() /*-{ return /foo.*bar/gi; }-*/;
>
> It is a JSO (see regexp/super/...) in the JS implementaiton, so you can do
> exactly that.

but it'll fail in DevMode, right?

> It is a pure Java version in the devmode and server
> implementations so you can use RegExp in shared code.

I missed the fact that it could be used on the server too.

And as far as Google Wave is concerned (and yeah it's great tool!), I
cannot find any wave shared with the group ;-)
https://wave.google.com/wave/#restored:search:group%253Agoogle-web-toolkit-contributors%2540googlegroups.com
(well, except the one I just shared (read-only though, for now))

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Re: r7517 committed - Adding RegExp to public GWT (native version, pure Java version, tests)

[David]

Hi,

The subject of roadmap ... when will we see a 2.0.1 ? We currently
need to run with a patch gwt-servlet) due to a classloading issue
which is now in fixed state in the issue database.

Moving to a Wave would be great! I'm always waving alone :-S... maybe
I can then finally grasp why it is supposed to be so great.

David

On Tue, Feb 2, 2010 at 12:46 AM, Bruce Johnson  wrote:
> On Mon, Feb 1, 2010 at 4:05 PM, Sami Jaber  wrote:
>>
>> I'm agree with Thomas. RegExp integration should have been discussed in
>> the list. It is landing into the trunk from nowhere for us...
>
> I mentioned a couple of weeks ago that we were switching to a different
> version control system -- and this is the first example of the sorts of
> hiccups we thought could happen. A Googler, a GWT user but who is not on the
> GWT team proper, has been working on this as a potential contribution, and
> submitted this patch for a code review. We accidentally approved it for
> commit rather than just giving some positive feedback on the code review.
> Thus, a work in progress got dumped on svn.
> We're still working out what sort of approval process makes sense for these
> sorts of contributions, but for a large change like this involving new API
> surface area, we definitely do want and need open, public discussion.
>
>>
>> Since the 2.0 release, I feel that there is less interaction with the
>> contrib list (btw what have been decided for the roadmap ?) and what we are
>> supposed to see in the coming releases.
>
> I think more than anything, you're seeing the effects of a lot of us being
> tired from the GWT 2.0 push. An updated roadmap is still forthcoming, but I
> can summarize a lot of the ad hoc design discussions starting to take place
> like this: we need to fill a lot of gaps in the libraries, especially
> widgets and "app framewpork" sorts of library code. GWT is powerful at
> present, but it doesn't make it especially easy to create traditional
> business apps quickly. We'd like to change that.
>
>>
>> We can understand that you prefer to use internal waves/lists but please
>> let's not forget the "openess" nature of GWT that contribute to make this
>> framework so popular
>
> It's true that Wave is fantastic for design docs, and it's hard not to want
> to use that instead of email. Maybe the right answer is to get everyone on
> this list to move to Wave :-)
>
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Re: r7517 committed - Adding RegExp to public GWT (native version, pure Java version, tests)

[Miguel Méndez]

We are in the process of smoke testing 2.0.1.  We expect for it to be
released in the next day or so.

On Tue, Feb 2, 2010 at 7:18 AM, David  wrote:

> Hi,
>
> The subject of roadmap ... when will we see a 2.0.1 ? We currently
> need to run with a patch gwt-servlet) due to a classloading issue
> which is now in fixed state in the issue database.
>
> Moving to a Wave would be great! I'm always waving alone :-S... maybe
> I can then finally grasp why it is supposed to be so great.
>
> David
>
> On Tue, Feb 2, 2010 at 12:46 AM, Bruce Johnson  wrote:
> > On Mon, Feb 1, 2010 at 4:05 PM, Sami Jaber  wrote:
> >>
> >> I'm agree with Thomas. RegExp integration should have been discussed in
> >> the list. It is landing into the trunk from nowhere for us...
> >
> > I mentioned a couple of weeks ago that we were switching to a different
> > version control system -- and this is the first example of the sorts of
> > hiccups we thought could happen. A Googler, a GWT user but who is not on
> the
> > GWT team proper, has been working on this as a potential contribution,
> and
> > submitted this patch for a code review. We accidentally approved it for
> > commit rather than just giving some positive feedback on the code review.
> > Thus, a work in progress got dumped on svn.
> > We're still working out what sort of approval process makes sense for
> these
> > sorts of contributions, but for a large change like this involving new
> API
> > surface area, we definitely do want and need open, public discussion.
> >
> >>
> >> Since the 2.0 release, I feel that there is less interaction with the
> >> contrib list (btw what have been decided for the roadmap ?) and what we
> are
> >> supposed to see in the coming releases.
> >
> > I think more than anything, you're seeing the effects of a lot of us
> being
> > tired from the GWT 2.0 push. An updated roadmap is still forthcoming, but
> I
> > can summarize a lot of the ad hoc design discussions starting to take
> place
> > like this: we need to fill a lot of gaps in the libraries, especially
> > widgets and "app framewpork" sorts of library code. GWT is powerful at
> > present, but it doesn't make it especially easy to create traditional
> > business apps quickly. We'd like to change that.
> >
> >>
> >> We can understand that you prefer to use internal waves/lists but please
> >> let's not forget the "openess" nature of GWT that contribute to make
> this
> >> framework so popular
> >
> > It's true that Wave is fantastic for design docs, and it's hard not to
> want
> > to use that instead of email. Maybe the right answer is to get everyone
> on
> > this list to move to Wave :-)
> >
> > --
> > http://groups.google.com/group/Google-Web-Toolkit-Contributors
>
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>



-- 
Miguel

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Re: r7517 committed - Adding RegExp to public GWT (native version, pure Java version, tests)

[John Tamplin]

On Tue, Feb 2, 2010 at 5:47 AM, Thomas Broyer  wrote:

> I don't understand how user/src/com/google/gwt/regexp/super is any
> different from user/super/com/google/gwt/regexp/translatable, it's
> just a matter of including user/super in the classpath (which it
> already is).


One advantage is that "super" is illegal in any Java package name, so there
can't be collision between a super and non-super path.  Also, it is more
consistent with the super-source module tag.  Finally, it seems cleaner to
have all parts of a module under an isolated directory tree, rather than
split into user/src and user/super.


> > It is a JSO (see regexp/super/...) in the JS implementaiton, so you can
> do
> > exactly that.
>
> but it'll fail in DevMode, right?


No, it works fine in DevMode just like any other JSO, since JSNI methods get
run there.  It won't work in pure Java, so you can't use that in server or
shared code.


> And as far as Google Wave is concerned (and yeah it's great tool!), I
> cannot find any wave shared with the group ;-)
>
> https://wave.google.com/wave/#restored:search:group%253Agoogle-web-toolkit-contributors%2540googlegroups.com
> (well, except the one I just shared (read-only though, for now))


The problem is that right now the public wave and the internal one are two
separate instances.  Once the wave team has federated servers working, it
should be readily possible to do that.

-- 
John A. Tamplin
Software Engineer (GWT), Google

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Re: r7517 committed - Adding RegExp to public GWT (native version, pure Java version, tests)

[Ray Ryan]

We can use the public Wave instance with alternate addresses. Inconvenient,
but it's not that big a deal.

On Feb 2, 2010 7:18 AM, "John Tamplin"  wrote:

On Tue, Feb 2, 2010 at 5:47 AM, Thomas Broyer  wrote:
>
> I don't understand how...
One advantage is that "super" is illegal in any Java package name, so there
can't be collision between a super and non-super path.  Also, it is more
consistent with the super-source module tag.  Finally, it seems cleaner to
have all parts of a module under an isolated directory tree, rather than
split into user/src and user/super.



>
> > It is a JSO (see regexp/super/...) in the JS implementaiton, so you can
do
> > exactly that...
No, it works fine in DevMode just like any other JSO, since JSNI methods get
run there.  It won't work in pure Java, so you can't use that in server or
shared code.



>
> And as far as Google Wave is concerned (and yeah it's great tool!), I
> cannot find any wave ...

The problem is that right now the public wave and the internal one are two
separate instances.  Once the wave team has federated servers working, it
should be readily possible to do that.



-- 
John A. Tamplin
Software Engineer (GWT), Google

-- 

http://groups.google.com/group/Google-Web-Toolkit-Contributors

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Eclipse project Readme file outdated.

[Marko Vuksanovic]

Hi,

I have tried to set up the eclipse development environment as
described in /trunk/eclipse/readme but when I have imported projects
into the eclipse workspace I noticed that all the project have
references to gwt-user and/or gwt-dev. The problem is that those
projects do not exist - it seems that they are renamed into user and
dev, respectively.

Could somebody verify this? If I am right - should I rename the
projects into gwt-user and gwt-dev, or should I replace the references
in other projects?

Thanks in advance.

- Marko Vuksanovic.

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Eclipse project Readme file outdated.

[John Tamplin]

On Tue, Feb 2, 2010 at 10:56 AM, Marko Vuksanovic  wrote:

> I have tried to set up the eclipse development environment as
> described in /trunk/eclipse/readme but when I have imported projects
> into the eclipse workspace I noticed that all the project have
> references to gwt-user and/or gwt-dev. The problem is that those
> projects do not exist - it seems that they are renamed into user and
> dev, respectively.
>
> Could somebody verify this? If I am right - should I rename the
> projects into gwt-user and gwt-dev, or should I replace the references
> in other projects?
>

There are directories user and dev, but the Eclipse projects are gwt-dev,
gwt-user, gwt-lang, Mail, Showcase, etc.  If you follow the import
instructions in the README, you will get a list of all the Eclipse projects
which are available when you choose to import existing projects and choose
the eclipse directory as the base to search.

-- 
John A. Tamplin
Software Engineer (GWT), Google

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Re: r7517 committed - Adding RegExp to public GWT (native version, pure Java version, tests)

[Paul Robinson]

I'd hate to see even more discussions moving away from here (because I,
and maybe quite a few others here, don't have access to Wave).

Paul

Ray Ryan wrote:
>
> We can use the public Wave instance with alternate addresses.
> Inconvenient, but it's not that big a deal.
>
>  

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Re: r7517 committed - Adding RegExp to public GWT (native version, pure Java version, tests)

[Ray Ryan]

That's a very good point. I'm confident we could get anyone invited who
wants to participate, but there's nothing we could do yet to make such waves
visible to non-members, and that would be really bad.

On Tue, Feb 2, 2010 at 8:43 AM, Paul Robinson  wrote:

> I'd hate to see even more discussions moving away from here (because I,
> and maybe quite a few others here, don't have access to Wave).
>
> Paul
>
> Ray Ryan wrote:
> >
> > We can use the public Wave instance with alternate addresses.
> > Inconvenient, but it's not that big a deal.
> >
> > 
>
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>



-- 
I wish this were a Wave

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Re: r7517 committed - Adding RegExp to public GWT (native version, pure Java version, tests)

[Ray Ryan]

Well, not nothing — it'd be pretty easy for a bot to be written to publish
static views of waves. But without that…

On Tue, Feb 2, 2010 at 8:47 AM, Ray Ryan  wrote:

> That's a very good point. I'm confident we could get anyone invited who
> wants to participate, but there's nothing we could do yet to make such waves
> visible to non-members, and that would be really bad.
>
>
> On Tue, Feb 2, 2010 at 8:43 AM, Paul Robinson  wrote:
>
>> I'd hate to see even more discussions moving away from here (because I,
>> and maybe quite a few others here, don't have access to Wave).
>>
>> Paul
>>
>> Ray Ryan wrote:
>> >
>> > We can use the public Wave instance with alternate addresses.
>> > Inconvenient, but it's not that big a deal.
>> >
>> > 
>>
>> --
>> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>>
>
>
>
> --
> I wish this were a Wave
>



-- 
I wish this were a Wave

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: RR : Record selected annotations in Java AST

[spoon]

LGTM, with a few nits.

Also, if there is no specific reason to have the annotations white list,
I think we could simplify our code and drop it for now.



http://gwt-code-reviews.appspot.com/134810/diff/1/2
File dev/core/src/com/google/gwt/dev/jjs/ast/HasAnnotations.java
(right):

http://gwt-code-reviews.appspot.com/134810/diff/1/2#newcode26
Line 26: List getAnnotations();
getAnnotations(String className) would seem good to add here.  That's
the method that would almost always be used.

http://gwt-code-reviews.appspot.com/134810/diff/1/3
File dev/core/src/com/google/gwt/dev/jjs/ast/JAnnotation.java (right):

http://gwt-code-reviews.appspot.com/134810/diff/1/3#newcode32
Line 32: public class JAnnotation extends JLiteral {
Extending literal means it extends expression, which means this class
will show up whenever someone contemplates an operation across all
expressions.  However, most places that expressions can be used, an
annotation cannot.

How about instead an interface AnnotationArgument?  JLiteral and
JAnnotation would implement it.

http://gwt-code-reviews.appspot.com/134810/diff/1/3#newcode56
Line 56: assert values.size() == 1 : "Expecting single-valued property,
found "
This seems like a method developers would expect to always do the check,
not only when assertions are enabled.

http://gwt-code-reviews.appspot.com/134810/diff/1/3#newcode145
Line 145: private Object reifyValue(JLiteral value) throws
ClassNotFoundException {
This is more precisely "evaluation": it converts an AST to a value.

http://gwt-code-reviews.appspot.com/134810/diff/1/3#newcode186
Line 186: // Crete the annotation as a reflective Proxy instance
Create

http://gwt-code-reviews.appspot.com/134810/diff/1/13
File dev/core/src/com/google/gwt/dev/jjs/impl/GenerateJavaAST.java
(right):

http://gwt-code-reviews.appspot.com/134810/diff/1/13#newcode2689
Line 2689: * @param annotations
Noise in the Javadoc.

http://gwt-code-reviews.appspot.com/134810/diff/1/13#newcode2711
Line 2711: JInterfaceType annotationType = (JInterfaceType)
typeMap.tryGet(binding);
Add TypeMap.getOrExternal?  This logic appears twice in GenerateJavaAST.

http://gwt-code-reviews.appspot.com/134810/diff/1/13#newcode3120
Line 3120: "com.google.gwt.dev.jjs", "test"));
Do we actually need an explicit white list?  There's already an implicit
white list that the only annotations that will have any effect are those
that the compiler includes special support for.

http://gwt-code-reviews.appspot.com/134810

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Re: r7517 committed - Adding RegExp to public GWT (native version, pure Java version, tests)

[Bruce Johnson]

On Tue, Feb 2, 2010 at 11:43 AM, Paul Robinson  wrote:

> [...] I, and maybe quite a few others here, don't have access to Wave.
>

We can probably do something about that. I'll start another thread where
people who don't have Wave access yet can indicate interest in signing up.

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Interest in Wave for design docs?

[Bruce Johnson]

Hi folks,

There has been some discussion about having design discussions in Wave, but
maybe not everybody has access yet.

Disclaimer: I can't promise the rate at which everyone will get invites, but
as GWT contributors, I'll happily argue that you should be early in the
queue.

Reply to this thread if you'd like to get an invitation.

-- Bruce

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Interest in Wave for design docs?

[Paul Robinson]

Yes please.

> Reply to this thread if you'd like to get an invitation. 
>

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: Interest in Wave for design docs?

[Daniel Dietrich]

Hi Bruce,

thank you for your commitment regarding Wave participation for GWT
folks.
I really appreciate that.

- Daniel

On 2 Feb., 18:12, Bruce Johnson  wrote:
> Hi folks,
>
> There has been some discussion about having design discussions in Wave, but
> maybe not everybody has access yet.
>
> Disclaimer: I can't promise the rate at which everyone will get invites, but
> as GWT contributors, I'll happily argue that you should be early in the
> queue.
>
> Reply to this thread if you'd like to get an invitation.
>
> -- Bruce

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: Eclipse project Readme file outdated.

[Marko Vuksanovic]

I have checked out the project once again on another machine and followed
the procedure as in readme file once again - this time the projects were
named correctly but I got a lot of warnings - mostly unread local variable
or possible accidental assignement and a few others...

Is this normal? or I have set up sth wrong?

On Tue, Feb 2, 2010 at 4:56 PM, Marko Vuksanovic
wrote:

> Hi,
>
> I have tried to set up the eclipse development environment as
> described in /trunk/eclipse/readme but when I have imported projects
> into the eclipse workspace I noticed that all the project have
> references to gwt-user and/or gwt-dev. The problem is that those
> projects do not exist - it seems that they are renamed into user and
> dev, respectively.
>
> Could somebody verify this? If I am right - should I rename the
> projects into gwt-user and gwt-dev, or should I replace the references
> in other projects?
>
> Thanks in advance.
>
> - Marko Vuksanovic.




-- 
-Marko Vuksanovic

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Re: Eclipse project Readme file outdated.

[John Tamplin]

On Tue, Feb 2, 2010 at 12:22 PM, Marko Vuksanovic  wrote:

> I have checked out the project once again on another machine and followed
> the procedure as in readme file once again - this time the projects were
> named correctly but I got a lot of warnings - mostly unread local variable
> or possible accidental assignement and a few others...
>
> Is this normal? or I have set up sth wrong?
>

Did you setup your Java warnings as described in the README?

-- 
John A. Tamplin
Software Engineer (GWT), Google

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Re: Interest in Wave for design docs?

[Ray Ryan]

Hey, all. I've just set up a de facto GWT Contrib Home Wave:

https://wave.google.com/wave/#restored:wave:googlewave.com!w%252Boe8GWDliE

On Tue, Feb 2, 2010 at 9:20 AM, Daniel Dietrich wrote:

> Hi Bruce,
>
> thank you for your commitment regarding Wave participation for GWT
> folks.
> I really appreciate that.
>
> - Daniel
>
> On 2 Feb., 18:12, Bruce Johnson  wrote:
> > Hi folks,
> >
> > There has been some discussion about having design discussions in Wave,
> but
> > maybe not everybody has access yet.
> >
> > Disclaimer: I can't promise the rate at which everyone will get invites,
> but
> > as GWT contributors, I'll happily argue that you should be early in the
> > queue.
> >
> > Reply to this thread if you'd like to get an invitation.
> >
> > -- Bruce
>
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>



-- 
I wish this were a Wave

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: Interest in Wave for design docs?

[Daniel Dietrich]

Hi Ray,

your link doesn't work for me. Do I need a Wave account?

Thanks in advance

- Daniel

On 2 Feb., 18:33, Ray Ryan  wrote:
> Hey, all. I've just set up a de facto GWT Contrib Home Wave:
>
> https://wave.google.com/wave/#restored:wave:googlewave.com!w%252Boe8G...
>
> On Tue, Feb 2, 2010 at 9:20 AM, Daniel Dietrich 
> wrote:
>
>
>
>
>
> > Hi Bruce,
>
> > thank you for your commitment regarding Wave participation for GWT
> > folks.
> > I really appreciate that.
>
> > - Daniel
>
> > On 2 Feb., 18:12, Bruce Johnson  wrote:
> > > Hi folks,
>
> > > There has been some discussion about having design discussions in Wave,
> > but
> > > maybe not everybody has access yet.
>
> > > Disclaimer: I can't promise the rate at which everyone will get invites,
> > but
> > > as GWT contributors, I'll happily argue that you should be early in the
> > > queue.
>
> > > Reply to this thread if you'd like to get an invitation.
>
> > > -- Bruce
>
> > --
> >http://groups.google.com/group/Google-Web-Toolkit-Contributors
>
> --
> I wish this were a Wave

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: JsStackEmulation leaves alone expressions invoked as functions

[spoon]

Committed at r7516 .

http://gwt-code-reviews.appspot.com/132815

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Re: Interest in Wave for design docs?

[Ray Ryan]

Yes, you'll need an invitation to Wave.

On Tue, Feb 2, 2010 at 10:10 AM, Daniel Dietrich wrote:

> Hi Ray,
>
> your link doesn't work for me. Do I need a Wave account?
>
> Thanks in advance
>
> - Daniel
>
> On 2 Feb., 18:33, Ray Ryan  wrote:
> > Hey, all. I've just set up a de facto GWT Contrib Home Wave:
> >
> > https://wave.google.com/wave/#restored:wave:googlewave.com!w%252Boe8G...
> >
> > On Tue, Feb 2, 2010 at 9:20 AM, Daniel Dietrich  >wrote:
> >
> >
> >
> >
> >
> > > Hi Bruce,
> >
> > > thank you for your commitment regarding Wave participation for GWT
> > > folks.
> > > I really appreciate that.
> >
> > > - Daniel
> >
> > > On 2 Feb., 18:12, Bruce Johnson  wrote:
> > > > Hi folks,
> >
> > > > There has been some discussion about having design discussions in
> Wave,
> > > but
> > > > maybe not everybody has access yet.
> >
> > > > Disclaimer: I can't promise the rate at which everyone will get
> invites,
> > > but
> > > > as GWT contributors, I'll happily argue that you should be early in
> the
> > > > queue.
> >
> > > > Reply to this thread if you'd like to get an invitation.
> >
> > > > -- Bruce
> >
> > > --
> > >http://groups.google.com/group/Google-Web-Toolkit-Contributors
> >
> > --
> > I wish this were a Wave
>
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>



-- 
I wish this were a Wave

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Re: Interest in Wave for design docs?

[Alejandro D. Garin]

Hi,

I have some wave invitations to give. Send me a private email if you want
one of it.

On Tue, Feb 2, 2010 at 3:30 PM, Ray Ryan  wrote:

> Yes, you'll need an invitation to Wave.
>
>
> On Tue, Feb 2, 2010 at 10:10 AM, Daniel Dietrich 
> wrote:
>
>> Hi Ray,
>>
>> your link doesn't work for me. Do I need a Wave account?
>>
>> Thanks in advance
>>
>> - Daniel
>>
>> On 2 Feb., 18:33, Ray Ryan  wrote:
>> > Hey, all. I've just set up a de facto GWT Contrib Home Wave:
>> >
>> > https://wave.google.com/wave/#restored:wave:googlewave.com!w%252Boe8G.
>> ..
>> >
>> > On Tue, Feb 2, 2010 at 9:20 AM, Daniel Dietrich <
>> cafeb...@googlemail.com>wrote:
>> >
>> >
>> >
>> >
>> >
>> > > Hi Bruce,
>> >
>> > > thank you for your commitment regarding Wave participation for GWT
>> > > folks.
>> > > I really appreciate that.
>> >
>> > > - Daniel
>> >
>> > > On 2 Feb., 18:12, Bruce Johnson  wrote:
>> > > > Hi folks,
>> >
>> > > > There has been some discussion about having design discussions in
>> Wave,
>> > > but
>> > > > maybe not everybody has access yet.
>> >
>> > > > Disclaimer: I can't promise the rate at which everyone will get
>> invites,
>> > > but
>> > > > as GWT contributors, I'll happily argue that you should be early in
>> the
>> > > > queue.
>> >
>> > > > Reply to this thread if you'd like to get an invitation.
>> >
>> > > > -- Bruce
>> >
>> > > --
>> > >http://groups.google.com/group/Google-Web-Toolkit-Contributors
>> >
>> > --
>> > I wish this were a Wave
>>
>> --
>> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>>
>
>
>
> --
> I wish this were a Wave
>
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Re: r7517 committed - Adding RegExp to public GWT (native version, pure Java version, tests)

[Arthur Kalmenson]

Seems like we need a bot to publish Waves as Google Code wikis :)

--
Arthur Kalmenson



On Tue, Feb 2, 2010 at 11:47 AM, Ray Ryan  wrote:
> Well, not nothing — it'd be pretty easy for a bot to be written to publish
> static views of waves. But without that…
>
> On Tue, Feb 2, 2010 at 8:47 AM, Ray Ryan  wrote:
>>
>> That's a very good point. I'm confident we could get anyone invited who
>> wants to participate, but there's nothing we could do yet to make such waves
>> visible to non-members, and that would be really bad.
>>
>> On Tue, Feb 2, 2010 at 8:43 AM, Paul Robinson  wrote:
>>>
>>> I'd hate to see even more discussions moving away from here (because I,
>>> and maybe quite a few others here, don't have access to Wave).
>>>
>>> Paul
>>>
>>> Ray Ryan wrote:
>>> >
>>> > We can use the public Wave instance with alternate addresses.
>>> > Inconvenient, but it's not that big a deal.
>>> >
>>> > 
>>>
>>> --
>>> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>>
>>
>>
>> --
>> I wish this were a Wave
>
>
>
> --
> I wish this were a Wave
>
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Questions on JsArray*

[Tom]

Hi,

I have some questions and proposals around the JsArray-classes because
they are handy when working with JSNI but I believe they could be
improved a bit.

a) Why are not all native methods provided through the wrapper.
Missing methods are:
* concat
* pop
* reverse
* slice
* splice
* sort

b) It would be nice if one could use them in a for-loop but because an
interface can only be implemented by one native class it can't
implement Iterable directly but provide a method like iterable().

An implementation for JsArrayString would look like this:

### Eclipse Workspace Patch 1.0
#P gwt-toolkit
Index: user/src/com/google/gwt/core/client/JsArrayString.java
===
--- user/src/com/google/gwt/core/client/JsArrayString.java  (revision
7519)
+++ user/src/com/google/gwt/core/client/JsArrayString.java  (working
copy)
@@ -15,6 +15,11 @@
  */
 package com.google.gwt.core.client;

+import java.util.Iterator;
+
+import com.google.gwt.emul.java.util.AbstractList;
+import com.google.gwt.emul.java.util.NoSuchElementException;
+
 /**
  * A simple wrapper around a homogeneous native array of string
values.
  *
@@ -116,4 +121,92 @@
   public final native void unshift(String value) /*-{
 this.unshift(value);
   }-*/;
+
+  /**
+   * Concatenate the receiver and parameter arrays and returns the
resulting array
+   *
+   * @param concat the array to append
+   * @return the concatenated array
+   */
+  public final native JsArrayString concat(JsArrayString concat) /*-{
+   return this.concat(concat);
+  }-*/;
+
+  /**
+   * Removes the last element in the array
+   *
+   * @return the remove value
+   */
+  public final native String pop() /*-{
+   return this.pop();
+  }-*/;
+
+  /**
+   * Extracts items starting from the given index to the end of the
array
+   *
+   * @param startIndex the start index
+   * @return the resulting array
+   */
+  public final native JsArrayString slice(int startIndex) /*-{
+   return this.slice(startIndex);
+  }-*/;
+
+  /**
+   * Extracts items starting from the startIndex (inclusive) to the
endIndex (exclusive)
+   *
+   * @param startIndex the startIndex
+   * @param endIndex the endIndex (negative values also allowed)
+   * @return the resulting array
+   */
+  public final native void slice(int startIndex, int endIndex) /*-{
+   this.slice(startIndex, endIndex);
+  }-*/;
+
+  /**
+   * Removes a given amount of items from the array starting with the
given index
+   *
+   * @param startIndex the start index
+   * @param removedItems the number of items to remove
+   */
+  public final native void splice(int startIndex, int removedItems) /
*-{
+ this.splice(startIndex,removedItems);
+  }-*/;
+
+  public final Iterable iterable() {
+ return new Iterable() {
+
+   public Iterator iterator() {
+   return new IteratorImpl();
+   }
+   };
+  }
+
+  private class IteratorImpl implements Iterator {
+   /*
+* i is the index of the item that will be returned on the next
call to
+* next() last is the index of the item that was returned on the
previous
+* call to next() or previous (for ListIterator), -1 if no such
item exists.
+*/
+   int i = 0, last = -1;
+
+   public boolean hasNext() {
+ return i < JsArrayString.this.length();
+   }
+
+   public String next() {
+ if (!hasNext()) {
+   throw new NoSuchElementException();
+ }
+ return JsArrayString.this.get(last = i++);
+   }
+
+   public void remove() {
+ if (last < 0) {
+   throw new IllegalStateException();
+ }
+ JsArrayString.this.splice(last, 1);
+ i = last;
+ last = -1;
+   }
+ }
 }

I don't know if it is a good idea to implement the iterable directly
and whether it's making sense for the 2 JsArray with primitive values
(Integer,Number) but that's why I'm posting here before filing an
enhancement request.

Tom

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Questions on JsArray*

[John Tamplin]

On Tue, Feb 2, 2010 at 2:16 PM, Tom  wrote:

> I have some questions and proposals around the JsArray-classes because
> they are handy when working with JSNI but I believe they could be
> improved a bit.
>
> a) Why are not all native methods provided through the wrapper.
>

One problem is that given how JSOs work, using a name on a parent class
means no subclass can have a method of that name.  Thus, you want to be very
careful about adding methods to a JSO class that is intended to be
subclassed.

A reasonable option would be to add a final subclass which does have those
methods, and you can freely cast any JSO to that class when you need to use
those methods.

-- 
John A. Tamplin
Software Engineer (GWT), Google

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Questions on JsArray*

[Tom Schindl]

On Tue, Feb 2, 2010 at 8:19 PM, John Tamplin  wrote:
> On Tue, Feb 2, 2010 at 2:16 PM, Tom  wrote:
>>
>> I have some questions and proposals around the JsArray-classes because
>> they are handy when working with JSNI but I believe they could be
>> improved a bit.
>>
>> a) Why are not all native methods provided through the wrapper.
>
> One problem is that given how JSOs work, using a name on a parent class
> means no subclass can have a method of that name.  Thus, you want to be very
> careful about adding methods to a JSO class that is intended to be
> subclassed.
> A reasonable option would be to add a final subclass which does have those
> methods, and you can freely cast any JSO to that class when you need to use
> those methods.

Thanks for your response. You are right. I didn't thought about the
fact that someone could have already subclassed this base
implementation and would be broken with such a changes.

Anyways I'd volunteer to implement the needed classes if you decide
that this is a good idea.

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] TextBoxBase to implement HasDirection instead of its children

[Tomer Greenberg]

Hello gwters,

I'm going to add some BiDi functionality to TextBox and TextArea. Given that
their parent, TextBoxBase, doesn't implement HasDirection, this has to be
done (in an identical manner) for TextBox and TextArea separately. But then,
why won't TextBoxBase implement HasDirection instead of its children? This
way we could save a lot of code duplication, and it's also reasonable - if
it has text, it also has direction.

Any objections?

Thanks

Tomer

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] TextBoxBase to implement HasDirection instead of its children

[Ray Ryan]

Extending TextBoxBase sounds perfectly reasonable, but what exactly are you
proposing to implement there?

On Tue, Feb 2, 2010 at 10:58 AM, Tomer Greenberg wrote:

> Hello gwters,
>
> I'm going to add some BiDi functionality to TextBox and TextArea. Given
> that their parent, TextBoxBase, doesn't implement HasDirection, this has to
> be done (in an identical manner) for TextBox and TextArea separately. But
> then, why won't TextBoxBase implement HasDirection instead of its children?
> This way we could save a lot of code duplication, and it's also reasonable -
> if it has text, it also has direction.
>
> Any objections?
>
> Thanks
>
> Tomer
>
>
>  --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors




-- 
I wish this were a Wave

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] [google-web-toolkit] r7520 committed - Add missing merge record.

[codesite-noreply]

Revision: 7520
Author: j...@google.com
Date: Tue Feb  2 13:02:43 2010
Log: Add missing merge record.

http://code.google.com/p/google-web-toolkit/source/detail?r=7520

Modified:
 /releases/2.0/branch-info.txt

===
--- /releases/2.0/branch-info.txt   Mon Feb  1 06:10:29 2010
+++ /releases/2.0/branch-info.txt   Tue Feb  2 13:02:43 2010
@@ -1463,3 +1463,9 @@
 tr...@7513 was merged into this branch
   Prevent MenuBar from losing focus when navigating to a new submenu.
   svn merge --ignore-ancestry -c 7513  
http://google-web-toolkit.googlecode.com/svn/trunk .

+
+(out of order)
+tr...@7354 was merged into this branch
+  Fix cookie encoding problem
+  svn merge --ignore-ancestry -c 7354 \
+  https://google-web-toolkit.googlecode.com/svn/trunk .

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Questions on JsArray*

[Bruce Johnson]

@John T: Are you saying we wouldn't want those methods on JsArray classes,
though? Seems like that's an appropriate place to put them. People don't
usually subclass containers like that (do they?).

On Tue, Feb 2, 2010 at 2:50 PM, Tom Schindl  wrote:

> On Tue, Feb 2, 2010 at 8:19 PM, John Tamplin  wrote:
> > On Tue, Feb 2, 2010 at 2:16 PM, Tom  wrote:
> >>
> >> I have some questions and proposals around the JsArray-classes because
> >> they are handy when working with JSNI but I believe they could be
> >> improved a bit.
> >>
> >> a) Why are not all native methods provided through the wrapper.
> >
> > One problem is that given how JSOs work, using a name on a parent class
> > means no subclass can have a method of that name.  Thus, you want to be
> very
> > careful about adding methods to a JSO class that is intended to be
> > subclassed.
> > A reasonable option would be to add a final subclass which does have
> those
> > methods, and you can freely cast any JSO to that class when you need to
> use
> > those methods.
>
> Thanks for your response. You are right. I didn't thought about the
> fact that someone could have already subclassed this base
> implementation and would be broken with such a changes.
>
> Anyways I'd volunteer to implement the needed classes if you decide
> that this is a good idea.
>
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Questions on JsArray*

[John Tamplin]

On Tue, Feb 2, 2010 at 4:05 PM, Bruce Johnson  wrote:

> @John T: Are you saying we wouldn't want those methods on JsArray classes,
> though? Seems like that's an appropriate place to put them. People don't
> usually subclass containers like that (do they?).


Since we didn't make them final, I am sure someone has subclassed them.

I am fine with adding them there since we have most of the others, but I do
think it will break some people.

-- 
John A. Tamplin
Software Engineer (GWT), Google

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Restore UiBinderUtilTest

[rjrjr]

Reviewers: jgw,

Message:
Review, please

Description:
Bring back UiBinderUtilTest after fixing IE6 failure in testDetach. Was
checking for null parentNode instead of parentElement,and on ie6 you
still have the former after the latter dumps you.

Test was rolled back in svn tr...@6318.


Please review this at http://gwt-code-reviews.appspot.com/136802

Affected files:
  M svn/user/test/com/google/gwt/uibinder/UiBinderGwtSuite.java
  A svn/user/test/com/google/gwt/uibinder/client/UiBinderUtilTest.java


--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] [google-web-toolkit] r7521 committed - Adds explicit pure Java test support to GWTTestCase, via a setter....

[codesite-noreply]

Revision: 7521
Author: guillaume.ry...@google.com
Date: Tue Feb  2 13:27:34 2010
Log: Adds explicit pure Java test support to GWTTestCase, via a setter.
Calling setForcePureJava(true) on a GWTTestCase forces running the test in  
pure Java mode (non-GWT). This feature has the same effect than returning  
null in getModuleName(), with the major difference that it can be called by  
test suite builders (which cannot reliably subclass tests in a generic way).

Fixes bug: gwtSetUp and gwtTearDown should be called in pure Java mode.
Also hardens existing JUnit tests to check that GWTTestCase tests are run  
in client or pure Java mode, as appropriate.


Review by: scottb, amitmanjhi

http://code.google.com/p/google-web-toolkit/source/detail?r=7521

Added:
 /trunk/user/test/com/google/gwt/junit/client/ForcePureJavaTest.java
 /trunk/user/test/com/google/gwt/junit/client/NullModuleNameTest.java
Modified:
 /trunk/user/src/com/google/gwt/junit/client/GWTTestCase.java
  
/trunk/user/super/com/google/gwt/junit/translatable/com/google/gwt/junit/client/GWTTestCase.java

 /trunk/user/test/com/google/gwt/junit/NonGwtTestSuite.java
 /trunk/user/test/com/google/gwt/junit/client/ModuleOneTest.java
 /trunk/user/test/com/google/gwt/junit/client/ModuleOneTest2.java
 /trunk/user/test/com/google/gwt/junit/client/ModuleTwoTest.java

===
--- /dev/null
+++ /trunk/user/test/com/google/gwt/junit/client/ForcePureJavaTest.java	Tue  
Feb  2 13:27:34 2010

@@ -0,0 +1,58 @@
+/*
+ * Copyright 2010 Google Inc.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License"); you may  
not
+ * use this file except in compliance with the License. You may obtain a  
copy of

+ * the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,  
WITHOUT

+ * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+ * License for the specific language governing permissions and limitations  
under

+ * the License.
+ */
+package com.google.gwt.junit.client;
+
+import com.google.gwt.core.client.GWT;
+
+/**
+ * Test case running in pure Java mode (non-GWT) due to a call to
+ * {...@link GWTTestCase#setForcePureJava}.
+ */
+public class ForcePureJavaTest extends GWTTestCase {
+
+  private int gwtSetUpCalls;
+
+  public ForcePureJavaTest() {
+setForcePureJava(true);
+  }
+
+  @Override
+  public String getModuleName() {
+return "invalid.module";
+  }
+
+  @Override
+  protected void gwtSetUp() throws Exception {
+gwtSetUpCalls++;
+super.gwtSetUp();
+  }
+
+  public void testGwtSetUpCalled() {
+assertEquals(1, gwtSetUpCalls);
+  }
+
+  public void testIsNotClient() {
+assertFalse(GWT.isClient());
+  }
+
+  public void testSetForcePureJava_inTestMethod() {
+setForcePureJava(false);
+  }
+
+  public void testIsNotClient_afterChangeForcePureJavaInTest() {
+assertFalse(GWT.isClient());
+  }
+}
===
--- /dev/null
+++ /trunk/user/test/com/google/gwt/junit/client/NullModuleNameTest.java	 
Tue Feb  2 13:27:34 2010

@@ -0,0 +1,46 @@
+/*
+ * Copyright 2010 Google Inc.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License"); you may  
not
+ * use this file except in compliance with the License. You may obtain a  
copy of

+ * the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,  
WITHOUT

+ * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+ * License for the specific language governing permissions and limitations  
under

+ * the License.
+ */
+package com.google.gwt.junit.client;
+
+import com.google.gwt.core.client.GWT;
+
+/**
+ * Test case running in pure Java mode (non-GWT) due to {...@link  
#getModuleName}

+ * returning null.
+ */
+public class NullModuleNameTest extends GWTTestCase {
+
+  private int gwtSetUpCalls;
+
+  @Override
+  public String getModuleName() {
+return null;
+  }
+
+  @Override
+  protected void gwtSetUp() throws Exception {
+gwtSetUpCalls++;
+super.gwtSetUp();
+  }
+
+  public void testGwtSetUpCalled() {
+assertEquals(1, gwtSetUpCalls);
+  }
+
+  public void testIsNotClient() {
+assertFalse(GWT.isClient());
+  }
+}
===
--- /trunk/user/src/com/google/gwt/junit/client/GWTTestCase.java	Thu Jan 28  
08:39:11 2010
+++ /trunk/user/src/com/google/gwt/junit/client/GWTTestCase.java	Tue Feb  2  
13:27:34 2010

@@ -163,6 +163,15 @@
*/
   protected TestResult testResult = null;

+  /**
+   * Whether this test case should be always run in pure Java mode  
(non-GWT).

+   * Setting this to true has the same effect as returning
+   * null in {...@link #getModuleName}.
+   *
+   * @see #isPureJava
+   */
+  private boolean for

[gwt-contrib] [google-web-toolkit] r7522 committed - Create 2.0.1 release tag.

[codesite-noreply]

Revision: 7522
Author: j...@google.com
Date: Tue Feb  2 17:25:02 2010
Log: Create 2.0.1 release tag.

http://code.google.com/p/google-web-toolkit/source/detail?r=7522

Added:
 /tags/2.0.1

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Announcing GWT 2.0.1

[Miguel Méndez]

The GWT 2.0.1 point release is now available for download. It contains fixes
for bugs found in the 2.0.0 release.

Potentially breaking changes and fixes

   - Fixed a bug in how code generators collect method arguments from
   generated source, which impacted the Messages interfaces generated for
   UiBinder template files. In GWT 2.0, such argument names were incorrectly
   changed to ARGn. Most GWT applications will be unaffected, but external
   systems relying on these names may need to be updated.
   - The development mode server will, by default, only bind to localhost
   which will break cross-machine debugging. You can get the old behavior by
   specifying -bindAddress 0.0.0.0. Please see issue
(#4322)
   for more details. For webAppCreator-generated ant files, you can pass this
   with ant -Dgwt.args="-bindAddress 0.0.0.0" devmode.
   - The CurrencyList/CurrencyData APIs are now public - if you were relying
   upon these classes in their non-public location, you should only need to
   update your imports.

Noteworthy Fixed Issues

   - UiBinder Image class with resource attribute, removes styles on that
   image 
(#4415
   )
   - Widgets lose focus if its placed on FocusPanel (Opera, Safari)
(#1471
   )
   - Standard.css missing new layout styles
(#4429
   )
   - Remove method in SplitLayoutPanel is broken
(#4217
   )
   - Splitter constructor hard codes the background color of the splitter to
   white 
(#4335
   )
   - Image should provide method to set alternative text
(#4335
   )
   - CssResource cannot parse unescaped '-', '_' in class selectors and
   unknown at-rules
(#3946
   )
   - Focusable implementation breaks ScrollPanels in Safari
(#1313
   )
   - RequestBuilder restricted to GET and POST
(#3388
   )
   - HTMLTable.Cell.getElement() calls getCellFormatter().getElement() with
   row and column swapped RequestBuilder restricted to GET and POST
(#3757
   )
   - MenuBar steals focus when hovered
(#3884
   )
   - TabLayoutPanel tabs don't line up properly on IE
(#4447
   )
   - webAppCreator produces ant build files which support the gwt.args
   property for passing additional flags to the gwtc and devmode rules, such as
   ant -Dgwt.args="-style PRETTY" gwtc.

See the GWT issue tracker for the complete list of bug fixes and
enhancements
in
this release.

--

Miguel on behalf of the GWT Team

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: Announcing GWT 2.0.1

[jarrod]

Hey great job! Thanks a mil!

On Feb 2, 9:01 pm, Miguel Méndez  wrote:
> The GWT 2.0.1 point release is now available for download. It contains fixes
> for bugs found in the 2.0.0 release.
>
> Potentially breaking changes and fixes
>
>    - Fixed a bug in how code generators collect method arguments from
>    generated source, which impacted the Messages interfaces generated for
>    UiBinder template files. In GWT 2.0, such argument names were incorrectly
>    changed to ARGn. Most GWT applications will be unaffected, but external
>    systems relying on these names may need to be updated.
>    - The development mode server will, by default, only bind to localhost
>    which will break cross-machine debugging. You can get the old behavior by
>    specifying -bindAddress 0.0.0.0. Please see issue
> (#4322)
>    for more details. For webAppCreator-generated ant files, you can pass this
>    with ant -Dgwt.args="-bindAddress 0.0.0.0" devmode.
>    - The CurrencyList/CurrencyData APIs are now public - if you were relying
>    upon these classes in their non-public location, you should only need to
>    update your imports.
>
> Noteworthy Fixed Issues
>
>    - UiBinder Image class with resource attribute, removes styles on that
>    image 
> (#4415
>    )
>    - Widgets lose focus if its placed on FocusPanel (Opera, Safari)
> (#1471
>    )
>    - Standard.css missing new layout styles
> (#4429
>    )
>    - Remove method in SplitLayoutPanel is broken
> (#4217
>    )
>    - Splitter constructor hard codes the background color of the splitter to
>    white 
> (#4335
>    )
>    - Image should provide method to set alternative text
> (#4335
>    )
>    - CssResource cannot parse unescaped '-', '_' in class selectors and
>    unknown at-rules
> (#3946
>    )
>    - Focusable implementation breaks ScrollPanels in Safari
> (#1313
>    )
>    - RequestBuilder restricted to GET and POST
> (#3388
>    )
>    - HTMLTable.Cell.getElement() calls getCellFormatter().getElement() with
>    row and column swapped RequestBuilder restricted to GET and POST
> (#3757
>    )
>    - MenuBar steals focus when hovered
> (#3884
>    )
>    - TabLayoutPanel tabs don't line up properly on IE
> (#4447
>    )
>    - webAppCreator produces ant build files which support the gwt.args
>    property for passing additional flags to the gwtc and devmode rules, such 
> as
>    ant -Dgwt.args="-style PRETTY" gwtc.
>
> See the GWT issue tracker for the complete list of bug fixes and
> enhancements
> in
> this release.
>
> --
>
> Miguel on behalf of the GWT Team

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: Comment on DataBackedWidgetsDesign in google-web-toolkit

[codesite-noreply]

Comment by andrew.pietsch:

...and while I'm at it, is anything like (or preferably better than)  
Swing's ListSelectionModel planned?  It'd also like to be able to veto  
selection events if possible.



For more information:
http://code.google.com/p/google-web-toolkit/wiki/DataBackedWidgetsDesign

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors