Re: [gwt-contrib] Packaging issue: org.json and RequestFactory

I wouldn't be opposed to having differing rules for the GWT SDK package downloadable at code.google.com and the Maven artifacts. AFAIK, the original idea of bundling them into gwt-user.jar (and gwt-dev.jar) was to make things simpler for users (just put gwt-dev and gwt-user in the

[gwt-contrib] Change in gwt[master]: Fix an infinite loop in RPC deserialization due to type vari...

James Nelson has posted comments on this change. Change subject: Fix an infinite loop in RPC deserialization due to type variable cycles. .. Patch Set 3: Code-Review+1 (4 comments

[gwt-contrib] Change in gwt[master]: Fix an infinite loop in RPC deserialization due to type vari...

James Nelson has posted comments on this change. Change subject: Fix an infinite loop in RPC deserialization due to type variable cycles. .. Patch Set 4: Code-Review+1 -- To view, visit https://gwt-review.googlesource.com

[gwt-contrib] Change in gwt[master]: Prevent dev mode breakage when lots of jso classes are used.

James Nelson has uploaded a new change for review. https://gwt-review.googlesource.com/2210 Change subject: Prevent dev mode breakage when lots of jso classes are used. .. Prevent dev mode breakage when lots of jso classes

[gwt-contrib] Change in gwt[master]: Prevent dev mode breakage when lots of jso classes are used.

James Nelson has posted comments on this change. Change subject: Prevent dev mode breakage when lots of jso classes are used. .. Patch Set 1: (1 comment) Not sure if it helps to move from rietveld to here, but I moved

[gwt-contrib] Change in gwt[master]: Prevent dev mode breakage when lots of jso classes are used.

James Nelson has uploaded a new patch set (#2). Change subject: Prevent dev mode breakage when lots of jso classes are used. .. Prevent dev mode breakage when lots of jso classes are used. Elemental introduces a lot of native

[gwt-contrib] Change in gwt[master]: Prevent dev mode breakage when lots of jso classes are used.

James Nelson has posted comments on this change. Change subject: Prevent dev mode breakage when lots of jso classes are used. .. Patch Set 2: I rebased on master, but couldn't switch username to give john proper credit 'cos

[gwt-contrib] Change in gwt[master]: Prevent dev mode breakage when lots of jso classes are used.

James Nelson has posted comments on this change. Change subject: Prevent dev mode breakage when lots of jso classes are used. .. Patch Set 2: (1 comment) File dev/core/src

[gwt-contrib] Change in gwt[master]: Prevent dev mode breakage when lots of jso classes are used.

James Nelson has posted comments on this change. Change subject: Prevent dev mode breakage when lots of jso classes are used. .. Patch Set 2: (2 comments) Marked points in code that may need to change / be checked against

[gwt-contrib] Change in gwt[master]: Fixes TypeError in keys() for JsMapFromStringTo in dev mode.

James Nelson has posted comments on this change. Change subject: Fixes TypeError in keys() for JsMapFromStringTo in dev mode. .. Patch Set 1: This needs to be rebased on top of master; it was submitted without running git

[gwt-contrib] Re: gwt rebranding

Here is an extremely crude mockup of an idea I had... For those talking about how it is pronounced Gwit, but still spelled GWT, I suggest some play on words using the T on the G. https://lh4.googleusercontent.com/-Zb4YtUAo39k/UULrfkz_5MI/Ans/a8LSWrgh1UM/s1600/gwt.png Also, I hope it's

Re: [gwt-contrib] Re: gwt rebranding

/What_are_some_animals_that_begin_with_the_letter_G I like very much Goat ;) On Fri, Mar 15, 2013 at 11:38 AM, James Nelson ja...@wetheinter.netjavascript: wrote: Here is an extremely crude mockup of an idea I had... For those talking about how it is pronounced Gwit, but still spelled GWT

[gwt-contrib] Change in gwt[master]: add Class.getSimpleName to gwt emulation

James Nelson has posted comments on this change. Change subject: add Class.getSimpleName to gwt emulation .. Patch Set 1: If we're going to include simple name, how about throwing in Package as well; when obfuscation

[gwt-contrib] Change in gwt[master]: Implemented handling of GwtIncompatible annotations.

James Nelson has posted comments on this change. Change subject: Implemented handling of GwtIncompatible annotations. .. Patch Set 8: This feature is so awesome, it's a shame it might have to wait for 2.6.0... My project

[gwt-contrib] Change in gwt[master]: Prevent dev mode breakage when lots of jso classes are used.

James Nelson has posted comments on this change. Change subject: Prevent dev mode breakage when lots of jso classes are used. .. Patch Set 3: Code-Review-1 (3 comments) This patch doesn't actually fix the underlying issue

[gwt-contrib] Change in gwt[master]: Prevent dev mode breakage when lots of jso classes are used.

James Nelson has posted comments on this change. Change subject: Prevent dev mode breakage when lots of jso classes are used. .. Patch Set 3: Yes, this patch will not be able to fix the actual underlying issue; the best

[gwt-contrib] Change in gwt[master]: Add callbacks to Super Dev Mode to find out when a compile s...

James Nelson has posted comments on this change. Change subject: Add callbacks to Super Dev Mode to find out when a compile starts and finishes, and an alternate main() that can be called after parsing options. .. Patch

[gwt-contrib] Change in gwt[master]: Including the module name in the magic sourceURL comment in ...

James Nelson has posted comments on this change. Change subject: Including the module name in the magic sourceURL comment in code generated by the iframe linker. This gives a bit more context in the browser debugger, and is especially important when including multiple GWT applications

[gwt-contrib] Change in gwt[master]: Remove dependency from GWT-JUnit on deRPC

James Nelson has posted comments on this change. Change subject: Remove dependency from GWT-JUnit on deRPC .. Patch Set 2: RPCSuite is adding a number of deRPC test suites at the bottom of the test

[gwt-contrib] Change in gwt[master]: Remove dependency from GWT-JUnit on deRPC

James Nelson has posted comments on this change. Change subject: Remove dependency from GWT-JUnit on deRPC .. Patch Set 2: Sorry to spam, but the fix would be to trace the test classes extending HybridServiceServlet

[gwt-contrib] Change in gwt[master]: Remove dependency from GWT-JUnit on deRPC

James Nelson has posted comments on this change. Change subject: Remove dependency from GWT-JUnit on deRPC .. Patch Set 2: The tests that were commented out simply extend the other tests that run through a normal

[gwt-contrib] Change in gwt[master]: Temporarily disable deRPC tests.

James Nelson has posted comments on this change. Change subject: Temporarily disable deRPC tests. .. Patch Set 2: Code-Review+1 Looks good, but after checking out the tests that are disabled, I've noticed the only

[gwt-contrib] Change in gwt[master]: Adds support for lower case encoding names to String

James Nelson has posted comments on this change. Change subject: Adds support for lower case encoding names to String .. Patch Set 2: (1 comment) lgtm; made a nit for production mode performance (using native js regex

[gwt-contrib] Change in gwt[master]: Adds support for lower case encoding names to String

James Nelson has posted comments on this change. Change subject: Adds support for lower case encoding names to String .. Patch Set 2: Code-Review+1 -- To view, visit https://gwt-review.googlesource.com/3000 To unsubscribe

[gwt-contrib] Change in gwt[master]: Adds support for lower case encoding names to String

James Nelson has posted comments on this change. Change subject: Adds support for lower case encoding names to String .. Patch Set 2: Aye, my tests on the regex show it way slower, even with cached regex matcher

[gwt-contrib] Re: Initial support for @GwtCreate (code-gen methods)

I like it! I've got a few comments / ideas, but overall, I'm glad to see more work being done to empower core GWT functionality. Note that the @GwtCreate class parameters aren't replaced by GwtCreateFactory as was originally suggested by Ray Cromwell. This provides access to actual

[gwt-contrib] Re: Initial support for @GwtCreate (code-gen methods)

Thanks! I think this proposal is the most conservative way to enhance GWT.create(). A more radical approach would be to forget GWT.create() and imitate what scala macros do, as was suggested by Gotktug: @Macro(SumGenerator.class) int sum(int arg0, int arg1) { return 0; // we

[gwt-contrib] Re: Initial support for @GwtCreate (code-gen methods)

For posterity's sake, could you drop those links off here (or are you referring to the ones Ray posted in the G+ community? The phrase javac 8 doesn't ring any bells for me). Nevermind. I just browsed the group and saw the thread. My bad. --

Re: [gwt-contrib] Google team meeting notes for August 7 (and earlier)

re: Heiko Braun it means having an optional compilation path that does not recompile the entire world (as the current monolithic compile path does) and instead tries to recompile just files (or or modules) that have changed. it is exploratory work for me right now as there are very many

Re: [gwt-contrib] Google team meeting notes for August 7 (and earlier)

So as a result, in the best possible world the maximum impact it can have on compile time, is ~50%. In practice it has a little less than that because reading and deserializing these GWT Java ASTs from disk takes some (smaller) amount of time and because in large modular projects there's

Re: [gwt-contrib] Google team meeting notes for August 7 (and earlier)

I may need to revisit some of that responsibility though, since the current GWT Eclipse plugin owns/manages the GWT compile triggering process. I'm toying with the idea of implementing this iterative compilation triggering responsibility in Maven and (since GWT shouldn't try to act like

[gwt-contrib] Quarterly Hangouts On Air

Hi all, I am just wondering if it would be possible to setup a quarterly QA hangout-on-air with steering committee members taking questions from the public, and presenting on ideas that are in the works for GWT. It would be similar to the panel held at GWT.create, except we could collect up

Re: [gwt-contrib] Quarterly Hangouts On Air

/in/borisbrudnoy , Careers 2.0 http://careers.stackoverflow.com/brudnoy) On Sun, Jan 26, 2014 at 3:41 PM, James Nelson ja...@wetheinter.netjavascript: wrote: Hi all, I am just wondering if it would be possible to setup a quarterly QA hangout-on-air with steering committee members taking

[gwt-contrib] Re: Quarterly Hangouts On Air

A reddit-style AMA would be really cool; so long as we give enough warning and promo, (like posting the event in the G+ community a month ahead of time) I'm sure it would be a hit. The questions in the moderator would probably all get asked; though seeing some of them come up in the gwt-team

[gwt-contrib] Re: I am getting ClassCastException on my app production code, but not on dev mode.

Please post to http://stackoverflow.com to get support; this group is for discussing project architecture and product development. Also, the snippet of code you've sent really doesn't mean anything by itself. Try running in superdevmode on chrome to get a more meaningful stacktrace. On Sunday,

Re: [gwt-contrib] JavaWriter API as replacement for SourceWriter family

Is there anywhere to get a sneak preview on the discussions about the future of codegen? Andres and I have both invested time in some extensions of ast-based codegen, and could really use some time and forewarning to adapt our strategy to stay future-friendly with out apis. --

Re: [gwt-contrib] JavaWriter API as replacement for SourceWriter family

There is not much more that what is already discussed earlier in the list . APT takes responsibility of codegen out of GWT compiler and get more inline with the rest of the java world and works on GWT/Android/server. That is basically what would you do if there was no TypeOracle nor

Re: [gwt-contrib] JavaWriter API as replacement for SourceWriter family

An excellent read about the trick behind Lombok, and related ast-hacking utils: http://notatube.blogspot.ca/2010/11/project-lombok-trick-explained.html -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google

Re: [gwt-contrib] JavaWriter API as replacement for SourceWriter family

SourceWriter is not incompatible with APT, just like JavaWriter is not incompatible with generators. Both take a PrintWriter where they write; SourceWriter is string-based with only a few helpers for javadoc and indent/outdent, whereas JavaWriter is more Java oriented with methods to

[gwt-contrib] Changes in monthly GWT contributor hangout

I will be returning this month, and would like to discuss how best to support java 8 emulation. Ray had sent a bullet point list of items, like having a separate super source folder for java 8 emulation and building a separate jar with those sources, but I would like to hear what the team

Re: [gwt-contrib] Re: Dropping IE8 support in useragent-less GWT

Just to toss in another use case... I develop a cross-platform java library that exposes generic apis that run on multiple platforms; each module inherits the minimum possible dependencies, and all platform-specific code is isolated from shared APIs. I never touch anything in User unless I

Re: [gwt-contrib] Re: What constitutes an acceptable emulated String.format implementation?

I know that adding more magic methods is generally frowned upon, but the advantage here is that a String literal can be made available at compile time, allowing the injection of a minimal-overhead replacement. If, for any reason, the String is not a literal, we can emit a warning about the

Re: [gwt-contrib] Jsni on String methods in GWT 2.7

I stand very much corrected. /hat tip/ I suppose I've already been using JsType so much it has begin to cloud my judgement. Hm. How ironic that the only methods unreachable to reflection-via-jsni would be private jsni methods? :-) -- You received this message because you are subscribed to

Re: [gwt-contrib] Jsni on String methods in GWT 2.7

I suppose I technically have access to the AST nodes... If I *really *wanted to I could probably find a way, but that would be exceptionally nasty, so, no thanks... -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this

Re: [gwt-contrib] Incremental compiler refreshes triggered by IDE touching files

Ok. It doesn't always happen to me, but I am using eclipse Luna on Ubuntu 14.04. I noticed it personally while testing magic method injection, but it has also happened at work with a standard 2.7 SDK. What I noticed is when I have a lot of files open, even if I am editing another file in a

Re: [gwt-contrib] Incremental compiler refreshes triggered by IDE touching files

Oh, any my work machine is Windows, and one coworker who reported it is on mac. Both work builds are on plain 2.7 -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an

[gwt-contrib] Incremental compiler refreshes triggered by IDE touching files

Whilst digging around trying to make some stuff go faster, I noticed something odd... I was getting a bunch of extra types getting marked stale at the beginning of a recompile, and at work, recompiles triggered even when no changes were made to Gwt-related files. So, a little debugging and I

Re: [gwt-contrib] Re: Elemental 2?

+1 for hacky prototype to play with. Collide was built with hacky pre Elemental1, and it was rescuable, and I may have a use case to upgrade it again to Elemental2 (plus a little other top secret magic). https://github.com/cromwellian/gwt-sandbox was where I got the hacky pre java 8 version.

[gwt-contrib] Re: System.getProperty as a replacement for replace-with, generate-with

Here is the code that is doing the selection, in ResolvePermutationDependentValues: private JExpression propertyValueExpression(JPermutationDependentValue x) { List propertyValues = props.getConfigurationProperties().getStrings(x.getRequestedValue()); String propertyValue =

[gwt-contrib] Re: System.getProperty as a replacement for replace-with, generate-with

Yup. CompilerParameters.gwt.xml: /** * Returns the binding property values to be embedded into the initial JavaScript fragment * for this permutation. (There will be one map for each soft permutation.) */ public ImmutableList>

[gwt-contrib] Re: GWTCon 2015 keynote question

So, a little late to jump in, but figured I'd add my $0.02 to this conversation. I've been hard at work building a future-oriented declarative UI DSL. Specifically, I extended the Java 8 JavaCC parser to include xml, json and css expression syntax. This allows creation of UI's like the

[gwt-contrib] Re: GWTCon 2015 keynote question

Hi Predrag; There is not currently an online demo of the framework just yet, but the prototype application being built with it is designed to make explaining complex ideas and processes as simple and as concise as possible, and it will certainly contain tutorials on how the custom elements are

[gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

Huzzah!! I'll be taking this for a spin on my week off; see if I can make custom elements completely hack free (at long last)! Many thanks good sirs. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop

[gwt-contrib] Re: Java 9

As I've mentioned elsewhere, https://plus.google.com/+JamesNelsonX/posts/gBfpBDnwV9V , java 9 support is entirely possible. When I last tried it out, it required a fair number of hacks, but it worked fine. I expect the final version of java 9 modules to require slightly fewer hacks, and for

[gwt-contrib] Re: Java 9

> > Are there specific Java9 JRE classes that we should focus on to get into > GWT? > > I didn't go through the full changelog, but I believe there have been more helper methods added to Optional and other classes; will need emul updates for sure. > Would making GWT support Java9 sources

[gwt-contrib] Re: Java 9

So, to be pedantic: Language features -> no issues there at all, since JDT happily compiles java 8 code w/ a java 9-compatible compiler. Emul updates -> standard "don't use java 9 methods if you need java 8 support" Classpathery -> Made it use ugly reflection to not require java 9 classes on

[gwt-contrib] Re: Java 9

> > > Fwiw, I think it would work, according to > https://github.com/AdoptOpenJDK/openjdk-jdk9/blob/f9129bba032f3b75be9b67f45636f76940e029a6/jdk/src/java.base/share/classes/jdk/internal/loader/ClassLoaders.java#L70-L73 > (for now, I'm not interested in supporting modules, just making GWT 2 work

[gwt-contrib] Re: Java 9

> > > It is my understanding that we use ASM to load the annotation attributes > from source classes, and then create a Proxy to load member values / > classes / enums off the classpath. JDT is not involved at all (strange > that it isn't...). > > The most likely reason we aren't using JDT

[gwt-contrib] Re: Java 9

> > > Could that work if we complemented the "instanceof URLClassLoader" with > some check for "is the system classloader" and then use > System.getProperty("java.class.path") (or the equivalent > ManagementFactory.getRuntimeMXBean().getClassPath()) to get the system > classpath entries? (do

Re: [gwt-contrib] Re: Business proposition of GWT 3.0 - what is it good for vs. other solutions out there?

Have not read the whole thread yet, but just wanted to point out a few small things. First, whole-world compilations and transforms are something I've been working on as a replacement for generator subsystem since I heard it was dying a couple years ago. I have a toy implementation working