Thanks Roberto, I'll give that a shot. I normally work with Java 7, but we
want our code to work with anyone who chooses to use Java 6 as well - and I
surmised that GWT had the same goal.
Would it make sense to consider a warning indicating that the flag is
needed with Java 6, or auto-detecting
You should be able to invoke devmode with -sourceLevel 6.
Roberto Lublinerman | Software Engineer | rlu...@google.com | 408-500-9148
On Fri, Nov 8, 2013 at 3:31 PM, Colin Alworth wrote:
> I'm not yet convinced that this isn't either a) a workspace issue or b) a
> decision the community reached
I'm not yet convinced that this isn't either a) a workspace issue or b) a
decision the community reached and I missed, but I figured I should stick
it out there and see if someone can correct me.
I've just brought our project up to date with GWT 2.6.0-rc1 from maven, and
I can verify that the c
gwt.widget is not used at all internally, We have our own internal widget
set mostly based on gwt.user.client.ui w/ appearance pattern and that is
what Groups is very likely using.
Unless we have a full set of cell based widgets, I don't see much value in
moving it into gwt.user and will just add
On Thu, Nov 7, 2013 at 9:28 PM, Li Bin wrote:
> Is it possible for 2.6 to support IE11 in the final release ?
>
It's unclear to me what you mean by supporting IE11. If you know of issues
between GWT and IE11, please report them at
https://code.google.com/p/google-web-toolkit/issues/list.
Howev
Is it possible for 2.6 to support IE11 in the final release ?
Many thanks
On Thursday, November 7, 2013 5:00:05 PM UTC+8, Daniel Kurka wrote:
>
> I think we still need to update the release notes:
> http://www.gwtproject.org/release-notes.html
>
> Did we already track stuff that needs to go in