from:"Manuel Carrasco"

Seems like gwt-dev is not in your classpath

El vie., 29 jul. 2016 a las 16:27, Frank Taffelt (<
frank.taff...@interface-projects.de>) escribió:

> thanks for the rc.
>
> updated a project coming from 2.7.0. the project is mainly based on thomas
> gwt maven-archetypes.
>
> the following build error is dumped doing an mvn package on the
> gwt-compilation step:
>
> [INFO]   [WARN] Line 39 column 7: encountered "(". Was
> expecting one of: 
> [INFO][ERROR] An internal compiler exception occurred
> [INFO] com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error
> during visit.
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JVisitor.translateException(JVisitor.java:111)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:276)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)
> [INFO]  at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:118)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JCastOperation.traverse(JCastOperation.java:72)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)
> [INFO]  at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:118)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JDeclarationStatement.traverse(JDeclarationStatement.java:49)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JModVisitor$ListContext.traverse(JModVisitor.java:88)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JModVisitor.acceptWithInsertRemove(JModVisitor.java:331)
> [INFO]  at com.google.gwt.dev.jjs.ast.JBlock.traverse(JBlock.java:92)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)
> [INFO]  at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:139)
> [INFO]  at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:135)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JMethodBody.traverse(JMethodBody.java:83)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JMethod.visitChildren(JMethod.java:785)
> [INFO]  at com.google.gwt.dev.jjs.ast.JMethod.traverse(JMethod.java:777)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)
> [INFO]  at
> com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)
> [INFO]  at
> com.google.gwt.dev.jjs.impl.UnifyAst.mainLoop(UnifyAst.java:1379)
> [INFO]  at com.google.gwt.dev.jjs.impl.UnifyAst.exec(UnifyAst.java:875)
> [INFO]  at
> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.unifyJavaAst(JavaToJavaScriptCompiler.java:1410)
> [INFO]  at
> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.constructJavaAst(JavaToJavaScriptCompiler.java:1222)
> [INFO]  at
> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.precompile(JavaToJavaScriptCompiler.java:1140)
> [INFO]  at
> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.precompile(JavaToJavaScriptCompiler.java:255)
> [INFO]  at com.google.gwt.dev.Precompile.precompile(Precompile.java:255)
> [INFO]  at com.google.gwt.dev.Precompile.precompile(Precompile.java:202)
> [INFO]  at com.google.gwt.dev.Precompile.precompile(Precompile.java:143)
> [INFO]  at com.google.gwt.dev.Compiler.compile(Compiler.java:204)
> [INFO]  at com.google.gwt.dev.Compiler.compile(Compiler.java:155)
> [INFO]  at com.google.gwt.dev.Compiler.compile(Compiler.java:144)
> [INFO]  at com.google.gwt.dev.Compiler$1.run(Compiler.java:118)
> [INFO]  at
> com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55)
> [INFO]  at
> com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50)
> [INFO]  at com.google.gwt.dev.Compiler.main(Compiler.java:125)
> [INFO] Caused by: java.lang.NoClassDefFoundError:
> org/w3c/dom/ElementTraversal
> [INFO]  at java.lang.ClassLoader.defineClass1(Native Method)
> [INFO]  at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
> [INFO]  at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> [INFO]  at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> [INFO]  at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> [INFO]  at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> [INFO]  at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> [INFO]  at java.security.AccessController.doPrivileged(Native Method)
> [INFO]  at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> [INFO]  at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> [INFO]  at

Re: [gwt-contrib] Thinking about the future: GWT 3, J2Cl, modularization, etc.

Since  3.0 details aren't yet clear enough, I agree that it should be
modular, and eventually  modules from 2.8.x could be used or ported to 3.0

So the ideal situation is that we are able to split gwt 2.8.x into as much
independent modules as possible, making GWT easier to maintain, and assign
maintainers.

I agree also with the idea of 2.8.x being a long term support product.
So to me the roadmap could be,  make 2.8.x support modules (via maven or
whatever), and split it.
IMO 2.9 might be the modular release of GWT, fully compatible with 2.8.

- Manolo



El jue., 28 jul. 2016 a las 17:57, Thomas Broyer ()
escribió:

> Hi all,
>
> We've talked about modularizing GWT for several years now, and I gave it a
> try at several occasions, with Maven, then Gradle, then Buck… and last year
> I completely gave up, knowing the J2Cl was coming which would be quite
> disruptive, with the hope that we could start on new grounds (including a
> fresh start from the built tool side; farewell Ant!). As GWT 2.8.0 is
> approaching (RC1 is imminent), I think it's time we start talking about
> that GWT 3 future with J2Cl at its core.
>
> As I understand it, Google would rather have things as "exploded" as
> possible: J2Cl and emulation in one repo (or possibly even split in 2),
> then each "module" in its own repo (elemental2, etc.) with its own
> maintainers and moving at its own pace (and possibly even its own
> contributing guidelines: using GitHub+Travis? Gerrit+Jenkins?
> GitHub+GerritHub+Travis? and its own build tools: Maven vs. Gradle vs.
> whatever)
> First: I'm all for it!
> The way I see it, Google would opensource J2Cl, and we (the community)
> would start moving bits from GWT out to their own repos (either removing
> them from GWT proper –the challenge then is to make sure it stays
> compatible with both GWT 2.x and J2Cl/GWT 3.x– or duplicating them –the
> challenge being to keep both versions in sync, as we don't want to abandon
> GWT 2.8.x users; but 2.x maintenance is another, though closely related,
> topic).
>
> It's been suggested during the last Steering Committee meeting that the
> community (i.e. "outside Google") may want to package/bundle many such
> things together into "GWT 3.x" releases; probably a bit similar to how
> Eclipse cuts yearly releases bundling many plugins/features together into
> downloadable packages.
> On one hand, it requires picking (or cutting?) specific "releases" of each
> module to be bundled and testing them all together to make sure they all
> play well with each other, which is relatively time-consuming (and one
> reason Google doesn't want to do it, given they don't even use "releases"
> internally but always run "from trunk").
> On the other hand, it makes it easy for users, particularly newcomers, to
> refer to their setup: “I use GWT 3.0.1” vs. “I use J2Cl x, emul y,
> elemental2 z, polymer-jsinterop i, places j, activities k, etc.”
> Also, without such bundles, what it is that we would call “GWT 3”? Would
> it become an “umbrella term” a bit like “HTML5”?
>
> There's also been pushbacks from the community that we should have
> (possibly semi-automated) releases several times a year (every month, every
> quarter, or twice a year), even with minimal testing (not as "unstable" as
> "nightlies" –which we currently have with SNAPSHOTs– but more similar to a
> "canary" release channel).
> That being said, if we use a "rather standard" build tool (Gradle?),
> people could use JitPack to "pin" a specific commit/snapshot without the
> need to have formal intermediate releases (with jitpack.yml one could
> probably build using Bazel or Buck too, after wget'ing them).
>
> So, WDYT? What should “GWT 3” look like? one bundle like today or a set of
> projects? or possibly a set of projects with a scaffolding tool (yeoman?)
> and build tool integrations?
> Also, what would gwtproject.org say? would it talk about each module? or
> leave each module's documentation to the modules themselves? (note that we
> could come up with a rule saying that each maintainer is responsible for
> updating the documentation on gwtproject.org, with someone to "unlist"
> projects that don't comply for too long). Would GWT 3 become an "ecosystem"
> around J2Cl more than a "project" by itself? (note that there are branding
> –i.e. legal– issues too around that).
>
> I, for one, would be OK with just "a set of projects" on a "practical"
> basis, though I easily admit that it probably wouldn't help "marketing" it.
>
> --
> 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
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEayHEPpGsGk1YZsAMKg_5mXwvxU7F1wJT1y9aWL-Wj8ybvxFw%40mail.gmail.com
>

Re: [gwt-contrib] Re: gwtproject.org site

About github pages with custom domains, the only minor I see is that it
does not supports https, but currently our site is not https enabled, so
not a big deal in the short time.


El vie., 29 jul. 2016 a las 13:36, Manuel Carrasco Moñino (<
man...@apache.org>) escribió:

> Nothing special, it gets the resource based in the pathinfo, decode it to
> utf-8, computes the content-type based on the extension, and writes the
> answer to the client.
>
> It is not storing any info in database, because we use google analytics
> for counting visits. The GA script is statically included in any page the
> servlet does not rewrite anything.
>
>
>
> El vie., 29 jul. 2016 a las 13:21, Jens (<jens.nehlme...@gmail.com>)
> escribió:
>
>> Why don't we use Github pages with custom domain? Never looked into the
>> code, does the servlet anything special?
>>
>> -- J.
>>
>> --
>> 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
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/ba7d3311-fb22-4729-a704-251dd49e4702%40googlegroups.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/ba7d3311-fb22-4729-a704-251dd49e4702%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAvd2JYvawwX4JBJUNXL4Ovaayqz2TCY_dMGeVHbk49%2BuQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: gwtproject.org site

Nothing special, it gets the resource based in the pathinfo, decode it to
utf-8, computes the content-type based on the extension, and writes the
answer to the client.

It is not storing any info in database, because we use google analytics for
counting visits. The GA script is statically included in any page the
servlet does not rewrite anything.



El vie., 29 jul. 2016 a las 13:21, Jens ()
escribió:

> Why don't we use Github pages with custom domain? Never looked into the
> code, does the servlet anything special?
>
> -- J.
>
> --
> 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
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/ba7d3311-fb22-4729-a704-251dd49e4702%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAsWZG4YT80j1X42dv2kdEESP_twj9odUqzNXNiLVbbBmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] gwtproject.org site

Hello all.

Due to changes in the GAE java Remote API, the uploader tool that we have
to update the gwtproject.org site is not working anymore.
Julien has updated last changes by hand (thanks Julien), but this is a
tough task and we should fix the issue.

Although I can take the time to fix the tool, I think it's time to propose
different options that make the deploy process simpler.
The system we have right now comes from the ages when GAE was almost the
only option in google infra to deploy web sites. We are storing static data
in the DataStore, and it is served by a dedicated servlet, using custom
code to index the site using  key values.

Since all the data we serve from gwtproject.org are static files, I would
propose to use either Google Cloud Storage or Compute Engine services.
- Cloud Storage makes easy and fast deploy and serve static content.
- Compute Engine needs more setup, but it's more versatile in the sense
that we can deploy demo web apps running anything in server side. Also we
already have an instance where we run the CI.

More options? thoughts?

- Manolo

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAvr%2BMp%2B8x2AWp3kYWt%3DcD3eHUhXvfkQFS94P-yQwK%2BZ0A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.8 RC1 Help with testing

2016-07-20 Thread Manuel Carrasco Moñino

I don't see 2.8.0-rc1 anywhere,  what is the branch/tag/commit cut I have
to use ?

El mié., 20 jul. 2016 a las 19:07, Manuel Carrasco Moñino (<
man...@apache.org>) escribió:

> I can help with windows testing as well on Friday.
> Brandon let me know what platforms are you going to test, I have XP with
> IE8, Win8 IE10, and Win8.1 IE11,  ready machines with everything set for
> GWT, but I don't have any win7
>
> - Manolo
>
> El mié., 20 jul. 2016 a las 17:41, Brandon Donnelson (<
> branflake2...@gmail.com>) escribió:
>
>> I can work on some of the windows testing. I've scheduled time for
>> Thursday and will continue on Friday if needed.
>>
>>
>> https://docs.google.com/spreadsheets/d/1DmF8V3fSxN1N2UgQ9zToZz6xCwtx53lOSy8_u1xTC6Q
>>
>> -Brandon
>>
>> On Wednesday, July 20, 2016 at 1:53:36 AM UTC-7, Thomas Broyer wrote:
>>>
>>> I'll test on Linux / Chrome.
>>>
>>> On Wednesday, July 20, 2016 at 3:09:08 AM UTC+2, Daniel Kurka wrote:
>>>>
>>>> Hi all,
>>>>
>>>> we have build the preliminary GWT 2.8.0-rc1 version and now need help
>>>> with DOA testing (making sure its not dead on arrival).
>>>>
>>>> We are currently missing testers for:
>>>>
>>>> Linux / Chrome
>>>> Windows 7 / IE8/IE9
>>>> Windows 7 / IE 10
>>>> Windows 7 / IE 11
>>>>
>>>> If you are interested in spending ~1h in testing the new GWT release,
>>>> please reach out to me.
>>>>
>>>> -Daniel
>>>>
>>>> --
>> 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
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/0c51fdb5-2f3d-4952-ada2-b9c9fdeffd7d%40googlegroups.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/0c51fdb5-2f3d-4952-ada2-b9c9fdeffd7d%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAuVBry6rGTbF_RuCAKv_9SXogPvVKrvoQWaCjkEfy%3D%3DBA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Current snapshots failing with JDK 7

2016-07-03 Thread Manuel Carrasco Moñino

I can configure the existing jenkins build (gwt-java7) using jdk7 to upload
the snapshot instead of the current one (gwt) which uses jdk8. I guess it
should fix the problem

El dom., 3 jul. 2016 a las 1:07, Thomas Broyer ()
escribió:

> Hi all,
>
> Current snapshots fail with JDK 7:
> [INFO] [INFO]Tracing compile failure path for type
> 'java.util.Comparator'
> [INFO] [INFO]   [ERROR] Errors in
> 'jar:file:/home/travis/build/tbroyer/gwt-maven-plugin/target/it-repo/com/google/gwt/gwt-user/2.8.0-SNAPSHOT/gwt-user-2.8.0-SNAPSHOT.jar!/com/google/gwt/emul/java/util/Comparator.java'
> [INFO] [INFO]  [ERROR] Line 1: The type
> java.lang.invoke.SerializedLambda cannot be resolved. It is indirectly
> referenced from required .class files
>
> (see https://travis-ci.org/tbroyer/gwt-maven-plugin/jobs/141919077#L410)
>
> Is this because the snaphots are built with JDK 8 (see
> http://www.draconianoverlord.com/2014/04/01/jdk-compatibility.html for
> instance) or that we actually no longer support JDK 7 (without noticing it)
> ?
>
> --
> 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
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/bb56d241-c198-4bb6-9612-c5bd3ccfd6cc%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAvmuBCgXVjVkvSjLxOyY2h0gbhxLRWJVMY31jzkpOoL2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Experimental release of Elemental2

2016-07-02 Thread Manuel Carrasco Moñino

I'm wondering if it would be possible to have type-safe convenience methods
for creating elements, so as the user does not have to provide the string
tag name, nor cast the object, maybe something like :

HTMLButtonElement button = HTMLButtonElement.createElement();

instead of

HTMLButtonElement button = (HTMLButtonElement)
document.createElement("button");



El sáb., 2 jul. 2016 a las 4:38, 'Goktug Gokdogan' via GWT Contributors (<
google-web-toolkit-contributors@googlegroups.com>) escribió:

> Closure extern definition uses a union type here:
>
> https://github.com/google/closure-compiler/blob/master/externs/browser/w3c_event.js#L34
>
> So it accepts either EventListener interface or a function.
>
> When we see a union type, we generate overloads for each type so Elemental
> should provide overloads that includes both. And it seems like it does. If
> not please let us know.
>
> On Fri, Jul 1, 2016 at 3:39 AM, Jens  wrote:
>
>>
>> Thanks, now makes sense. I get confused with the JsFunction
>>> JsType(native) because elemental2 has some callbacks as JsFunction and
>>> others as JsType(native), now an actual elemental2 question; what criteria
>>> is used to apply JsFunction (ex. elemental2.Node.AddEventListenerCallback)
>>> instead of JsType (ex. elemental2.JsType)?
>>>
>>
>> I think its the result of definition of EventTarget.addEventListener():
>>
>> *listener - The object that receives a notification (an object that
>> implements the Event
>>  interface) when an
>> event of the specified type occurs. This must be an object implementing the
>> EventListener
>>  interface,
>> or simply a JavaScript function
>> .*
>>
>> The EventListener interface is a defined API and thus a @JsType(isNative
>> = true) interface has been generated. But to conform to "or simply a
>> JavaScript function" there is also an AddEventListenerCallback that is a
>> @JsFunction. Not sure if this distinction has any real value, in a hand
>> coded elemental2 I would have only created a @JsFunction interface
>> EventListener
>>
>> -- J.
>>
>> --
>> 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
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/73b36bdb-c496-4768-a221-21fe8b5a437c%40googlegroups.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA0ZfCbS%2Bnwtre0QuAnhDdLYz%2B3LuzXqD3WqoWqK%3DFe%2BEg%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAsU1UZgkh3cjG1HPkpRBJfaiEh631fq9WdS_RQg8Z_Leg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Error: cannot extend JsFunction implementation

2016-05-24 Thread Manuel Carrasco Moñino

Gotcha. So the javadoc should say something about this constrain

Thanks

El mar., 24 may. 2016 a las 8:21, 'Goktug Gokdogan' via GWT Contributors (<
google-web-toolkit-contributors@googlegroups.com>) escribió:

> Works as intended.
>
> Any form of polymorphism is avoided in JsFunction design so that we could
> generate a simple javascript function out of it:
> https://gwt-review.googlesource.com/#/c/12810/
>
> On Mon, May 23, 2016 at 10:50 PM, Manuel Carrasco Moñino <
> man...@apache.org> wrote:
>
>>
>> Is there any reason why a Class implementing a JsFunction cannot be
>> extended or it is a bug?
>>
>> In the @JsFunction documentation there is nothing about this constrain.
>>
>> @JsFunction
>> interface I {
>>   void call(...);
>> }
>> class A implements I {...}
>> class B extends A {...}
>>
>> [ERROR] : 'A' cannot extend JsFunction implementation 'B'.
>>
>>
>> Thanks
>> - Manolo
>>
> --
>> 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
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAuQi8iTbWcgUcMLSHOgYKbQqNOhwMAG-tLJFtZkTEqpig%40mail.gmail.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAuQi8iTbWcgUcMLSHOgYKbQqNOhwMAG-tLJFtZkTEqpig%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA0%3DJCCedeNcM73ae9RYCMP0%3D_vtvwo9f0C2WT%3DyjQMA%2Bg%40mail.gmail.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA0%3DJCCedeNcM73ae9RYCMP0%3D_vtvwo9f0C2WT%3DyjQMA%2Bg%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAsKXynNh39Y5VA-UU8w8yJVKd7Asof%2BBzDGGZL6%3DOJ2aQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Error: cannot extend JsFunction implementation

2016-05-23 Thread Manuel Carrasco Moñino

Is there any reason why a Class implementing a JsFunction cannot be
extended or it is a bug?

In the @JsFunction documentation there is nothing about this constrain.

@JsFunction
interface I {
  void call(...);
}
class A implements I {...}
class B extends A {...}

[ERROR] : 'A' cannot extend JsFunction implementation 'B'.


Thanks
- Manolo

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAuQi8iTbWcgUcMLSHOgYKbQqNOhwMAG-tLJFtZkTEqpig%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Compiler failing with java 7

2016-02-18 Thread Manuel Carrasco Moñino

Agree, there are some corner cases, but normally gwt developers have to
deal with a bunch of differences between java and gwt.

Anyway I think that it's better that SDK7 users assume some language issues
than not be able to compile their projects at all.

On Thu, Feb 18, 2016 at 10:17 AM, 'Daniel Kurka' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> We have seen issues internally where some code would be a compile error in
> Java8 but not in Java7 (especially around type checking). This setup will
> leave users vulnerable to this since their code will compile in their IDE,
> but will fail GWT compile.
>
> On Thu, Feb 18, 2016 at 8:57 AM Manuel Carrasco Moñino <man...@apache.org>
> wrote:
>
>> I follow, but I have a couple of thoughts
>>
>> - Is it actually useful from the user perspective to use a
>> sourceLevel=1.7 if he has to manually provide a compatible
>> gwt-jre-emulation?
>> IMO, he might want that everything works out-of-the-boxy. Right now, gwt
>> emul classes in the 2.8-snapshot make fail sourceLevel=1.7 though, so I
>> don't see any reason to deliver gwt-2.8.0 with a non working flag.
>>
>> - IMHO, for real users having to code in 1.7, it's not a problem to set
>> javac.source=1.7 and have gwtc.sourceLevel=default=1.8. In this case the
>> javac compiler will validate his source code and gwtc compiler does not
>> need to do the validation, it simply works without raising any error when
>> processing its internal jre-emul classes.
>>
>> So, since gwtc can be run with a sdk7 (even with gwt java8 sources),
>> there should not be any problem compiling gwt projects written in java7 and
>> compiled with sdk7, and the user does not bother about the sourceLevel flag.
>>
>>
>>
>> On Wed, Feb 17, 2016 at 9:13 PM, 'Goktug Gokdogan' via GWT Contributors <
>> google-web-toolkit-contributors@googlegroups.com> wrote:
>>
>>> I think you didn't understand what I said. Let me try to clarify:
>>>
>>> "For any reason, if community wants to run the GWT 2.8 SDK in Java 7
>>> source level *(i.e. gwtc sourcelevel 7)*, they can theoretically do it
>>> by supplying *a java7 compatible JRE emulation* without any
>>> compiler/SDK changes *(but just setting the gwtc sourcelevel 7)*.
>>> That's why I didn't originally remove Java7 option from the SourceLevel
>>> flag.
>>> By removing the flag (which seems submitted now), the community will not
>>> have that option *(i.e. they need also supply a modified compiler
>>> together with the emulation)*."
>>>
>>> This may never happen but keeping the flag was cheap so I kept it.
>>>
>>> On Tue, Feb 16, 2016 at 11:35 PM, Manuel Carrasco Moñino <
>>> man...@apache.org> wrote:
>>>
>>>> Removing the 1.7 flag does not make the compiler fail when using a
>>>> java7 sdk.
>>>> Now the compiler always thinks that source code is sourced-level 1.8 so
>>>> it does not fail when looking at java8 emul classes.
>>>>
>>>> You can still have the java.source property set to 1.7 when compiling
>>>> your project and javac will validate that your code is java7 compliant,
>>>> because javac process your client code.
>>>>
>>>> In summary javac and gwtc could use at the same time different source
>>>> languages, but we always need to force gwtc to use 1.8 since new java8 api
>>>> emul code.
>>>>
>>>>
>>>> On Wed, Feb 17, 2016 at 2:32 AM, 'Goktug Gokdogan' via GWT Contributors
>>>> <google-web-toolkit-contributors@googlegroups.com> wrote:
>>>>
>>>>> To remind the backlog of this:
>>>>>
>>>>> GWT 2.8 decided to support only Java8 source level (see related
>>>>> threads from last year) as the emulation will include Java 8 APIs which
>>>>> cannot be compiled in Java7 mode.
>>>>>
>>>>> However, GWT compiler itself is intended to be runnable in a Java 7
>>>>> JVM. This should enable slow-to-upgrade enterprises business to keep their
>>>>> legacy dev environments.
>>>>> For any reason, if community wants to run the GWT 2.8 SDK in Java 7
>>>>> source level, they can theoretically do it by supplying a java7 compatible
>>>>> JRE emulation without any compiler/SDK changes. That's why I didn't
>>>>> originally remove Java7 option from the SourceLevel flag.
>>>>> By removing the flag (which seems submitted now), th

Re: [gwt-contrib] Re: Compiler failing with java 7

2016-02-17 Thread Manuel Carrasco Moñino

I follow, but I have a couple of thoughts

- Is it actually useful from the user perspective to use a sourceLevel=1.7
if he has to manually provide a compatible gwt-jre-emulation?
IMO, he might want that everything works out-of-the-boxy. Right now, gwt
emul classes in the 2.8-snapshot make fail sourceLevel=1.7 though, so I
don't see any reason to deliver gwt-2.8.0 with a non working flag.

- IMHO, for real users having to code in 1.7, it's not a problem to set
javac.source=1.7 and have gwtc.sourceLevel=default=1.8. In this case the
javac compiler will validate his source code and gwtc compiler does not
need to do the validation, it simply works without raising any error when
processing its internal jre-emul classes.

So, since gwtc can be run with a sdk7 (even with gwt java8 sources), there
should not be any problem compiling gwt projects written in java7 and
compiled with sdk7, and the user does not bother about the sourceLevel flag.



On Wed, Feb 17, 2016 at 9:13 PM, 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> I think you didn't understand what I said. Let me try to clarify:
>
> "For any reason, if community wants to run the GWT 2.8 SDK in Java 7
> source level *(i.e. gwtc sourcelevel 7)*, they can theoretically do it by
> supplying *a java7 compatible JRE emulation* without any compiler/SDK
> changes *(but just setting the gwtc sourcelevel 7)*. That's why I didn't
> originally remove Java7 option from the SourceLevel flag.
> By removing the flag (which seems submitted now), the community will not
> have that option *(i.e. they need also supply a modified compiler
> together with the emulation)*."
>
> This may never happen but keeping the flag was cheap so I kept it.
>
> On Tue, Feb 16, 2016 at 11:35 PM, Manuel Carrasco Moñino <
> man...@apache.org> wrote:
>
>> Removing the 1.7 flag does not make the compiler fail when using a java7
>> sdk.
>> Now the compiler always thinks that source code is sourced-level 1.8 so
>> it does not fail when looking at java8 emul classes.
>>
>> You can still have the java.source property set to 1.7 when compiling
>> your project and javac will validate that your code is java7 compliant,
>> because javac process your client code.
>>
>> In summary javac and gwtc could use at the same time different source
>> languages, but we always need to force gwtc to use 1.8 since new java8 api
>> emul code.
>>
>>
>> On Wed, Feb 17, 2016 at 2:32 AM, 'Goktug Gokdogan' via GWT Contributors <
>> google-web-toolkit-contributors@googlegroups.com> wrote:
>>
>>> To remind the backlog of this:
>>>
>>> GWT 2.8 decided to support only Java8 source level (see related threads
>>> from last year) as the emulation will include Java 8 APIs which cannot be
>>> compiled in Java7 mode.
>>>
>>> However, GWT compiler itself is intended to be runnable in a Java 7 JVM.
>>> This should enable slow-to-upgrade enterprises business to keep their
>>> legacy dev environments.
>>> For any reason, if community wants to run the GWT 2.8 SDK in Java 7
>>> source level, they can theoretically do it by supplying a java7 compatible
>>> JRE emulation without any compiler/SDK changes. That's why I didn't
>>> originally remove Java7 option from the SourceLevel flag.
>>> By removing the flag (which seems submitted now), the community will not
>>> have that option.
>>>
>>> (It is not import from Google side; just wanted to let you know if the
>>> community cares about it.)
>>>
>>> On Mon, Feb 15, 2016 at 5:12 AM, Thomas Broyer <t.bro...@gmail.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Monday, February 15, 2016 at 11:39:02 AM UTC+1, Thomas Broyer wrote:
>>>>>
>>>>>
>>>>>
>>>>> On Monday, February 15, 2016 at 10:06:47 AM UTC+1, Manuel Carrasco
>>>>> Moñino wrote:
>>>>>>
>>>>>> Thomas, I want to experiment with this, pls, could you give me some
>>>>>> advise what are the classes I have to look at?
>>>>>>
>>>>>
>>>>> https://gwt-review.googlesource.com/14353
>>>>> (currently running the testsuite locally)
>>>>>
>>>>
>>>> Tests pass \o/
>>>>
>>>> --
>>>> 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 email to
&

Re: [gwt-contrib] Re: Compiler failing with java 7

2016-02-16 Thread Manuel Carrasco Moñino

Removing the 1.7 flag does not make the compiler fail when using a java7
sdk.
Now the compiler always thinks that source code is sourced-level 1.8 so it
does not fail when looking at java8 emul classes.

You can still have the java.source property set to 1.7 when compiling your
project and javac will validate that your code is java7 compliant, because
javac process your client code.

In summary javac and gwtc could use at the same time different source
languages, but we always need to force gwtc to use 1.8 since new java8 api
emul code.


On Wed, Feb 17, 2016 at 2:32 AM, 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> To remind the backlog of this:
>
> GWT 2.8 decided to support only Java8 source level (see related threads
> from last year) as the emulation will include Java 8 APIs which cannot be
> compiled in Java7 mode.
>
> However, GWT compiler itself is intended to be runnable in a Java 7 JVM.
> This should enable slow-to-upgrade enterprises business to keep their
> legacy dev environments.
> For any reason, if community wants to run the GWT 2.8 SDK in Java 7 source
> level, they can theoretically do it by supplying a java7 compatible JRE
> emulation without any compiler/SDK changes. That's why I didn't originally
> remove Java7 option from the SourceLevel flag.
> By removing the flag (which seems submitted now), the community will not
> have that option.
>
> (It is not import from Google side; just wanted to let you know if the
> community cares about it.)
>
> On Mon, Feb 15, 2016 at 5:12 AM, Thomas Broyer <t.bro...@gmail.com> wrote:
>
>>
>>
>> On Monday, February 15, 2016 at 11:39:02 AM UTC+1, Thomas Broyer wrote:
>>>
>>>
>>>
>>> On Monday, February 15, 2016 at 10:06:47 AM UTC+1, Manuel Carrasco
>>> Moñino wrote:
>>>>
>>>> Thomas, I want to experiment with this, pls, could you give me some
>>>> advise what are the classes I have to look at?
>>>>
>>>
>>> https://gwt-review.googlesource.com/14353
>>> (currently running the testsuite locally)
>>>
>>
>> Tests pass \o/
>>
>> --
>> 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
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/a96d8bde-37f5-4bdd-92f2-7fda3492cc94%40googlegroups.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/a96d8bde-37f5-4bdd-92f2-7fda3492cc94%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA2BRAZ1%2Bu33NNK%2BgqNdijZs7a0V7YY4fasWCes2iGJ%2Bvg%40mail.gmail.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA2BRAZ1%2Bu33NNK%2BgqNdijZs7a0V7YY4fasWCes2iGJ%2Bvg%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAsQGwM4MRA-aBxoze-1MQ_fzeCQp4Jxw1Hc2o0FiOtmHA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Compiler failing with java 7

2016-02-15 Thread Manuel Carrasco Moñino

Thomas, I want to experiment with this, pls, could you give me some advise
what are the classes I have to look at?

On Sun, Feb 14, 2016 at 12:00 PM, Thomas Broyer <t.bro...@gmail.com> wrote:

> Just to make it clearer, my suggestion is:
>
>  * force sourceLevel to 8 (either make the argument a no-op –using 8 even
> if arg says 7–, or fail on "-sourceLevel 7")
>  * build GWT with JDK 7; particularly the release artifacts (snapshots
> matter less). Note that this means changing the CI builds to run tests in
> prod mode rather than dev mode, this is probably a good idea anyway given
> we recently changed GWTTestCase to use prod mode by default.
>
> We can revise those rules after 2.8.
>
>
> On Saturday, February 13, 2016 at 6:06:24 PM UTC+1, Manuel Carrasco Moñino
> wrote:
>>
>> Hi all, in the behave of gwt-maintainers, I'm forwarding this discussion
>> started in the maintainer list to the contributors one. Feel free to
>> contribute with your opinions.
>> Basically the matter is about the convenience of not breaking java7
>> compatibility in 2.8
>>
>> Thanks
>>  -Manolo
>>
>> On Fri, Feb 12, 2016 at 6:14 PM, Thomas Broyer <t.bro...@gmail.com>
>> wrote:
>>
>>> FWIW, I just tried the latest snapshot (from today) with Java 7 and it
>>> seems to work (for now; see below).
>>> I think the issue in the samples is with -sourceLevel: the POMs there
>>> set maven.compiler.source to 1.7, which automatically passes -sourceLevel
>>> 1.7 to GWT, which then fails to parse the emul.
>>>
>>> I think that:
>>>  * now that we no longer run tests in "dev mode", it shouldn't be a
>>> problem using -sourceLevel 8 with a JDK 7 (it's a problem in dev mode as
>>> dev mode will compile sources to classes –using JDT so with the
>>> -sourceLevel compat– and then won't be able to read them back in a JDK 7;
>>> IIRC)
>>>  * we should then be able to *build* GWT with a JDK 7, and ensure
>>> compatibility of gwt-servlet with Java 7 runtimes.
>>>  * we could make GWT ignore "-sourceLevel 7" (automatically upgrading to
>>> "8", or simply removing -sourceLevel processing entirely and hard-coding
>>> the value as in older versions of GWT)
>>> This only holds as long as we don't use Java 8 language features and
>>> APIs in GWT proper (and non-GWT tests), but maybe we could set it as a goal
>>> for 2.8?
>>>
>>> Note: I said above that it works "for now", because if we build with JDK
>>> 8, we can never be sure that it'll run with a JDK 7, unless we correctly
>>> cross-compile, by passing the bootclasspath to a JDK 7 too (which is
>>> equivalent to use a JDK 7, except you're using a different version of JavaC
>>> that has a different set of bugs ;-) ) Hence my suggestion above to *build*
>>> the final SDK with a JDK 7.
>>>
>>> Let's continue that discussion publicly on gwt-contrib though.
>>>
>>> On Fri, Feb 12, 2016 at 5:28 PM 'Daniel Kurka' via gwt-maintainers <
>>> gwt-maintain...@googlegroups.com> wrote:
>>>
>>>> GWT 2.8 needs to contain Java8 APIs so taht guava will start working
>>>> again. All the outstanding Java8 patches need to go in before 2.8. So 2.8
>>>> will not work with Java7.
>>>>
>>>>
>>>> On Fri, Feb 12, 2016 at 5:25 PM Jens Nehlmeier <
>>>> jens.nehlme...@gmail.com> wrote:
>>>>
>>>>> Its not just about adding new classes but we also add APIs to existing
>>>>> classes that require Java8 classes in their signature. So you would
>>>>> need to ignore these changes on method level.
>>>>>
>>>>> AFAICT it was said that as soon as Java 8 APIs are committed GWT will
>>>>> require Java8. If someone needs Java7 support they need to replace the
>>>>> emulation code of GWT 2.8 with the one of GWT 2.7. Because of this
>>>>> possibility we don't use Java8 APIs in gwt-user code. gwt-servlet.jar
>>>>> is something to think about as soon as we want to add GWT-RPC
>>>>> serializer for Java 8 classes. If we really want to give users the
>>>>> possibility to compile GWT 2.8 with Java 7 after replacing the
>>>>> emulation code we probably need a build target that builds
>>>>> gwt-servlet-jdk8.jar when running Java8 only.
>>>>>
>>>>> Generally I thought Java8 stuff will be committed after GWT 2.8 has
>>>>> b

[gwt-contrib] Re: Compiler failing with java 7

2016-02-13 Thread Manuel Carrasco Moñino

Hi all, in the behave of gwt-maintainers, I'm forwarding this discussion
started in the maintainer list to the contributors one. Feel free to
contribute with your opinions.
Basically the matter is about the convenience of not breaking java7
compatibility in 2.8

Thanks
 -Manolo

On Fri, Feb 12, 2016 at 6:14 PM, Thomas Broyer <t.bro...@gmail.com> wrote:

> FWIW, I just tried the latest snapshot (from today) with Java 7 and it
> seems to work (for now; see below).
> I think the issue in the samples is with -sourceLevel: the POMs there set
> maven.compiler.source to 1.7, which automatically passes -sourceLevel 1.7
> to GWT, which then fails to parse the emul.
>
> I think that:
>  * now that we no longer run tests in "dev mode", it shouldn't be a
> problem using -sourceLevel 8 with a JDK 7 (it's a problem in dev mode as
> dev mode will compile sources to classes –using JDT so with the
> -sourceLevel compat– and then won't be able to read them back in a JDK 7;
> IIRC)
>  * we should then be able to *build* GWT with a JDK 7, and ensure
> compatibility of gwt-servlet with Java 7 runtimes.
>  * we could make GWT ignore "-sourceLevel 7" (automatically upgrading to
> "8", or simply removing -sourceLevel processing entirely and hard-coding
> the value as in older versions of GWT)
> This only holds as long as we don't use Java 8 language features and APIs
> in GWT proper (and non-GWT tests), but maybe we could set it as a goal for
> 2.8?
>
> Note: I said above that it works "for now", because if we build with JDK
> 8, we can never be sure that it'll run with a JDK 7, unless we correctly
> cross-compile, by passing the bootclasspath to a JDK 7 too (which is
> equivalent to use a JDK 7, except you're using a different version of JavaC
> that has a different set of bugs ;-) ) Hence my suggestion above to *build*
> the final SDK with a JDK 7.
>
> Let's continue that discussion publicly on gwt-contrib though.
>
> On Fri, Feb 12, 2016 at 5:28 PM 'Daniel Kurka' via gwt-maintainers <
> gwt-maintain...@googlegroups.com> wrote:
>
>> GWT 2.8 needs to contain Java8 APIs so taht guava will start working
>> again. All the outstanding Java8 patches need to go in before 2.8. So 2.8
>> will not work with Java7.
>>
>>
>> On Fri, Feb 12, 2016 at 5:25 PM Jens Nehlmeier <jens.nehlme...@gmail.com>
>> wrote:
>>
>>> Its not just about adding new classes but we also add APIs to existing
>>> classes that require Java8 classes in their signature. So you would
>>> need to ignore these changes on method level.
>>>
>>> AFAICT it was said that as soon as Java 8 APIs are committed GWT will
>>> require Java8. If someone needs Java7 support they need to replace the
>>> emulation code of GWT 2.8 with the one of GWT 2.7. Because of this
>>> possibility we don't use Java8 APIs in gwt-user code. gwt-servlet.jar
>>> is something to think about as soon as we want to add GWT-RPC
>>> serializer for Java 8 classes. If we really want to give users the
>>> possibility to compile GWT 2.8 with Java 7 after replacing the
>>> emulation code we probably need a build target that builds
>>> gwt-servlet-jdk8.jar when running Java8 only.
>>>
>>> Generally I thought Java8 stuff will be committed after GWT 2.8 has
>>> been released so that GWT 2.8 stays Java7 compatible. I don't know
>>> about the Guava issue that requires GWT 2.8 to already have Java8 APIs
>>> available. I thought Guava will just release Guava 20 when 2.8 is
>>> released because Gauva 19 did use some private APIs of GWT that do not
>>> exist anymore.
>>
>>
>>> 2016-02-12 16:06 GMT+01:00 Daniel Kurka <danku...@google.com>:
>>> > +Colin Alworth  +Jens
>>> >
>>> > Colin and Jens have been doing a lot of the Java8 API work, I believe
>>> this
>>> > will touch many classes within the JRE and thus will not be as easy as
>>> > ignoring a few classes.
>>> >
>>> > To be clear:
>>> > We won't be putting any resources into addressing this since its not an
>>> > issue for us, if someone feels strongly (s)he can step up and tackle
>>> this,
>>> > but the whole case does not seem to be convincing for me, why would
>>> agencies
>>> > that are slow to adopt things adopt the latest GWT version?
>>> >
>>> > -Daniel
>>> >
>>> > On Fri, Feb 12, 2016 at 3:52 PM Manuel Carrasco Moñino <
>>> man...@apache.org>
>>> > wrote:
>>> >>
>>> >> Well the situation I know,

Re: [gwt-contrib] Re: GWTCon 2015 keynote question

2015-11-17 Thread Manuel Carrasco Moñino

Exactly, although future releases of  GWT will still allow you to create
your UI components (you have access to the DOM tree), the point is to reuse
external widget collections instead of reinvent the wheel.

Obviously nowadays UI designers are much more comfortable writing
components using html + JS than using uibinder + java, and the community is
creating really good quality elements. So let's take advantage of it in gwt.

My talk in the GWTCon 2015 [1] was about using polymer catalog in GWT.
Gwt-polymer-elements [2] library allows not only  to use them as plain
elements but as widgets for classic apps. Notice that the library uses
JsInterop and all the java code needed to use the components in java is
generated automatically.

If you do a basic search in github, you could see much more contributions
to modern widgets developed with polymer than pure gwt. So if you want a
modern and good looking app you have either develop your own widgets, or
you will end reusing 3party JS libraries (polymer, angular, materialize,
material lite, jquery-ui ...) .


[1] http://www.slideshare.net/dodotis/rock-gwt-uis-with-polymer-elements
[2] https://github.com/vaadin/gwt-polymer-elements

On Tue, Nov 17, 2015 at 5:01 PM, 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> I think I need to make a few clarifications.
>
> We (we as in Google) are not planning to go on delete any code from
> GWT-SDK after 2.8 release.
> Yes, we believe Widget, GWT-RPC, RF etc. reached end of its useful life
> and we will not invest on them anymore however if there is enough
> interest/demand outside, there is nothing preventing you from resurrecting
> the pieces you see useful. If you like old GWT widget / MVP style coding,
> go ahead and use it. Being said that I would highly suggest maintaining
> them as separate libraries outside of the SDK and let them progress at
> their own pace, otherwise they will become more irrelevant in time.
>
> Please also keep in mind that GWT is not the only framework that provides
> widget abstraction. Actually there is very healthy ecosystem outside of GWT
> that solves similar problems. So don't think that you are bound with
> earlier patterns, abstractions, framework etc. I personally find recent
> frameworks very innovative and productive.
>
> Also note that; Julien's demonstrated Angular integration as part of the
> *JsInterop* presentation; the whole idea was to show that how easy to
> integrate with JS; it wasn't a recommendation. He had a demo for Polymer as
> well but the code could have confused listeners due the way polymer works
> so we chose to skip that; otherwise there would have been a polymer demo in
> the presentation as well. We are not actively working on any framework.
> Again use whatever works for you, or better invent your own.
>
> And finally, at Google side; our current guiding principle is to enable
> the java language and tools for use in modern web development. Our
> customers are people who want to use Java; either because they love it or
> because they need it in for code charing. I see that as the most value we
> bring into the table and we will do that as best as we can. So if you don't
> fall into that category, probably you need to look for something else.
>
> Cheers.
>
>
> On Mon, Nov 16, 2015 at 4:04 PM, 'Ray Cromwell' via GWT Contributors <
> google-web-toolkit-contributors@googlegroups.com> wrote:
>
>> My hope would be that some enterprising individuals will start porting
>> pieces of GWT generators to annotation processors in the future. Some of
>> them are definitely doable without much effort
>> (CssResource/ClientBundle/etc) Some of them will require more work, but are
>> still possible (UiBinder with caveats), and some of them just plain won't
>> work (RPC) because of the requirement of global information.
>>
>> Other useful bits of com.google.gwt could be easy modified to use
>> JsInterop instead of JSNI as we have done in much of the JRE to share code
>> with J2CL.
>>
>>
>>
>>
>> On Mon, Nov 16, 2015 at 3:51 PM, Alain Ekambi 
>> wrote:
>>
>>> Errai UI ?
>>> On 17 Nov 2015 00:41, "Stephen Haberman" 
>>> wrote:
>>>


> I guess I will be trying UiBinder with GQuery and not rely on Widget
> for my project. The UiBinder might disappear, but we are using mostly 
> plain
> HTML and Bootstrap styles. So we are only interested in binding events. 
> The
> UiBinder templates will be easy to migrate later on.
>

 FWIW this is what we're doing, with a small variation:

 Use UiBinder, use regular CSS styling (bootstrap/etc.), but only very
 minimal/core widgets, like TextBox (just an input tag), HTMLPanel, and
 ListBox (select tag).

 My theory/hope is that porting away from UiBinder + TextBox/ListBox to
 some other templating language + "basically a text box, basically a select
 box" replacements

Re: [gwt-contrib] Re: New JsInterop document

2015-11-14 Thread Manuel Carrasco Moñino

Goktug, this is an example perfectly working with jsInteropMode=JS but not
working with JS_RC :
  (Errors : Native JsType field 'String MyComponent.TAG' cannot have
initializer &  Native JsType method 'String MyComponent.getTagName()'
should be native or abstract)

@com.google.gwt.core.client.js.JsType

@jsinterop.annotations.JsType(isNative=true)

public interface MyComponent {

 public static String TAG = "my-component";

 public static String getTagName() {

   return TAG;

 }

 @jsinterop.annotations.JsProperty

 @com.google.gwt.core.client.js.JsProperty

 public String getFoo();

 @jsinterop.annotations.JsProperty

 @com.google.gwt.core.client.js.JsProperty

 public void setFoo(String foo);

}


public void onModuleLoad() {

 assert MyComponent.getTagName() == MyComponent.TAG;

 Element elem = Document.get().createElement(MyComponent.TAG);

 Document.get().getBody().appendChild(elem);

 MyComponent comp = (MyComponent) elem;

 comp.setFoo("bar");

}





On Wed, Nov 11, 2015 at 6:25 AM, 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> In native types, the support for static methods are same as the support
> for static fields; only overlays are supported because we don't modify the
> native types. Can you give an example that works with static methods and
> doesn't work with static field but should work as well? What do you mean by
> "static shared fields"?
>
>
> wrt. overloading: we are not planning to support automatic dispatches per
> argument count in this version. And btw, method overloading never worked
> earlier and we recently added support and just for native types.
>
> On Tue, Nov 10, 2015 at 4:19 PM, Manuel Carrasco Moñino <man...@apache.org
> > wrote:
>
>>
>> Another issue in the new implementation is that it's not supported any
>> more static shared fields in JsType native interfaces, I think if we
>> support static methods we should support static fields as well, or is there
>> i any reason to prevent it ?.
>>
>> On Tue, Nov 10, 2015 at 6:11 PM, Manuel Carrasco Moñino <
>> man...@apache.org> wrote:
>>
>>> var args sounds pretty good, but some kind of overloading based on the
>>> number of parameters like we had in gwt-exporter should cover many use
>>> cases, compiler could give an error (like it does now) when it sees two
>>> methods with the same-number-of-parameters signature.
>>>
>>>
>>>
>>> On Tue, Nov 10, 2015 at 5:59 PM, 'Roberto Lublinerman' via GWT
>>> Contributors <google-web-toolkit-contributors@googlegroups.com> wrote:
>>>
>>>> No plan to support through Java implementors, although there are plans
>>>> to support varargs which would let you accomplish something similar.
>>>> On Nov 10, 2015 08:53, "Manuel Carrasco Moñino" <man...@apache.org>
>>>> wrote:
>>>>
>>>>> I see, it works, thanks.
>>>>>
>>>>> Any plan to work as well with gwt exported classes ?
>>>>>
>>>>> On Tue, Nov 10, 2015 at 5:33 PM, Julien Dramaix <
>>>>> julien.dram...@gmail.com> wrote:
>>>>>
>>>>>> Method overloading works in native JsType JsType(isNative=true)
>>>>>>
>>>>>> On Tue, Nov 10, 2015 at 5:15 PM Manuel Carrasco Moñino <
>>>>>> man...@apache.org> wrote:
>>>>>>
>>>>>>> Seems that method overloading is not working anymore with JS_RC
>>>>>>> mode, it was working in JS mode though:
>>>>>>>
>>>>>>> Example:
>>>>>>>
>>>>>>>boolean validate()
>>>>>>>boolean validate(String foo)
>>>>>>>
>>>>>>> Is it a feature not implemented yet, or it is not in the
>>>>>>> specification?
>>>>>>>
>>>>>>> Thanks
>>>>>>> - Manolo
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Nov 9, 2015 at 3:40 PM, Cristian Rinaldi <
>>>>>>> csrina...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Thanks Julien!!!
>>>>>>>>
>>>>>>>> This work fine!!
>>>>>>>>
>>>>>>>> El viernes, 23 de octubre de 2015, 4:13:55 (UTC-3), Goktug Gokdogan
>>>>>>>> escribió:
>>>>>>>>>
>>>>>>>>> As we are getting close to 2.8 release I wrote

Re: [gwt-contrib] Re: New JsInterop document

Seems that method overloading is not working anymore with JS_RC mode, it
was working in JS mode though:

Example:

   boolean validate()
   boolean validate(String foo)

Is it a feature not implemented yet, or it is not in the specification?

Thanks
- Manolo


On Mon, Nov 9, 2015 at 3:40 PM, Cristian Rinaldi 
wrote:

> Thanks Julien!!!
>
> This work fine!!
>
> El viernes, 23 de octubre de 2015, 4:13:55 (UTC-3), Goktug Gokdogan
> escribió:
>>
>> As we are getting close to 2.8 release I wrote a new document that is
>> concentrating on jsinterop features to be released in 2.8:
>>
>> https://docs.google.com/document/d/10fmlEYIHcyead_4R1S5wKGs1t2I7Fnp_PaNaa7XTEk0/edit#
>>
>> Please share your feedback.
>>
>> Thanks,
>>
>> Goktug
>>
> --
> 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
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/51f767f9-0afd-48fd-bef8-a9106b0d716a%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtrYCKBHtp6ccqnxTq%3Dq2EK8jB-A57qqFX05U2sw6-12w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: New JsInterop document

I see, it works, thanks.

Any plan to work as well with gwt exported classes ?

On Tue, Nov 10, 2015 at 5:33 PM, Julien Dramaix <julien.dram...@gmail.com>
wrote:

> Method overloading works in native JsType JsType(isNative=true)
>
> On Tue, Nov 10, 2015 at 5:15 PM Manuel Carrasco Moñino <man...@apache.org>
> wrote:
>
>> Seems that method overloading is not working anymore with JS_RC mode, it
>> was working in JS mode though:
>>
>> Example:
>>
>>boolean validate()
>>boolean validate(String foo)
>>
>> Is it a feature not implemented yet, or it is not in the specification?
>>
>> Thanks
>> - Manolo
>>
>>
>> On Mon, Nov 9, 2015 at 3:40 PM, Cristian Rinaldi <csrina...@gmail.com>
>> wrote:
>>
>>> Thanks Julien!!!
>>>
>>> This work fine!!
>>>
>>> El viernes, 23 de octubre de 2015, 4:13:55 (UTC-3), Goktug Gokdogan
>>> escribió:
>>>>
>>>> As we are getting close to 2.8 release I wrote a new document that is
>>>> concentrating on jsinterop features to be released in 2.8:
>>>>
>>>> https://docs.google.com/document/d/10fmlEYIHcyead_4R1S5wKGs1t2I7Fnp_PaNaa7XTEk0/edit#
>>>>
>>>> Please share your feedback.
>>>>
>>>> Thanks,
>>>>
>>>> Goktug
>>>>
>>> --
>>> 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 email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
>>> .
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/51f767f9-0afd-48fd-bef8-a9106b0d716a%40googlegroups.com
>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/51f767f9-0afd-48fd-bef8-a9106b0d716a%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> 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
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtrYCKBHtp6ccqnxTq%3Dq2EK8jB-A57qqFX05U2sw6-12w%40mail.gmail.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtrYCKBHtp6ccqnxTq%3Dq2EK8jB-A57qqFX05U2sw6-12w%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D62mQ0iqjRBc8E8vbPTWqtE61gUcb-1qbKATt8wtrsUTw%40mail.gmail.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D62mQ0iqjRBc8E8vbPTWqtE61gUcb-1qbKATt8wtrsUTw%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtTjvgcdJLojY4C4ouNzDUOBOXTF_TKjxRA8V2Azjoecw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: New JsInterop document

var args sounds pretty good, but some kind of overloading based on the
number of parameters like we had in gwt-exporter should cover many use
cases, compiler could give an error (like it does now) when it sees two
methods with the same-number-of-parameters signature.



On Tue, Nov 10, 2015 at 5:59 PM, 'Roberto Lublinerman' via GWT Contributors
<google-web-toolkit-contributors@googlegroups.com> wrote:

> No plan to support through Java implementors, although there are plans to
> support varargs which would let you accomplish something similar.
> On Nov 10, 2015 08:53, "Manuel Carrasco Moñino" <man...@apache.org> wrote:
>
>> I see, it works, thanks.
>>
>> Any plan to work as well with gwt exported classes ?
>>
>> On Tue, Nov 10, 2015 at 5:33 PM, Julien Dramaix <julien.dram...@gmail.com
>> > wrote:
>>
>>> Method overloading works in native JsType JsType(isNative=true)
>>>
>>> On Tue, Nov 10, 2015 at 5:15 PM Manuel Carrasco Moñino <
>>> man...@apache.org> wrote:
>>>
>>>> Seems that method overloading is not working anymore with JS_RC mode,
>>>> it was working in JS mode though:
>>>>
>>>> Example:
>>>>
>>>>boolean validate()
>>>>boolean validate(String foo)
>>>>
>>>> Is it a feature not implemented yet, or it is not in the specification?
>>>>
>>>> Thanks
>>>> - Manolo
>>>>
>>>>
>>>> On Mon, Nov 9, 2015 at 3:40 PM, Cristian Rinaldi <csrina...@gmail.com>
>>>> wrote:
>>>>
>>>>> Thanks Julien!!!
>>>>>
>>>>> This work fine!!
>>>>>
>>>>> El viernes, 23 de octubre de 2015, 4:13:55 (UTC-3), Goktug Gokdogan
>>>>> escribió:
>>>>>>
>>>>>> As we are getting close to 2.8 release I wrote a new document that is
>>>>>> concentrating on jsinterop features to be released in 2.8:
>>>>>>
>>>>>> https://docs.google.com/document/d/10fmlEYIHcyead_4R1S5wKGs1t2I7Fnp_PaNaa7XTEk0/edit#
>>>>>>
>>>>>> Please share your feedback.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Goktug
>>>>>>
>>>>> --
>>>>> 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 email to
>>>>> google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/51f767f9-0afd-48fd-bef8-a9106b0d716a%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/51f767f9-0afd-48fd-bef8-a9106b0d716a%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>>
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>> --
>>>> 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 email to
>>>> google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtrYCKBHtp6ccqnxTq%3Dq2EK8jB-A57qqFX05U2sw6-12w%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtrYCKBHtp6ccqnxTq%3Dq2EK8jB-A57qqFX05U2sw6-12w%40mail.gmail.com?utm_medium=email_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> --
>>> 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 email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
>>> .
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D62mQ0iqjRBc8E8vbPTWqtE61gUcb-1qbKATt8wtrsUTw%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D62m

Re: [gwt-contrib] Re: New JsInterop document

Another issue in the new implementation is that it's not supported any more
static shared fields in JsType native interfaces, I think if we support
static methods we should support static fields as well, or is there i any
reason to prevent it ?.

On Tue, Nov 10, 2015 at 6:11 PM, Manuel Carrasco Moñino <man...@apache.org>
wrote:

> var args sounds pretty good, but some kind of overloading based on the
> number of parameters like we had in gwt-exporter should cover many use
> cases, compiler could give an error (like it does now) when it sees two
> methods with the same-number-of-parameters signature.
>
>
>
> On Tue, Nov 10, 2015 at 5:59 PM, 'Roberto Lublinerman' via GWT
> Contributors <google-web-toolkit-contributors@googlegroups.com> wrote:
>
>> No plan to support through Java implementors, although there are plans to
>> support varargs which would let you accomplish something similar.
>> On Nov 10, 2015 08:53, "Manuel Carrasco Moñino" <man...@apache.org>
>> wrote:
>>
>>> I see, it works, thanks.
>>>
>>> Any plan to work as well with gwt exported classes ?
>>>
>>> On Tue, Nov 10, 2015 at 5:33 PM, Julien Dramaix <
>>> julien.dram...@gmail.com> wrote:
>>>
>>>> Method overloading works in native JsType JsType(isNative=true)
>>>>
>>>> On Tue, Nov 10, 2015 at 5:15 PM Manuel Carrasco Moñino <
>>>> man...@apache.org> wrote:
>>>>
>>>>> Seems that method overloading is not working anymore with JS_RC mode,
>>>>> it was working in JS mode though:
>>>>>
>>>>> Example:
>>>>>
>>>>>boolean validate()
>>>>>boolean validate(String foo)
>>>>>
>>>>> Is it a feature not implemented yet, or it is not in the specification?
>>>>>
>>>>> Thanks
>>>>> - Manolo
>>>>>
>>>>>
>>>>> On Mon, Nov 9, 2015 at 3:40 PM, Cristian Rinaldi <csrina...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Thanks Julien!!!
>>>>>>
>>>>>> This work fine!!
>>>>>>
>>>>>> El viernes, 23 de octubre de 2015, 4:13:55 (UTC-3), Goktug Gokdogan
>>>>>> escribió:
>>>>>>>
>>>>>>> As we are getting close to 2.8 release I wrote a new document that
>>>>>>> is concentrating on jsinterop features to be released in 2.8:
>>>>>>>
>>>>>>> https://docs.google.com/document/d/10fmlEYIHcyead_4R1S5wKGs1t2I7Fnp_PaNaa7XTEk0/edit#
>>>>>>>
>>>>>>> Please share your feedback.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Goktug
>>>>>>>
>>>>>> --
>>>>>> 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 email to
>>>>>> google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>>>>>> To view this discussion on the web visit
>>>>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/51f767f9-0afd-48fd-bef8-a9106b0d716a%40googlegroups.com
>>>>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/51f767f9-0afd-48fd-bef8-a9106b0d716a%40googlegroups.com?utm_medium=email_source=footer>
>>>>>> .
>>>>>>
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>> --
>>>>> 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 email to
>>>>> google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtrYCKBHtp6ccqnxTq%3Dq2EK8jB-A57qqFX05U2sw6-12w%40mail.gmail.com
>>>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtrYCKBHtp6ccqnxTq%3Dq2EK8jB-A57qqFX05U2sw6-12w%40mail.gmail.com?utm_medium=email_source=footer>
>>>>> .
>>>>> For more options, visit https:

Re: [gwt-contrib] [GWT2.8] RequestFactory lambda support

2015-09-15 Thread Manuel Carrasco Moñino

Hi Kay,

It makes sense to me if it does not break old code, could you take the time
to make those modifications and send a patch?

Thanks
- Manolo

On Tue, Sep 15, 2015 at 3:06 PM, Kay-Uwe Janssen 
wrote:

> Hello there,
>
> i wonder if there are plans to allow developers to use lambdas/method
> references for requestfactory.
>
> my idea was that there could be some overloaded versions of
> fire(Receiver) and to(Receiver) that accept 1-3 lamdbas (4 if the
> deprecated onViolation should be supported here too).
>
> e.g
> fire(Receiver) // the original
> fire(SuccessReceiver) // only the success callback
> fire(SuccessReceiver, FailureReceiver) // the success + failure callback
> fire(SuccessReceiver, ConstraintViolationReceiver) // the success +
> ConstraintViolation callback
> fire(SuccessReceiver, FailureReceiver, ConstraintViolationReceiver) //
> the success + failure + ConstraintViolation callback
>
> same for to() of course.
>
> the implementation could be something like: all lambda supporting methods
> call the one with the Receiver parameter with an assembled Receiver that
> forwards its calls to the corresponding lambda.
>
>
> --
> 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
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/b33b86ac-e2e9-4e9d-a6d5-a4efdfa9117e%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAshjwuiDq3zcpB7qF15_%2BfUHR6X3P-tFugS9Y8u_9tLUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib]

2015-07-16 Thread Manuel Carrasco Moñino

Dear contributors:

In my opinion there is a lot of stuff in our site which is obsolete, or is
not useful or even could confuse new developers.

I also spoke with Julien and he agrees that we should remove many of the
entries, so we want open a thread before in the mailing list to get some
feedback from you.

Although we can remove those page totally from the site, I think it should
be fine if we remove links from our TOC, so as they start being removed
from crawlers, but we don't break external links.

These are the items I consider to be removed:

* Tutorials - AJAX Communication.
- Introduction: is quite trivial and most people knows about ajax.
- RPC: it's an old protocol
- JSON: it's a tedious task and makes the user feel that JSON in GWT is
laborious, it says nothing about autobeans, or many popular gwt libraries
widely used.
- Cros-site: it's out dated since does not say anything about modern
CORS
- JSON php: I don't think so many people are interested on php
I think everything here is obsolete or confusing. The only thing to
maintain could be RPC, but

So in my opinion we could either remove all points here, or just
maintain the RPC section, picking up some paragraphs from the introduction,
adding a disclaimer about it is a former protocol, and noticing that there
are many other 3party options nowadays.

* Tutorials - jUnit testing
We could remove this, since we already have a doc about junit, and we
don't have to maintain this page which is outdated and a complex section
for beginners.

* Tutorials - GAE Deploy
I don't think we should maintain it. Half of the tutorial is about how
to setup a GAE project and how to use some stuff in server side. I think
most of our audience might not being using GAE and there is plenty of info
about how to deal with GAE in other forums.

* Resources - Presentations
Everything here seems outdated 9/10 years ago, probably we should link
or embed recent GWT events like GWT.create or GWTconf, but I think it's
better to remove this section until we have something better.

* Resources - Articles

- GWT Hibernate, is it still valid ?
- Memory Leaks, is it still relevant ?
- GWT iPhone, imo definetively should be removed.

* Resources - Case Studies
Probably we should disable this until we add some modern case studies
because it seems like nothing happened in GWT since 2011

* Resources - Developer Spotlight
I don't see so much value here right now, Link to submit more stuff is
broken, linked gallery does not work anymore, project list is a query to
google code, and videos are very old.

I volunteer to remove all those entries after your feedback

Thanks
- Manolo

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtxyGf%3DtgZw%3D%2BGaV0C56KqWtDL%3DrbS4qq5d5-ryuxCujw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re:

2015-07-16 Thread Manuel Carrasco Moñino

Will work on improving RPC and JSON and not remove them.

And agree, devmode is the next step.
Also I want to write something about jsinterop although it's experimental.

On Thu, Jul 16, 2015 at 11:57 AM, Thomas Broyer t.bro...@gmail.com wrote:

On Thursday, July 16, 2015 at 10:50:12 AM UTC+2, Manuel Carrasco Moñino
wrote:

Dear contributors:

In my opinion there is a lot of stuff in our site which is obsolete, or
is not useful or even could confuse new developers.

I also spoke with Julien and he agrees that we should remove many of the
entries, so we want open a thread before in the mailing list to get some
feedback from you.

Although we can remove those page totally from the site, I think it
should be fine if we remove links from our TOC, so as they start being
removed from crawlers, but we don't break external links.

+1
And add a notice/warning at the top of the removed pages.

These are the items I consider to be removed:

* Tutorials - AJAX Communication.
- Introduction: is quite trivial and most people knows about ajax.
- RPC: it's an old protocol

…but we don't really have anything better to propose for now
(RequestFactory? It doesn't really fit in a tutorial, too complex).

- JSON: it's a tedious task and makes the user feel that JSON in GWT
is laborious, it says nothing about autobeans, or many popular gwt
libraries widely used.

…or JsInterop (though it's still beta as of the last release)
Also note that AutoBeans don't work well when the root of the JSON is an
array.
I think the JSNI approach is OK until we can safely recommend JsInterop.

- Cros-site: it's out dated since does not say anything about modern
CORS

+1 to remove it.

- JSON php: I don't think so many people are interested on php

I wouldn't bet on that ;-)
But +1 for hiding it.

I think everything here is obsolete or confusing. The only thing to
maintain could be RPC, but

Sounds good.

* Tutorials - jUnit testing
We could remove this, since we already have a doc about junit, and we
don't have to maintain this page which is outdated and a complex section
for beginners.

I would simplify it (remove the part about running the tests: just run it
like any other JUnit test, just make sure your sources are in the classpath
–like with the compiler and devmode–, this is all taken care of for you by
the plugin for Eclipse) but not remove it.

+1
But on the other hand, it's the *only* page on the site that talks about
the AppEngineLauncher for DevMode.

* Resources - Articles

- GWT Hibernate, is it still valid ?
- Memory Leaks, is it still relevant ?
- GWT iPhone, imo definetively should be removed.

* Resources - Case Studies
Probably we should disable this until we add some modern case studies
because it seems like nothing happened in GWT since 2011

I volunteer to remove all those entries after your feedback

Next step: rework the page about DevMode to no longer talk about classic
DevMode and the browser plugins.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/77ead255-598d-4378-9918-ab40501b39a6%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/77ead255-598d-4378-9918-ab40501b39a6%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] New Tutorial for the gwtproject site

2015-07-08 Thread Manuel Carrasco Moñino

Dear contributors,

In order to add some modern stuff to gwtproject site, I have written a
tutorial [1] to create applications based on web components.

This tutorial uses JsInterop wrappers for Polymer Iron and Paper
collections through the gwt-polymer-elements [2] library, so as the user
can create modern material design based UI in GWT.

The tutorial follows the same approach than other gwt tutorials: the user
learns at the same time that he codes an example application. In this case
a simple TodoList which you can test and play with at [3].

I have deployed a version of the gwtproject site in github pages [4] so as
you can see how the tutorial will look in the site after the merge.

Please, could someone review the pull request [1] and give some feedback?

Thanks
- Manolo

[1] https://github.com/gwtproject/gwt-site/pull/94
[2] https://github.com/vaadin/gwt-polymer-elements
[3] http://manolo.github.io/gwt-polymer-todo-list/demo/TodoListWidgets.html
[4]
http://manolo.github.io/gwt-polymer-todo-list/gwt/doc/latest/polymer-tutorial/introduction.html

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAuu4kLMJyZByHs5iBxG2ikqU8Hew-Q_4GfV5dG-j9_kVw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: New Tutorial for the gwtproject site

2015-07-08 Thread Manuel Carrasco Moñino

Path to polyfill was not updated after renaming module outputs, fixed at
[1] and deployed.

Thank you
- Manolo

[1]
https://github.com/manolo/gwt-polymer-todo-list/commit/29b5569638b48ae291928f6f9d1085afe9e43fc9

El jue., 9 jul. 2015 a las 0:39, Jens (jens.nehlme...@gmail.com) escribió:

The demo fails to load webcomponents.js and thus does not work in any
other browser except Chrome (which probably does not need webcomponents.js).

-- J.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/93140aff-f9a5-4777-a5d5-7412ff5fa7dc%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/93140aff-f9a5-4777-a5d5-7412ff5fa7dc%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAs%3D%3DuxR5uSH8cV9ctKvShVzwjH3rTSEEVRLB_zO3nW0Vw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT RPC or Errai or RequestBuilder?

2015-02-19 Thread Manuel Carrasco Moñino

FYI, Gwtquery Ajax is almost the same than Requestor, it uses the jquery
sexy api and suppors json and xml serialization/deserialization and
databinding among other features like data forms etc. It has a jvm
implementation so as you can use gquery Ajax in your tests or in server
side.

http://gwtquery.github.io/gwt.create-slides/gwtcreate2015/gwtcreate2015.html#19

http://gwtquery.github.io/gwt.create-slides/gwtcreate2015/gwtcreate2015.html#32

- Manolo


On Wed, Feb 11, 2015 at 2:56 PM, Danilo Reinert danilorein...@gmail.com
wrote:

 Hi Mohammed.

 If you're looking for a replacement for RequestBuilder, which is a
 low-level approach for requesting, with all its flexibility, you would
 better go with a high level http client api.

 To fulfill exactly this need, I developed Requestor
 https://github.com/reinert/requestor, which is really an HTTP Client
 API for GWT.

 I strongly recommend you to try it, since it offers everything you need to
 communicate via HTTP out of the box and many other features for a good HTTP
 Client API. (I've modeled it based on successful APIs from the Python, JS
 and Java communities)

 You won't need to worry about json serialization (many alternatives are
 available for it), binary data manipulation, authentication, and many other
 things.

 The API has a very elegant idiom and you find it simple and intuitive to
 make requests (a comparison with RequestBuilder is shown at the project
 home).

 Cheers.


 Em segunda-feira, 9 de fevereiro de 2015 09:41:03 UTC-3, Mohammed Sameen
 escreveu:

 Hi,
 I created big application using GWT and am using RequestBuilder to
 communicate with the server.So what is the best way for communicate to
 server from client.
 i)RequestBuilder
 ii)GWT RPC
 iii)Any other approach(GWT Errai).


 I came to know that using GWT RPC is huge pain , so,what are the drawback
 of using GWT RPC?what is the best approach?Please give me suggestion?

  --
 You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-web-toolkit@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Could someone plubish a video showing how to debug GWT using SuperDevMode in NetBeans?

2015-02-19 Thread Manuel Carrasco Moñino

does 'temporarily' mean that eventually you will replace the old one with
the new one? or simply we should switch to the new one because the other
would become unmaintained?

On Thu, Feb 19, 2015 at 7:02 PM, Thomas Broyer t.bro...@gmail.com wrote:

 I don't know Netbeans much but IIUC it has pretty good support for Maven;
 so how about using Maven with gwt-maven-plugin?
 If you have a multi-module project (which you should, IMO), then have a
 look at the net.ltgt.gwt.maven:gwt-maven-plugin:1.0-beta-1 instead of
 org.codehaus.mojo:gwt-maven-plugin; it's gwt:codeserver has been designed
 specifically for multi-module projects (disclaimer: this is my own project,
 the other I'm just maintaining “temporarily”).


 On Friday, January 16, 2015 at 11:03:03 PM UTC+1, Edson Richter wrote:

 As in subject, please, someone could publish a video showing how to use
 SuperDevMode to debug a GWT app in NetBeans?

 Thanks,

 Edson

  --
 You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-web-toolkit@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT and Material Design

2015-02-11 Thread Manuel Carrasco Moñino

Awesome project !
I did a couple of examples in my gwt.create presentation to demo how gquery
can help with things like material design [1] [2], I'm about to release a
better css3 animation plugin for gquery which allows inject css frames,
etc. Contact me for any help you need.

- Manolo

[1]
http://gwtquery.github.io/gwt.create-slides/gwtcreate2015/gwtcreate2015.html#28
[2]
http://gwtquery.github.io/gwt.create-slides/gwtcreate2015/gwtcreate2015.html#29



On Wed, Feb 11, 2015 at 6:19 AM, mark kevin ringor kevzlou7...@gmail.com
wrote:

 Hi Grace,

 I have updated the Getting Started Documentation on how to implement
 material design in GWT (http://www.gwt-material.appspot.com). I need more
 help on how to make it more easy (like using gQuery).


 Best Regards,
 Kevin

 On Wed, Feb 11, 2015 at 4:33 AM, Grace C glchri...@gmail.com wrote:

 Nice! Do you have the current code / a starting project available as open
 source? I would love to use this.


 On Saturday, February 7, 2015 at 12:59:07 AM UTC-5, mark kevin ringor
 wrote:

 Checkout our under development project on http://gwt-material.
 appspot.com/ we are integrating the MaterializeCSS(http://
 materializecss.com/) to GWT.
 Hope you like it :)

 On Tuesday, January 6, 2015 at 10:30:37 AM UTC+8, philip andrew wrote:

 Hi there,

 Has anyone tried to make a Material Design for GWT?
 http://www.google.com/design/spec/material-design/introduction.html

 Philip

  --
 You received this message because you are subscribed to a topic in the
 Google Groups Google Web Toolkit group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/google-web-toolkit/bn57tSMkH7E/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to
 google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-web-toolkit@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.


  --
 You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-web-toolkit@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Where do I find my password for gerrit?

I agree 100%, the friction for contributing this project is huge. Not only
the setup of the project, but the review process, tools, build, etc.

We are trying to improve the process, right now contribution to the
documentation has been enormously simplified (please don't hesitate improve
to the contributors page if you found something wrong or unclear) but
anyway we must continue working to facilitate code contributions, we love
hearing suggestions and ideas from you.

On Mon, Feb 9, 2015 at 4:32 PM, Richard Wallis rdwal...@gmail.com wrote:

I know it's too much to ask to move the project to github. But even the
authentication on this project is not done in the standard way.

Last time I tried to submit a patch I was stuck for days because I'd done
the checkout with --depth 1.

There's a lot of friction to contributing to this project.

I'm useless with git / the unix command line but things could be made
easier.

On Mon, Feb 9, 2015 at 5:18 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

On Mon, Feb 9, 2015 at 4:15 PM, Richard Wallis rdwal...@gmail.com
wrote:

Thanks Thomas Manuel for the handholding :)

Managed to find git bash and create the cookie.

If anyone has the time, please can the contribution process be made more
standardized.

What do you mean as standard, accept github pull requests?

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAuZ%2BEcRdHza2qARVJ0PspEt-WndjTrQFuwRWtqBQwwq%2BQ%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAuZ%2BEcRdHza2qARVJ0PspEt-WndjTrQFuwRWtqBQwwq%2BQ%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEqaEVhW5bhaySZLgxT-JU0ckpC-EOLCJjTReB2JQdhUhCysrg%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEqaEVhW5bhaySZLgxT-JU0ckpC-EOLCJjTReB2JQdhUhCysrg%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAuxzbivGOHENea5%3DJ9hP_gcqp1PTDXmC-SM9Sn3__A4NA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Where do I find my password for gerrit?

On Mon, Feb 9, 2015 at 4:15 PM, Richard Wallis rdwal...@gmail.com wrote:

 Thanks Thomas  Manuel for the handholding :)

 Managed to find git bash and create the cookie.

 If anyone has the time, please can the contribution process be made more
 standardized.


What do you mean as standard, accept github pull requests?

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAuZ%2BEcRdHza2qARVJ0PspEt-WndjTrQFuwRWtqBQwwq%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Where do I find my password for gerrit?

On Mon, Feb 9, 2015 at 2:47 PM, Richard Wallis rdwal...@gmail.com wrote:

 Thanks for the help.

 I've contributed before, so everything is setup.  I just need the password
 (Is this not possible?).

 It's a bit too much to ask Windows users to install cygwin, I'll setup a
 vm if it's not possible to get a password.


It's no so much, actually 'git for windows' is built on the top of cygwin,
it installs a bash shell and iirc, some utilities like perl etc. You can
even select if it installs some other unix like utilities like find etc.






-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAvvg%3DHPgOGFPN5QOWoisKdF%2BZTRda0MBFoTNvybB%2B-awA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.8.0-SNAPSHOT

It was updated yesterday with all the stuff in master, so those changes
should be there.
Today is going to be run in a couple of hours, although there are no
changes in the repo.
Try to force your maven cache to be updated: mvn -U

On Tue, Feb 10, 2015 at 7:39 AM, Ali Akhtar ali.rac...@gmail.com wrote:

Hey Manuel,

I'm using your linked repo, but I'm not sure if its updating. Defender
methods were added a few days ago, however when I try to use them within
client code, I get an 'undefined' javascript error.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/e542c9ca-00ec-4466-826b-8f7ac5ef38af%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/e542c9ca-00ec-4466-826b-8f7ac5ef38af%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAuECu0rMy7dZOsZVa83mtyfYYwk9wSttLsM9XHytc%3DGYw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Where do I find my password for gerrit?

You cannot submit your patch via github.

In windows, probably your git installation comes with a terminal where you
can copy and paste the instructions google give you to setup your cookies.

Otherwise I recommend to install cygwin, it comes with a terminal which
almost emulates a unix system environment, when installing cygwing select
git, and any other utility you could need.

On Mon, Feb 9, 2015 at 1:59 PM, Richard Wallis rdwal...@gmail.com wrote:

Hi, trying to submit a patch and I can't authenticate.

I go to https://gwt.googlesource.com

I click generate password and I get instructions on how to generate a
cookie on a Unix system. I'm on Windows.

I have signed the contributor agreement. Can I submit my patch via github?

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/c3b6c72f-ccea-4d5a-afa1-5146d23b39e7%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/c3b6c72f-ccea-4d5a-afa1-5146d23b39e7%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAv_b42LGTbZSsdZ1yBG13ZiU3q5%2Bj_uLuQ1GNooFFonWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Why doesn't GWT just export everything automattically

2015-02-03 Thread Manuel Carrasco Moñino

gwt-exporter allows you to export entire classes, certain methods on it,
static functions and interfaces, even not modifying the original classes,
so you can export an entire library just using auxiliary classes and
annotations. Take a look to the documentation of ExportOverlay:
https://code.google.com/p/gwt-exporter/wiki/GettingStarted#ExportOverlay

We are not adding new features to gwt-exporter, because the future will be
JsInterop which uses the compiler to do the magic instead of generators,
but there are a lot of features in gwt-exporter which could not be
eventually in jsinterop.

If you need to export something for production right now I'll go with
gwt-exporter until jsinterop is ready since their API is still in
discussion, it is experimental and some things could fail.

If gwt-export documentation is not good enough, you can take a look to some
projects using it, in the way you want, I mean not modifying original
classes.

JsQuery: exports gwtquery and produces a clone of jQuery
https://github.com/manolo/gwt-slides/blob/master/src/main/java/com/google/gwt/query/jsquery/JsQuery.java
JsUpload: exports gwtupload
https://github.com/manolo/gwtupload/tree/master/jsupload/src/main/java/jsupload

Finally, and answering the question in the subject, GWT does not export
everything in order to optimize the JS generated, think that marking
anything as exportable using either jsInterop or gwt-exporter, implies that
all this code is candidate to be used from JS, so the compiler does not
remove it if eventually is not used in your java app.

- Manolo

On Sun, Feb 1, 2015 at 12:20 AM, Joseph Gardi jgleo...@gmail.com wrote:

That's a good point. I understand why they don't export everything
automatically now, but if they won't export everything automatically then I
want an easier way to export classes without changing them. The most common
reason to not change code in order to export it is if it's in a library.
Messing with a library's code would be a lot of trouble. GWT exporter's
mechanism for exporting classes without changing them is also difficult.

On Saturday, January 31, 2015 at 6:00:29 PM UTC-5, Peter Donald wrote:

On Sun, Feb 1, 2015 at 8:58 AM, Joseph Gardi jgle...@gmail.com wrote:

right now GWT will export things if you tell using GWT exporter. In the
GWT 3.0 it'll you can use JsInterfaces etcetera which is much better than
GWT exporter and built into the compiler. It seems like it'd still be very
complicated to build a hybrid app with GWT and JavaScript because you have
to tell the compiler what things to export. Why doesn't GWT just export
everything automatically? This would be a dramatic simplification. I
understand that there might be a small performance cost but I think it'd be
worth it. Doesn't regular javaScript code remain accessible when minified?
I don't see why GWT shouldn't do the same.

GWT uses an optimizing compiler not a transpiler and minimizer, so GWT
does more than just convert java to javascript and minify it. It removes
any code it can determine that is not being used. It also rewrites code
that is used to be far more optimal, which often results in methods/fields
being elided. If all code was exported then it could not perform these
optimizations and the performance would be intolerably slow. I don't know
how GWT exporter works but I presume it is by identifying further entry
points that can't be optimized away.

--
Cheers,

Peter Donald

--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an
email to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.8.0-SNAPSHOT

2015-02-03 Thread Manuel Carrasco Moñino

In the meanwhile you can use a temporary repository updated daily:

https://github.com/manolo/gwt-snapshot/raw/master/

On Tue, Feb 3, 2015 at 12:40 PM, Jens jens.nehlme...@gmail.com wrote:

I was just curious about whats going on (I already use custom GWT trunk
builds). Its just strange to me that an open source project kills its build
server accessibility and snapshot builds from the public and won't say why
(other than we have an issue).

-- J.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/f4c9db34-ef11-4f24-acdf-0336074ff411%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/f4c9db34-ef11-4f24-acdf-0336074ff411%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAs-KDpVn-1E76ANuNP6yXiK1NQWV8B8J60sebegfm7EfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Where to call an Action when user remove an uploaded image in GWTUpload?

2015-01-07 Thread Manuel Carrasco Moñino

Answered in stackoverflow, let me know if this solution works for you.


On Tue, Sep 30, 2014 at 11:38 AM, Tom henry...@gmail.com wrote:

 I am using GWTUpload , the library is in here
 https://code.google.com/p/gwtupload/

 The Example code at client side found on that website has this structure:

  // Attach an image to the pictures viewer
 private OnLoadPreloadedImageHandler showImage = new 
 OnLoadPreloadedImageHandler() {
 public void onLoad(PreloadedImage image) {
   //showImageFlowPanel code solution 1
   image.setWidth(75px);
   showImageFlowPanel.add(image);
 }
 };


 private IUploader.OnFinishUploaderHandler onFinishUploaderHandler = new 
 IUploader.OnFinishUploaderHandler() {
   public void onFinish(IUploader uploader) {
 if (uploader.getStatus() == Status.SUCCESS) {

   new PreloadedImage(uploader.fileUrl(), showImage);

   UploadedInfo info = uploader.getServerInfo();

   String headShotImageUrl=http://+Window.Location.getHost()+/ 
 +images/uploaded/+info.message;
   //headShotImage code solution 2
   if(!.equals(headShotImageUrl)  
 UriUtils.isSafeUri(headShotImageUrl)){
   headShotImage.setUrl(UriUtils.fromString(headShotImageUrl));
   }



 }
   }
 };

 The example uses showImageFlowPanel (solution 1) to store the image but I
 want to store the image inside headShotImage which take the url after
 user uploaded image successfully, see the headShotImage (solution 2) code
 above.

 Ok, the headShotImage code work fine but I dont know how to remove it when
 users remove the image. If I use showImageFlowPanel as in the solution 1
 then the program remove the image automatically for me and I do not need to
 do anything.

 So my question is *Where to call an Action when user remove an uploaded
 image in GWTUpload?*


 http://stackoverflow.com/questions/26117517/where-to-call-an-action-when-user-remove-an-uploaded-image-in-gwtupload

 --
 You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-web-toolkit@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Invesigating OOPHM chrome dev tools js extension creation

2014-11-24 Thread Manuel Carrasco Moñino

Leif at Vaadin already was exploring the possibility of having a devmode in
pure JS, his experimental work is at https://github.com/Legioth/devmodejs,
afaik although it's feasible (he succeed debugging some stuff) it is very
slow, apart from other issues like memory allocation, etc.

On Mon, Nov 24, 2014 at 6:49 PM, 'Ray Cromwell' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

If you mean replacing the DevMode plugin with pure JS in Chrome Dev
Tools, I don't think it's practical. You need synchronously re-entrant
code execution. Javascript's only synchronous blocking call is XHR
sync. But you also need re-entrancy, and when you are
debugging/pausing execution, you run into additional hurdles. Many
people have tried hacks to do this, with Applets, with XHR, it's
possible in theory if you rewrite all code sent to the browser to use
continuations. I would advocate just continuing to make IDE
integration with SDM better.

On Mon, Nov 24, 2014 at 9:38 AM, Brandon Donnelson
branflake2...@gmail.com wrote:
I'm investigating the possibility of creating a js chrome dev tools
extension to talk OOPHM with GPE OOPHM. So far it looks potential
feasible
to use what's in place on in GPE to do the communicating with some new
browser extension. Although I do see having to write some new
bidirectional
options to sync up the log entries and maybe adding some new parsing
ability
for sdm output.

For those who might know some about the OOPHM process, would you see any
hang ups in writing a chrome dev tools javascript extension?

Thanks,
Brandon

https://groups.google.com/d/msgid/google-web-toolkit-contributors/a1363906-faef-427d-b8f6-c9209dce891a%40googlegroups.com
.
For more options, visit https://groups.google.com/d/optout.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAPVRV7cKBFJeg8S-1B_Mzw%2BGMb21k-3qkRO-jzb%2B0-hQkR%3D4VQ%40mail.gmail.com
.
For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAuJ0AAKE-tPxty%3DtEkjnPkhP-n7sDp_PGvwW8DCOnEpcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Not able to run any GWTTestCase

2014-11-15 Thread Manuel Carrasco Moñino

Julien could you explain how are you trying to run tests, I mean if you are
using ant and what parameters you are using. I have just checked out master
and run non gwt tests, and everything went ok:
$ ant clean buildonly; (cd user  ant test.nongwt)

Can you try the same? what ant and java versions are you using?



On Fri, Nov 14, 2014 at 10:46 PM, 'Roberto Lublinerman' via GWT
Contributors google-web-toolkit-contributors@googlegroups.com wrote:

 This looks awfully a class path issue. Did you ant clean before building?

 On Fri, Nov 14, 2014 at 3:06 AM, Julien Dramaix julien.dram...@gmail.com
 wrote:

 I've updated my master branch (of the GWT-core project) the with the
 remote and now I'm not able to run any GWT test cases included in the
 project. I receive first this error:


 java.lang.NoSuchFieldError: VOID
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.isGetter(JSORestrictionsChecker.java:294)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsTypeMethodsForOverloads(JSORestrictionsChecker.java:341)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsType(JSORestrictionsChecker.java:262)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkType(JSORestrictionsChecker.java:368)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.visit(JSORestrictionsChecker.java:239)
 at
 org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDeclaration.java:1286)
 at
 org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.traverse(CompilationUnitDeclaration.java:712)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:601)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:524)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater$UnitProcessorImpl.process(CompilationStateBuilder.java:99)
 at
 com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.process(JdtCompiler.java:384)
 at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:470)
 at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:985)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:339)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:580)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:513)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:499)
 at
 com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:668)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1312)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277)
 at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671)
 at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)
 at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)
 at
 org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
 at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
 at
 com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74)
 at
 com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211)
 at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)


 Then each test case fails with:
 java.lang.NullPointerException
 at
 com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:714)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1321)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277)
 at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671)
 at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)
 at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)
 at
 org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
 at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
 at
 com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74)
 at
 com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211)
 at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)


 I'm sure something is wrong locally but I don't see what. Any hint ?

 Julien

 --
 You received this message because you are subscribed to the Google Groups
 GWT Contributors group.
 To unsubscribe from this

Re: [gwt-contrib] JsInterop retrofit

2014-11-01 Thread Manuel Carrasco Moñino

After reading, and playing with some stub code based on these ideas, I come
to the conclusion than 'native' is almost perfect from the point of view of
a gwt developer.

We want pure java syntax and simplicity, and any other conventions like
DSLs or magic interface names, etc, could obscure the understanding
existing code,  or trying to figure out how to implement something.

For java developers 'native' means that the platform knows how to deal with
this method, and in the case of gwt this is true and intuitive, meaning
that 'this is native because it's implemented natively in JS'.

The compiler ability to automatically resolve native methods, could be very
useful not only for JsInterop but for many other cases where we use them.

Hence any getter or setter could be automatically written by the compiler
if it does not have the jsni fragment. For instance in
c.g.g.d.c.StyleElement we could get rid of all of the jsni fragments and
just write methods declaration

 public final native void setCssText(String cssText);
If the compiler does this, we could save thousands of line of code in jsni
fragments in the gwt core, also in elemental, and in several other 3 party
libraries.

Even, we could have an annotation to deal with simple JSNI code instead of
using c++ comment blocks to change the default implementation:

 @Jsni(return $doc.head || $doc.getElementsByTagName('head')[0])
 public final native void getHead();


Also it would be nice if the compiler is able to deal directly with type
conversion and it is able to box returned values: java arrays to jsArrays,
js numbers to java types, etc. This will make gwt developer experience
better.

Related with testing, I think that because we already use the GWTTestCase
to run JRE tests (returning module null), it should be not difficult to
modify it and return proxies of classes implementing native methods ant
throwing sensible messages to the user telling what methods are used, etc.

Coming back to JsInterop, I agree that native methods is an easy solution,
probably not so difficult to implement, and definitively solves many
problems like inheritance, static methods, constructors, etc.




On Sat, Nov 1, 2014 at 6:52 AM, 'Goktug Gokdogan' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 I finally had some time to think about JsInterop and how to abstract
 browser APIs.

 I will try to summarize my thought process and different options that I
 have played with so that you could get a better understanding where I'm
 coming from and I hope it will provide good documentation for future.

 So I started by playing with the static functions, constructors and how to
 represent that with the current JsInterop semantics.

 First I started with the original approach: use @JsType on an interface
 and use some simple conventions to generate the rest:

 @JsType(prototype = Object)interface JsObject extends Auto_JsObject {

   static JsObject of(Object obj) {
 return obj instanceof JsObject ? (JsObject) obj : null;
   }

   interface Static {
 String[] keys(JsObject obj);
 JsObject defineProperties(JsObject obj, JsObject props);
   }

   interface constructors {
 void constructor(String param);
   }

   boolean hasOwnProperty(String prop);
   boolean isPrototypeOf(JsObject prop);
 }

 
 then with the annotation processor following code will be generated:

 interface Auto_JsObject {

 public static JsObject newInstance(String param) {
   return js(new Object($0), param);
 }

 public static String[] keys(JsObject obj) {
   return js(Object.keys($0), obj);
 }

 public static JsObject defineProperties(JsObject obj, JsObject props) {
   ...
 }

 @PrototypeOfJsType(JsObject.class)
 public static class prototype {
JsObject constructor(String param) { return null}
boolean hasOwnProperty(String prop) { return false; };
boolean isPrototypeOf(JsObject prop) { return false; };
 }
 }

 

 And it looks like following when used:

   MyObject extends JsObject.prototype {}

   JsObject.keys( ... );

   JsObject.newInstance( ... );

   JsObject.of(new Object());

 
 One of the advantages of this is; I can additionally generate a special
 method named statics() that returns an instance of JsObject.Static where
 we forward all calls to the static methods. This is pretty useful for
 people who care about pure unit testing.

 Although this solution is not ideal due to need for extending a separate
 class (i.e. JsObject.prototype), it looks reasonably good at first sight.
 But there is one major gotcha: it doesn't work!

 The reason is, according to here
 http://docs.oracle.com/javase/tutorial/java/IandI/override.html unlike
 static methods in real classes, static methods in interfaces are not
 'inherited' by subclasses.

 So I stepped backed and started questioning what we are doing here.

 We basically creating a DSL but this DSL is trying to enhance the very
 same class where it

Re: [gwt-contrib] GWT 2.7.0-RC1 Smoke testing update

2014-10-28 Thread Manuel Carrasco Moñino

On Tue, Oct 28, 2014 at 4:05 PM, 'Daniel Kurka' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 Hi all,

 the smoke testing for the release showed up a couple of problems, some of
 them need to be fixed before we put RC1 out others can wait until the final
 release.



- Dev mode test do not work: issue 8967
https://code.google.com/p/google-web-toolkit/issues/detail?id=8967
- Smoke tests fail with GPE since gwt-codeserver.jar is missing on the
classpath. We need to either modify GPE or put codeserver classes into
gwt-dev
- GWT designer crashes: see screenshot
https://drive.google.com/file/d/0B-K8EZ6jAAQrVzdweDhiTE5iQlU/view
- JSON Sample does not work since the yahoo search returns a 404

 Can somebody please take a look at updating the JSON Sample to use a
 different service for the actual search?


Ok I'll do



 -Daniel


  --
 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
 email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiptX2h5qZ7DJg0XiZqbAGMfJJX_m8jT4%2BVDA9z1%3DeEF1Q%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiptX2h5qZ7DJg0XiZqbAGMfJJX_m8jT4%2BVDA9z1%3DeEF1Q%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.


-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAvw6vGei_i50si7P%3DD6H%3DGVii0RQXHt2hbkmk0dixjO%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7.0-RC1 Smoke testing update

2014-10-28 Thread Manuel Carrasco Moñino

Fixed the JSON example, it was not a Yahoo issue since the yahoo response
is in a .json file in the project.
The problem is that 2.7.0 disallows entry classes not implementing the
interface EntryPoint.

https://gwt-review.googlesource.com/#/c/9994/

On Tue, Oct 28, 2014 at 4:07 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

On Tue, Oct 28, 2014 at 4:05 PM, 'Daniel Kurka' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

Hi all,

the smoke testing for the release showed up a couple of problems, some of
them need to be fixed before we put RC1 out others can wait until the final
release.

- Dev mode test do not work: issue 8967
https://code.google.com/p/google-web-toolkit/issues/detail?id=8967
- Smoke tests fail with GPE since gwt-codeserver.jar is missing on
the classpath. We need to either modify GPE or put codeserver classes into
gwt-dev
- GWT designer crashes: see screenshot
https://drive.google.com/file/d/0B-K8EZ6jAAQrVzdweDhiTE5iQlU/view
- JSON Sample does not work since the yahoo search returns a 404

Can somebody please take a look at updating the JSON Sample to use a
different service for the actual search?

Ok I'll do

-Daniel

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiptX2h5qZ7DJg0XiZqbAGMfJJX_m8jT4%2BVDA9z1%3DeEF1Q%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiptX2h5qZ7DJg0XiZqbAGMfJJX_m8jT4%2BVDA9z1%3DeEF1Q%40mail.gmail.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtK0MoG8VW0Pi20VJV2n5UrFJGEtKW5X_DUH%3D7%2BBtL22A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to use Elemental

2014-10-27 Thread Manuel Carrasco Moñino

Have you tried to run your code in superdev-mode or compiled ?

On Sun, Oct 26, 2014 at 9:01 PM, Steve poogleandr...@gmail.com wrote:

 It seems i can no longer instantiate objects as i was doing before since
 using Elemental.

 I'm getting errors on this line for some reason:

 Image imgPlay = new Image(img/Blue_Play_Button_Pressed_Down.svg);

 I tried changing it to Image imgPlay = new Image(); but got the same
 error. This works fine when i'm not referencing Elemental.

 The DevMode console displayed the following:

 Caused by: com.google.gwt.core.client.JavaScriptException: (String) :
 Invoking an instance method on a null instance
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
 at
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
 at
 com.google.gwt.dev.shell.ModuleSpace.createJavaScriptException(ModuleSpace.java:80)
 at
 com.google.gwt.dev.shell.ModuleSpace.createJavaScriptException(ModuleSpace.java:64)
 at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:60)
 at
 com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172)
 at
 com.google.gwt.dev.shell.BrowserChannelServer.reactToMessagesWhileWaitingForReturn(BrowserChannelServer.java:338)
 at
 com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:219)
 at
 com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:136)
 at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:576)
 at
 com.google.gwt.dev.shell.ModuleSpace.invokeNativeVoid(ModuleSpace.java:304)
 at
 com.google.gwt.dev.shell.JavaScriptHost.invokeNativeVoid(JavaScriptHost.java:107)
 at
 com.google.gwt.user.client.impl.DOMImplStandard.initEventSystem(DOMImplStandard.java)
 at
 com.google.gwt.user.client.impl.DOMImpl.maybeInitializeEventSystem(DOMImpl.java:181)
 at
 com.google.gwt.user.client.impl.DOMImplStandard.sinkEvents(DOMImplStandard.java:216)
 at com.google.gwt.user.client.DOM.sinkEvents(DOM.java:1361)
 at com.google.gwt.user.client.Event$.sinkEvents(Event.java:597)
 at
 com.google.gwt.user.client.ui.Image$UnclippedState.init(Image.java:376)
 at com.google.gwt.user.client.ui.Image.init(Image.java:510)
 at
 com.example.elem.client.ElementalDemo.onModuleLoad(ElementalDemo.java:31)


 On Sunday, 26 October 2014 19:32:54 UTC, Jens wrote:

 Please could someone share any thoughts?


 Putting gwt-elemental.jar on class path and inheriting
 elemental.Elemental is fine and it should work.

 When you see failed to load the module you usually see the reason in
 the DevMode console. We can't guess reasons.

 -- J.

  --
 You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-web-toolkit@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7 snapshot and Eclipse Plugin

2014-10-21 Thread Manuel Carrasco Moñino

You shouldn't put never that .jar in your classpath.
GPE takes care of adding it to the launcher classpath when you run
superdevmode and your gwt is not 2.7.

On Tue, Oct 21, 2014 at 2:31 PM, Matic Petek maticpe...@gmail.com wrote:

I have superdevmode-launcher-legacy.jar in classpath and it is not
compatible with GWT 2.7.
Regards,
Matic

On Friday, September 5, 2014 5:40:55 PM UTC+2, Brandon Donnelson wrote:

I suspect the sdk isn't what you think it is if its not working. Can you
check the classpath and see if it was updated?

On Monday, September 1, 2014 6:09:18 AM UTC-7, Matic Petek wrote:

Hi,
I would like to test new compile per file option, but we run our
project from Eclipse and we don't use Maven. So I have perform the
following steps :
1) Download JAR files from https://oss.sonatype.org/
content/repositories/google-snapshots/com/google/gwt/
gwt-servlet.jar
gwt-user.jar
gwt-dev.jar
gwt-codeserver.jar

on 1.9.2014 date

2) Create new Google - Web Toolkit configuration

3) select this configuration on my Eclipse project.

But when I run hosted mode, I get the error below. Any idea if I'm doing
something wrong or Plugin (Kepler SR2, Google Plugin for Eclipse
4.3 3.7.0.v201407290035-rel-r43) is not update-ed with the latest
version of GWT. Thank you.
Regards,
Matic

Exception in thread main java.lang.NoSuchMethodError:
com.google.gwt.dev.javac.CompilationStateBuilder.init(
Lcom/google/gwt/core/ext/TreeLogger;Ljava/io/File;)V

at com.google.gwt.dev.DevModeBase.doStartup(DevModeBase.java:943)

at com.google.gwt.dev.DevMode.doStartup(DevMode.java:498)

at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1097)

at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:863)

at com.google.gwt.dev.DevMode.main(DevMode.java:379)

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/f10b78d5-b358-4d18-abb5-3a9d49a2c429%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/f10b78d5-b358-4d18-abb5-3a9d49a2c429%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAukR_CEsNP9tL95xSUosBVjjqxgpn7Jis0UznO9PMJWWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] SuperDevMode : same time between 2.6.1 and 2.7.0

2014-10-20 Thread Manuel Carrasco Moñino

On Mon, Oct 20, 2014 at 11:24 AM, Raphael Garnier garnier.raph...@gmail.com
 wrote:

 Hi,

 I use SuperDevMode since a while and I'm testing the new features with my
 project and I have exactly the same compilation time between the 2
 versions.
 Is this come from the JsniBundleGenerator of GQuery ?


JsniBundleGenerator is very fast if your js file is in your hard disk,
which seems your case.
If the js is not modified it should be immediate when
incremental-recompiling.




 2.6.1 :

 binding: mgwt.formfactor=desktop

 Compiling module fr.agfahealthcare.cassis.CassisTablet_dev

Computing all possible rebind results for
 'fr.agfahealthcare.gwtmobiscroll.client.GwtMobiscroll.JqueryBundle'

   Rebinding
 fr.agfahealthcare.gwtmobiscroll.client.GwtMobiscroll.JqueryBundle

  Invoking generator com.google.gwt.query.rebind.JsniBundleGenerator

 JsniBundleGenerator - importing external javascript:
 fr/agfahealthcare/gwtmobiscroll/client/resources/js/jquery-2.0.3.min.js

Computing all possible rebind results for
 'fr.agfahealthcare.gwtmobiscroll.client.GwtMobiscroll.MobiscrollJsniResource'

   Rebinding
 fr.agfahealthcare.gwtmobiscroll.client.GwtMobiscroll.MobiscrollJsniResource

  Invoking generator com.google.gwt.query.rebind.JsniBundleGenerator

 JsniBundleGenerator - importing external javascript:
 fr/agfahealthcare/gwtmobiscroll/client/resources/js/mobiscroll.custom-2.9.0.min.js

Computing all possible rebind results for
 'fr.agfahealthcare.cassis.jquery.NProgress.NProgressJsniResource'

   Rebinding
 fr.agfahealthcare.cassis.jquery.NProgress.NProgressJsniResource

  Invoking generator com.google.gwt.query.rebind.JsniBundleGenerator

 JsniBundleGenerator - importing external javascript:
 fr/agfahealthcare/cassis/jquery/nprogress.js

Computing all possible rebind results for
 'fr.agfahealthcare.cassis.CassisFactoryImpl.Factory'

   Rebinding fr.agfahealthcare.cassis.CassisFactoryImpl.Factory

  Invoking generator
 com.google.web.bindery.autobean.gwt.rebind.AutoBeanFactoryGenerator

 [WARN] Error writing out generated unit at
 'D:\Users\AWTCK\Documents\Developpement\Workspace\cassis\cassis-tablet\target\gwtc\fr.agfahealthcare.cassis.CassisTablet_dev\compile-3\gen\fr\agfahealthcare\cassis\consommateurs\DetailTraitementDonneesConsommateurProxyAutoBean_com_google_web_bindery_requestfactory_shared_impl_EntityProxyCategory_com_google_web_bindery_requestfactory_shared_impl_ValueProxyCategory_com_google_web_bindery_requestfactory_shared_impl_BaseProxyCategory.java':
 java.io.FileNotFoundException:
 D:\Users\AWTCK\Documents\Developpement\Workspace\cassis\cassis-tablet\target\gwtc\fr.agfahealthcare.cassis.CassisTablet_dev\compile-3\gen\fr\agfahealthcare\cassis\consommateurs\DetailTraitementDonneesConsommateurProxyAutoBean_com_google_web_bindery_requestfactory_shared_impl_EntityProxyCategory_com_google_web_bindery_requestfactory_shared_impl_ValueProxyCategory_com_google_web_bindery_requestfactory_shared_impl_BaseProxyCategory.java
 (La syntaxe du nom de fichier, de répertoire ou de volume est incorrecte)

 [WARN] Error writing out generated unit at
 'D:\Users\AWTCK\Documents\Developpement\Workspace\cassis\cassis-tablet\target\gwtc\fr.agfahealthcare.cassis.CassisTablet_dev\compile-3\gen\fr\agfahealthcare\cassis\consommateurs\nutrition\DonneesHistoriqueConsultationResponseProxyAutoBean_com_google_web_bindery_requestfactory_shared_impl_EntityProxyCategory_com_google_web_bindery_requestfactory_shared_impl_ValueProxyCategory_com_google_web_bindery_requestfactory_shared_impl_BaseProxyCategory.java':
 java.io.FileNotFoundException:
 D:\Users\AWTCK\Documents\Developpement\Workspace\cassis\cassis-tablet\target\gwtc\fr.agfahealthcare.cassis.CassisTablet_dev\compile-3\gen\fr\agfahealthcare\cassis\consommateurs\nutrition\DonneesHistoriqueConsultationResponseProxyAutoBean_com_google_web_bindery_requestfactory_shared_impl_EntityProxyCategory_com_google_web_bindery_requestfactory_shared_impl_ValueProxyCategory_com_google_web_bindery_requestfactory_shared_impl_BaseProxyCategory.java
 (La syntaxe du nom de fichier, de répertoire ou de volume est incorrecte)

 [WARN] Error writing out generated unit at
 'D:\Users\AWTCK\Documents\Developpement\Workspace\cassis\cassis-tablet\target\gwtc\fr.agfahealthcare.cassis.CassisTablet_dev\compile-3\gen\fr\agfahealthcare\cassis\consommateurs\nutrition\MotifHospitalisationConsommateurProxyAutoBean_com_google_web_bindery_requestfactory_shared_impl_EntityProxyCategory_com_google_web_bindery_requestfactory_shared_impl_ValueProxyCategory_com_google_web_bindery_requestfactory_shared_impl_BaseProxyCategory.java':
 java.io.FileNotFoundException:

Re: [gwt-contrib] Build gwtproject?

2014-10-18 Thread Manuel Carrasco Moñino

I have created a task in Jenkins and used it to update the site

The task is private (only admins can see it) and It's not enabled to be run
whenever a new change is done, but after fixing a couple of issues it will
run automatically.

Brandon, could you check that all the stuff you need is there?

On Fri, Oct 17, 2014 at 11:36 AM, Manuel Carrasco Moñino man...@apache.org
wrote:

Shouldn't this be a task in our CI server, so as we always have the most
recent stuff approved and merged?

- Manolo

On Fri, Oct 17, 2014 at 9:28 AM, Julien Dramaix julien.dram...@gmail.com
wrote:

Hi Brandon

I will do that this week end !

Just ping me monday if it doesn't work.

Julien

On Fri, Oct 17, 2014 at 4:34 AM, Brandon Donnelson
branflake2...@gmail.com wrote:

Could gwtproject site be built?

I'm looking for access to these:
http://www.gwtproject.org/doctype/2.7.0/gwt-module.dtd

Thanks,
Brandon

--
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 email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/8f5c5e44-1543-4f64-84f8-0704507bb028%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/8f5c5e44-1543-4f64-84f8-0704507bb028%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D6gRewmZmOt14oNYSrcMjWYR%2BeWnnb3FgEzFrSGm2xwug%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D6gRewmZmOt14oNYSrcMjWYR%2BeWnnb3FgEzFrSGm2xwug%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtYsPc6NBDQoZqPQ8s8isL6uJU8M53p%2B_1-irG7WJDF5Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7.0 beta1

2014-10-18 Thread Manuel Carrasco Moñino

IIRC is because scripts should be guaranteed to be loaded before the
onModuleLoad is run, and it was done with document.write before xsiframe

On Sun, Oct 19, 2014 at 12:12 AM, 'Goktug Gokdogan' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 Is there any fundamental reason why we don't support script tags for
 Cross-Site-IFrame?

 On Sat, Oct 18, 2014 at 2:54 PM, Jens jens.nehlme...@gmail.com wrote:

Invoking Linker Cross-Site-Iframe

   [ERROR] The Cross-Site-Iframe linker does not support script
 tags in the gwt.xml files, but the gwt.xml file (or the gwt.xml files which
 it includes) contains the following script tags:

 html2canvas.min.js

 jquery-1.11.1.min.js

 jquery-ui.min.js

 In order for your application to run correctly, you will need to include
 these tags in your host page directly. In order to avoid this error, you
 will need to remove the script tags from the gwt.xml file, or add this
 property to the gwt.xml file: set-configuration-property 
 name='xsiframe.failIfScriptTag'
 value='FALSE'/


 And with the addition of that configuration property, the GWT
 compile/link now runs to completion:


 But keep in mind that setting the property to FALSE does only prevent the
 compilation error. Your app probably won't work correctly now as it does
 not have access to html2canvas.js and jquery.js. You need to follow the
 suggesting in the error message to fix it (or use ClientBundle +
 ScriptInjector instead)

 -- J.

 --
 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
 email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/be421e07-460a-4453-96d4-5b9b154f4699%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/be421e07-460a-4453-96d4-5b9b154f4699%40googlegroups.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.


  --
 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
 email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA3sDOEbt2iTmrbu_UwU_UN6jT3BYEuq-4kecsm8PGpbXw%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA3sDOEbt2iTmrbu_UwU_UN6jT3BYEuq-4kecsm8PGpbXw%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.


-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAuWa%3DDb7ZHswR9AtgNaxMA%2B-o0vqikBU0Z1oJTuvJ-C4Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Question to Windows users

2014-10-17 Thread Manuel Carrasco Moñino

Could Pants be compiled and run in cygwin ?

On Fri, Oct 17, 2014 at 12:43 PM, Richard Wallis rdwal...@gmail.com wrote:

How big is the VM image?

On Fri, Oct 17, 2014 at 12:06 PM, Thomas Broyer t.bro...@gmail.com
wrote:

Would it be a blocker if you had to use a VM (VirtualBox or boot2docker)
to be able to contribute to GWT (because build tools would only work on
Linux or OS X) ?
You'd still be able to use Eclipse or IntelliJ IDEA to develop, outside
the VM, but actually building the project to produce JAR files would
require Linux (running in a VM).

On the other hand, all you'd have to do to get things working would be to
download the image with everything preinstalled (and possibly call a script
too bootstrap the dev environment), with no other requirement on your
machine than having VirtualBox (or boot2docker; maybe Vagrant)

Just to have an idea if we should rule out Pants as a build tool or not
(Pants might support Windows in the future though).

I'm thinking that maybe we should try to come up with Docker images
and/or Vagrantfile anyway to make things easier for new contributors,
whether they're using Windows, Linux or OS X.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/c37dcd9e-5530-45e7-9f6b-86fd736a6a94%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/c37dcd9e-5530-45e7-9f6b-86fd736a6a94%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEqaEVh0RatrmFoNoHrP9YcV0yg9ddBBKEZ85A8gG46JV-JCfA%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEqaEVh0RatrmFoNoHrP9YcV0yg9ddBBKEZ85A8gG46JV-JCfA%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAuYO_ZF%3D2Roo7Roe%2BzcRUZtjK7L_Dk49wGQvXephgR5Vw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7 release plan

2014-10-09 Thread Manuel Carrasco Moñino

Well, actually there is no official maintainer for elemental, so Ray would
be the most suitable since he introduced elemental to GWT, but as Goktug
said in this thread, he might not have enough time.

What I've tried to do in my patches is to make the existent elemental test
suite run and pass. The suite was never included in our build scripts and
in fact, lately it didn't compile.

Now we have the suite being run in each build and, even there is patch
adding JRE tests for Json and Collections, because they were designed to
run in either JVM and JS.

Thomas split elemental module in three, hence projects can inherit just
Collections, or Json or the entire Elemental.  And Andrei fixed some tests
and code as well.

The three patches Leif point to, are very useful to using elemental-json in
the JVM as a replacement of the controversial org.json, and now with the
test running is much safer to include them.

So if there are no objections, I vote to include those three patches and
jre tests if Thomas agrees, who probably is the maintainer more familiar
with Elemental.

- Manolo



On Thu, Oct 9, 2014 at 7:14 PM, 'Daniel Kurka' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 I think this call is up to the elemental maintainers (manolo  thomas), if
 it breaks any tests I will roll it back since we need a green build to be
 able to branch.

 -Daniel

 On Thu, Oct 9, 2014 at 6:57 PM, 'Brian Slesinsky' via GWT Contributors 
 google-web-toolkit-contributors@googlegroups.com wrote:

 I think this is okay as long as it doesn't cause tests to fail. Elemental
 is quite separate from everything else so it seems low risk. Daniel?


 On Thu, Oct 9, 2014 at 8:57 AM, Leif Åstrand legi...@gmail.com wrote:

 Lots of Elemental patches have been merged in the last few days, but we
 do still have a short list that would be nice to get included.

 https://gwt-review.googlesource.com/#/c/9098/
 https://gwt-review.googlesource.com/#/c/9099/
 https://gwt-review.googlesource.com/#/c/9095/

 The code appears to be in good shape, so it only remains for someone
 with appropriate authority to decide whether the changes are wanted.

 On Thursday, 9 October 2014 16:25:37 UTC+3, Daniel Kurka wrote:

 We are making steady progress towards GWT 2.7. At this point we are not
 accepting any new patches, but we still have a list of issues that we would
 like to include in the upcoming release. This is no guarantee that all of
 them are going to make it but we are trying our best. Also we are holding
 off committing any risky patches to master until we have cut the GWT 2.7
 release branch. I'll ping back GWT contributors once we have done that.
 Please do not commit any patches that do not need to go in.


- Issue 8762
https://code.google.com/p/google-web-toolkit/issues/detail?id=8762:
Migration to android.json from org.json not being complete (Current 
 patch).
Deploy a com.google.gwt.org.json version based of android that the GWT 
 SDK
can depend on and update the pom of the SDK to use it. Include a 
 warning in
the release notes about small the very small incompatibilities between 
 the
two.
- Issue 8613
https://code.google.com/p/google-web-toolkit/issues/detail?id=8613:
Bug fix for ValuePicker
- Issue 8619
https://code.google.com/p/google-web-toolkit/issues/detail?id=8619:
Super dev mode can fail to start on windows if previous dirs are still
locked. SDM will skip deletion of dirs on windows if it fails and emit a
warning. (skybrian)
- Issue 8716
https://code.google.com/p/google-web-toolkit/issues/detail?id=8716:
Package names can collide with class names on case insensitive file 
 system.
John will come up with a fix for GWT 2.7 if it is not to hard to do
(stalcup).
- Issue 8938
https://code.google.com/p/google-web-toolkit/issues/detail?id=8938:
GWT RPC base url is not set correctly for all cases in SDM recompiles.
dankurka will update the implementation to include a full 
 computeScriptBase
implementation.
- GWT RPC policy files should be written to -launcherDir so that
the normal server can use them easily (skybrian)
- verify sample apps are actually compiling in SDM (since it is now
default) (dankurka)
- remove generation of SDM targets in samples since it is now
default (skybrian)
- John found two small issues in incremental. These need to be
fixed for GWT 2.7 (stalcup  rluble)
- Exception links in the chrome dev tools are not clickable (goktug)
- Issue 4236
https://code.google.com/p/google-web-toolkit/issues/detail?id=4236:
NavigatableMap: We would like to include this in GWT 2.7, but it needs 
 more
testing. Ask Andrei to copy all apache testcases and make them work, 
 then
we include it in GWT 2.7 (goktug)
- Removing IE6 references in the code base (niloc)


 -Daniel

  --
 You received this message because you are subscribed to the Google
 Groups

Re: [gwt-contrib] Re: Can't get 'ant test' to pass it times out

2014-10-08 Thread Manuel Carrasco Moñino

Just for your information, I was writing a document explaining how to run
tests from command line, I have taken advantage of this thread to commit a
first version to gerrit, feel free to play with the examples and make
suggestions.

https://gwt-review.googlesource.com/#/c/9552/

On Wed, Oct 8, 2014 at 12:40 PM, Jens jens.nehlme...@gmail.com wrote:

Hmm instead of ant I mostly use Eclipse to run tests. To do so I enable
the GPE plugin for gwt-user/gwt-dev projects in Eclipse and then run tests
as usual. Since GPE picks up the GWT source project as SDK it works quite
well for me.

-- J.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/0916bc14-d1f7-4b9a-be89-f0e2ffb56369%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/0916bc14-d1f7-4b9a-be89-f0e2ffb56369%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAvL4vkAc1iG7_9Yo29qtwftCdHuc8y51bCJxnCz6m0gBw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7 release plan

1.- History mechanism has changed in 2.7 to fulfil modern standards
https://gwt-review.googlesource.com/#/c/5356/. BTW: you should't use
HistoryImpl and in general any Impl class, in general they are private API
2.- Use -XjsInteropMode ONLY in the case that you have a need for
exporting gwt classes to JS or wrapping JS classes in gwt. Otherwise you
could have a increment of size and probably other issues. It is
experimental, even in 2.7.0, so don't use it for production or be prepared
to changes and breakages
3.- Code sizes in 2.6 and 2.7 should be very similar, but there are changes
in many places, so little differences are acceptable. Update to a new
version does not necessary bring a reduction on code size, but other
improvements.

On Fri, Oct 3, 2014 at 1:38 AM, confile michael.gorsk...@googlemail.com
wrote:

Code size explodes when using GWT 2.7 with -XjsInteropMode JS

I compiled the same code with GWT 2.6.1 and GWT 2.7 with argument strict

code size GWT 2.6.1 1.351 MB
code size GWT 2.7 1.361 MB

Then I compiled the same code with -XjsInteropMode JS flag on GWT 2.7

code size 1.601 MB

Why does GWT 2.7 increases the code size in every case and with Interop
even by 300 kb?

Am Freitag, 3. Oktober 2014 00:18:22 UTC+2 schrieb confile:

What is the difference between -XjsInteropMode JS and -XjsInteropMode
CLOSURE?

Am Donnerstag, 2. Oktober 2014 23:49:17 UTC+2 schrieb John Stalcup:

-XjsInteropMode JS

On Thu, Oct 2, 2014 at 2:46 PM, confile michael@googlemail.com
wrote:

How can JsInterop be activated in GWT 2.7? What flag does it?

Am Donnerstag, 2. Oktober 2014 03:22:56 UTC+2 schrieb Brian Slesinsky:

It's experimental and hidden behind a flag, but it's there.

On Wed, Oct 1, 2014 at 6:20 PM, Cristian Rinaldi csri...@gmail.com
wrote:

- JsInterop Preview is part of the release?

El miércoles, 1 de octubre de 2014 16:15:26 UTC-3, Daniel Kurka
escribió:

Hi all,

we just settled on a GWT 2.7 release plan:

- We *code freeze* on *October 7th* and branch for GWT 2.7.
- As soon as we have the *remaining patches submitted*, we put out
a beta1 build, this should be no later than *October 7th.*
- Putting out a *beta1 externally* allows us to collect feedback
on the new super dev mode integration externally as well.
- We are going to *flip incremental to default* tomorrow and *wait
for 1-2 weeks* for google internal feedback, if there is no serious
issues we are going to *put out RC1*
- GWT 2.7 will still be compatible with Java 6.

Patches / Fixes that need to go in:
- Recompile on reload: https://gwt-review.goo
glesource.com/#/c/9323/ (dankurka)
- Sending the wrong permutation to the client in SDM, if no files
have changed (dankurka).
- Investigate why some people are seeing errors with incremental
not restricting to one permutation (dankurka).
- Public directories are not copied o the war directory when using
SDM (skybrian).
- Restore Java 6 compatibility (skybrian).
- Document limitations of JsonUtils.safeEval and discourage usage
(goktug) (promote Json.parse)

Patches that are nice to have:
- Improve exception logging in SDM (goktug).

*If you have any outstanding patches that you thing need to go into
GWT 2.7, please bring them to our attention, by replying to this thread
or
adding me as a reviewer on Gerrit and setting the topic to GWT2.7.*

-Daniel

--
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 email to google-web-toolkit-contributors+unsubscribe@
googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/google-web-toolkit-contributors/1d5a4369-e03d-47ba-b8dd-
5031e5460751%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/1d5a4369-e03d-47ba-b8dd-5031e5460751%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email to google-web-toolkit-contributors+unsubscribe@
googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/google-web-toolkit-contributors/48e8f729-b645-
4534-af9d-c5a9947dffd2%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/48e8f729-b645-4534-af9d-c5a9947dffd2%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7 release plan

There is no plans to upgrade Jetty. It implies some changes in
JettyLauncher and WebServer, I have already a patch for that but not
committed yet because I have not tested enough. If someone else demands it
we could consider to upgrade it.

Anyway I think it should be nice not to bundle jetty in the .jar deployed
in maven repos, but set it as a dependency so as it's easier to experiment
other versions.

On Fri, Oct 3, 2014 at 10:44 AM, Александр Новоселов qui...@gmail.com
wrote:

Will you update to Jetty 9.2 (with JVM 8 support)?
Any link to branch version?

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/ad0b7807-4da7-4a83-844d-dae11c3c786f%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/ad0b7807-4da7-4a83-844d-dae11c3c786f%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAvgNuq2rew1u57KTPwHKXe2jvkjR611nxuEUFOeCh-OpA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7 release plan

On Fri, Oct 3, 2014 at 4:05 PM, confile michael.gorsk...@googlemail.com
wrote:

Well, I need to override HistoryImpl to enable HTML5 pushstate api.

HistoryImpl is now a private class inside History, maybe we could discuss
whether to change its visibility. Maybe @Daniel could help here.

Am Freitag, 3. Oktober 2014 16:01:31 UTC+2 schrieb Manuel Carrasco Moñino:

1.- History mechanism has changed in 2.7 to fulfil modern standards
https://gwt-review.googlesource.com/#/c/5356/. BTW: you should't use
HistoryImpl and in general any Impl class, in general they are private API
2.- Use -XjsInteropMode ONLY in the case that you have a need for
exporting gwt classes to JS or wrapping JS classes in gwt. Otherwise you
could have a increment of size and probably other issues. It is
experimental, even in 2.7.0, so don't use it for production or be prepared
to changes and breakages
3.- Code sizes in 2.6 and 2.7 should be very similar, but there are
changes in many places, so little differences are acceptable. Update to a
new version does not necessary bring a reduction on code size, but other
improvements.

On Fri, Oct 3, 2014 at 1:38 AM, confile michael@googlemail.com
wrote:

Code size explodes when using GWT 2.7 with -XjsInteropMode JS

I compiled the same code with GWT 2.6.1 and GWT 2.7 with argument strict

code size GWT 2.6.1 1.351 MB
code size GWT 2.7 1.361 MB

Then I compiled the same code with -XjsInteropMode JS flag on GWT 2.7

code size 1.601 MB

Why does GWT 2.7 increases the code size in every case and with Interop
even by 300 kb?

Am Freitag, 3. Oktober 2014 00:18:22 UTC+2 schrieb confile:

What is the difference between -XjsInteropMode JS and -XjsInteropMode
CLOSURE?

Am Donnerstag, 2. Oktober 2014 23:49:17 UTC+2 schrieb John Stalcup:

-XjsInteropMode JS

On Thu, Oct 2, 2014 at 2:46 PM, confile michael@googlemail.com
wrote:

How can JsInterop be activated in GWT 2.7? What flag does it?

Am Donnerstag, 2. Oktober 2014 03:22:56 UTC+2 schrieb Brian Slesinsky:

It's experimental and hidden behind a flag, but it's there.

On Wed, Oct 1, 2014 at 6:20 PM, Cristian Rinaldi csri...@gmail.com
wrote:

- JsInterop Preview is part of the release?

El miércoles, 1 de octubre de 2014 16:15:26 UTC-3, Daniel Kurka
escribió:

Hi all,

we just settled on a GWT 2.7 release plan:

- We *code freeze* on *October 7th* and branch for GWT 2.7.
- As soon as we have the *remaining patches submitted*, we put
out a beta1 build, this should be no later than *October 7th.*
- Putting out a *beta1 externally* allows us to collect feedback
on the new super dev mode integration externally as well.
- We are going to *flip incremental to default* tomorrow and *wait
for 1-2 weeks* for google internal feedback, if there is no
serious issues we are going to *put out RC1*
- GWT 2.7 will still be compatible with Java 6.

Patches / Fixes that need to go in:
- Recompile on reload: https://gwt-review.goo
glesource.com/#/c/9323/ (dankurka)
- Sending the wrong permutation to the client in SDM, if no files
have changed (dankurka).
- Investigate why some people are seeing errors with incremental
not restricting to one permutation (dankurka).
- Public directories are not copied o the war directory when
using SDM (skybrian).
- Restore Java 6 compatibility (skybrian).
- Document limitations of JsonUtils.safeEval and discourage usage
(goktug) (promote Json.parse)

Patches that are nice to have:
- Improve exception logging in SDM (goktug).

*If you have any outstanding patches that you thing need to go
into GWT 2.7, please bring them to our attention, by replying to this
thread or adding me as a reviewer on Gerrit and setting the topic to
GWT2.7.*

-Daniel

--
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 email to google-web-toolkit-contributors+unsubscribe@
googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contrib
utors/1d5a4369-e03d-47ba-b8dd-5031e5460751%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/1d5a4369-e03d-47ba-b8dd-5031e5460751%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email to google-web-toolkit-contributors+unsubscribe@
googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/google-web-toolkit-contributors/48e8f729-b645-4534-af9d-
c5a9947dffd2%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/48e8f729-b645-4534-af9d-c5a9947dffd2%40googlegroups.com?utm_medium=emailutm_source

Re: [gwt-contrib] Re: GWT 2.7 release plan

Thanks for the info Thomas, I din't realise that patch.

On Fri, Oct 3, 2014 at 6:34 PM, Thomas Broyer t.bro...@gmail.com wrote:

On Friday, October 3, 2014 4:06:01 PM UTC+2, Manuel Carrasco Moñino wrote:

AFAIK, we can't update Jetty to 9.x because HTMLUnit (used for
JUnitShell/GWTTestCase) depends on Jetty 8.x APIs (WebSockets)
There's been a patch proposed already and it has been abandoned because of
that.

Anyway I think it should be nice not to bundle jetty in the .jar deployed
in maven repos, but set it as a dependency so as it's easier to experiment
other versions.

It could possibly help with some setups but I doubt it'd be that useful.

If we had a modularized GWT then you could avoid depending on gwt-junit,
gwt-devmode-jettylauncher and gwt-codeserver (e.g. when compiling) and live
with Jetty 9.x dependencies in your classpath/buildpath, or we could
possibly provide a gwt-codeserver and/or gwt-devmode-jettylauncher using
using Jetty 9.x; so you'd use Jetty 8.x with gwt-junit to run your
unittests, and you could use Jetty 9.x in DevMode/superDevMode (and benefit
from Jetty 9.x perf improvements for gwt-codeserver?)
It's not possible with our current monolithic artifacts (and build) though.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/d22e2d8b-0bf1-4f17-9805-9fdb944076f5%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/d22e2d8b-0bf1-4f17-9805-9fdb944076f5%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAvKYKh5CYZGrU%2B7NgC8TR1Lnd%2BikpiBZjq1NMv13M%2BDGQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7 release plan

Hi,

There are a bunch of Elemental patches which fix some issues, some of them
manifested when running its test suite which was not enabled, and the
others to use elemental json as a replacement of the controversial
org.json. I know elemental 2.0 would be redesigned or rewritten for 3.0,
but I think we could leave a little bit better version of elemental 1.0 in
2.7.0.

Could anyone take a look to those patches? There is no official maintainer
of it, so maybe Ray is the most suitable reviewer?

Thanks
- Manolo

On Thu, Oct 2, 2014 at 3:22 AM, 'Brian Slesinsky' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

It's experimental and hidden behind a flag, but it's there.

On Wed, Oct 1, 2014 at 6:20 PM, Cristian Rinaldi csrina...@gmail.com
wrote:

- JsInterop Preview is part of the release?

El miércoles, 1 de octubre de 2014 16:15:26 UTC-3, Daniel Kurka escribió:

Hi all,

we just settled on a GWT 2.7 release plan:

- We *code freeze* on *October 7th* and branch for GWT 2.7.
- As soon as we have the *remaining patches submitted*, we put out a
beta1 build, this should be no later than *October 7th.*
- Putting out a *beta1 externally* allows us to collect feedback on
the new super dev mode integration externally as well.
- We are going to *flip incremental to default* tomorrow and *wait for
1-2 weeks* for google internal feedback, if there is no serious issues
we are going to *put out RC1*
- GWT 2.7 will still be compatible with Java 6.

Patches / Fixes that need to go in:
- Recompile on reload: https://gwt-review.googlesource.com/#/c/9323/ (
dankurka)
- Sending the wrong permutation to the client in SDM, if no files have
changed (dankurka).
- Investigate why some people are seeing errors with incremental not
restricting to one permutation (dankurka).
- Public directories are not copied o the war directory when using SDM
(skybrian).
- Restore Java 6 compatibility (skybrian).
- Document limitations of JsonUtils.safeEval and discourage usage
(goktug) (promote Json.parse)

Patches that are nice to have:
- Improve exception logging in SDM (goktug).

*If you have any outstanding patches that you thing need to go into GWT
2.7, please bring them to our attention, by replying to this thread or
adding me as a reviewer on Gerrit and setting the topic to GWT2.7.*

-Daniel

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/1d5a4369-e03d-47ba-b8dd-5031e5460751%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/1d5a4369-e03d-47ba-b8dd-5031e5460751%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2B%2BRBT-M5mAXmj5Ox8iQihjzFFinLM%2Bc57tmdD1JGwEMxKJHAw%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2B%2BRBT-M5mAXmj5Ox8iQihjzFFinLM%2Bc57tmdD1JGwEMxKJHAw%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAvDLRsQFsWV320q2%3Dpvw_oH46N47OvcpCp%3D07wkYbMhgw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: -src in DevMode EntryPoint

There are already some arguments not needed for DevMode which are passed to
the codeserver like -XjsInteropMode, so to me makes sense to add it as well.

On Tue, Sep 30, 2014 at 1:50 AM, Colin Alworth niloc...@gmail.com wrote:

Its possible that we can get away without an explicit way to add this
(like classic Dev Mode has done so far), but -src makes multi-project
development so much saner. No longer do you need to depend on your IDE to
do the Right Thing (i.e. use *that* project as a jar from local maven repo,
but *that* one over there should be raw sources, since the one former has
generated content but the latter is being edited constantly). Leaving this
out puts the onus on the IDE tooling to get it right every time, or provide
an alternate mechanism - you can get pretty close with the (often wrong but
at least easy to customize) Eclipse Run Configuration wiring, but on the
other hand the (totally un-customizable, but at least right 80% of the
time) IDEA Run Configurations that are shipped with Ultimate have to be
right out of the box, or you are just stuck (as is true for 12, 13, and the
14 EAP). I can't speak for Netbeans (though I've seen a recent resurgence
of GWT users making use of it!).

Is there a reason that CodeServer has this feature but DevMode doesn't?
Should DevMode have had it all along, or was this just a hack in CodeServer
that should be phased out?

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/fc562a17-0f4c-4573-9f18-9b5ea13ad723%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/fc562a17-0f4c-4573-9f18-9b5ea13ad723%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAux-mHZB%2Bm4o8rFMyGBROtEi7kXWsyrU%3D6feVgeXdRZFQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Compiler Faiure

On Thu, Oct 2, 2014 at 12:28 AM, 'Ray Cromwell' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

We kind of knew this sort of incompatibility would happen, but I still
think GWT should continue get out of the business of rebasing
everything.

We should even have a version of the JAR that can use
dynamic dependencies.

I think this is a good option. Can we go with it?

On Wed, Oct 1, 2014 at 3:16 PM, Manuel Carrasco Moñino
man...@apache.org wrote:
Thank Roberto, that is the key, everything works if I exclude the asm
transitive dependency in my pom

dependency
groupIdorg.eclipse.jetty/groupId
artifactIdjetty-annotations/artifactId
exclusions
exclusion
artifactIdorg.objectweb.asm/artifactId
groupIdorg.eclipse.jetty.orbit/groupId
/exclusion
/exclusions

On Wed, Oct 1, 2014 at 11:46 PM, 'Roberto Lublinerman' via GWT
Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

This seems to be the error:

java.lang.IncompatibleClassChangeError: class
com.google.gwt.dev.javac.asm.CollectMethodData has interface
org.objectweb.asm.MethodVisitor as super class

and the problem seems to be that you have ASM 5 in your class path.
(It
seems that MethodVisitor was an interface in ASM 4 and is now an
abstract
class.

2.7 no longer rebases ASM

On Wed, Oct 1, 2014 at 2:33 PM, Manuel Carrasco Moñino
man...@apache.org
wrote:

Hi all,

Do anyone knows what could change lately which makes the compiler fail
if
jetty annotations is in your classpath.

The way to reproduce is compiling any project which
jetty-annotations.jar
before before gwt-dev.jar.

Attached trace.

https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtxtLYTr43FBqwm7-CLFMkGVcS2Oi9-vPP6MdpkqqPw_w%40mail.gmail.com
.
For more options, visit https://groups.google.com/d/optout.

https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmTDSDYfCPzVg5o1AEXzHNcrXhLL91iWv_n%2BJsVJ-oNxA%40mail.gmail.com
.
For more options, visit https://groups.google.com/d/optout.

https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAvmpneRqr1LLry_C612U7PsdY-raj9fPo_5ysAJ3qoGaw%40mail.gmail.com
.

For more options, visit https://groups.google.com/d/optout.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAPVRV7fUFGt8ksPPoPTwhxUN2xBjVLLoJ%2B%3DbooMpDoy6cN5wWg%40mail.gmail.com
.
For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAsJLT%2BGtNnx8i3%2Bj6W6L98Dpo1gbEfTjZi_SrfK2AMphQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Compiler Faiure

Thank Thomas for fixing this.

On Thu, Oct 2, 2014 at 3:26 PM, Thomas Broyer t.bro...@gmail.com wrote:

On Thursday, October 2, 2014 2:33:29 PM UTC+2, Manuel Carrasco Moñino
wrote:

On Thu, Oct 2, 2014 at 12:28 AM, 'Ray Cromwell' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

We kind of knew this sort of incompatibility would happen, but I still
think GWT should continue get out of the business of rebasing
everything.

We should even have a version of the JAR that can use
dynamic dependencies.

I think this is a good option. Can we go with it?

I'm currently updating the scripts that push JARs to Maven to unbundle
ASM, along with the POMs to add the dependency on ASM.
I'll also add dependencyManagement to com.google.gwt:gwt and
com.google.web.bindery:requestfactory (aka make them bills of material)
so you could use them with scopeimport/scope in your
dependencyManagement to make sure you use everything with the same version,
even when some deps are transitive (e.g. you use a lib that depends on
gwt-dev with a version different than the one you use for gwt-user;
dependencyManagement helps solve these issues).

Other deps we could easily replace with non-rebased ones are Guava and
Protobuf.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/7b0c9a48-094a-4782-a362-52828a9505ee%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/7b0c9a48-094a-4782-a362-52828a9505ee%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAvun71Xkf2rQc%2BDsJj5%3DiW3LjAQ%3D9gqejzAGXz5TJCkGQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 release plan

On Wed, Oct 1, 2014 at 9:23 PM, 'Brian Slesinsky' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

- Make sure sample apps work with DevMode -superdevmode

I'm planing to do a exhaustive testing this week and verify that last
changes are reliable enough.

- I think we're waiting on a patch to CLDR 25

Patch is ready for review.

On Wed, Oct 1, 2014 at 12:15 PM, 'Daniel Kurka' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

Hi all,

we just settled on a GWT 2.7 release plan:

- We *code freeze* on *October 7th* and branch for GWT 2.7.
- As soon as we have the *remaining patches submitted*, we put out a
beta1 build, this should be no later than *October 7th.*
- Putting out a *beta1 externally* allows us to collect feedback on the
new super dev mode integration externally as well.
- We are going to *flip incremental to default* tomorrow and *wait for
1-2 weeks* for google internal feedback, if there is no serious issues
we are going to *put out RC1*
- GWT 2.7 will still be compatible with Java 6.

Patches / Fixes that need to go in:
- Recompile on reload: https://gwt-review.googlesource.com/#/c/9323/
(dankurka)
- Sending the wrong permutation to the client in SDM, if no files have
changed (dankurka).
- Investigate why some people are seeing errors with incremental not
restricting to one permutation (dankurka).
- Public directories are not copied o the war directory when using SDM
(skybrian).
- Restore Java 6 compatibility (skybrian).
- Document limitations of JsonUtils.safeEval and discourage usage
(goktug) (promote Json.parse)

Patches that are nice to have:
- Improve exception logging in SDM (goktug).

*If you have any outstanding patches that you thing need to go into GWT
2.7, please bring them to our attention, by replying to this thread or
adding me as a reviewer on Gerrit and setting the topic to GWT2.7.*

-Daniel

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirrw0BL1yfX7nxLbH-yVLEofbQM%2BBn-ZtgmriuW56SMNQ%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirrw0BL1yfX7nxLbH-yVLEofbQM%2BBn-ZtgmriuW56SMNQ%40mail.gmail.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2B%2BRBT8y2fE4WQqFeXiJCVwTwD6XbdWiKrR3fH28qzMLvk0Uvg%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2B%2BRBT8y2fE4WQqFeXiJCVwTwD6XbdWiKrR3fH28qzMLvk0Uvg%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtcBQUex7DxTWg64ZSgrLS_PWZnifC06gKbqk-G-ti%2BSQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Compiler Faiure

Hi all,

Do anyone knows what could change lately which makes the compiler fail if
jetty annotations is in your classpath.

The way to reproduce is compiling any project which jetty-annotations.jar
before  before gwt-dev.jar.

Attached trace.

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtxtLYTr43FBqwm7-CLFMkGVcS2Oi9-vPP6MdpkqqPw_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
com.vaadin.prototype.wc:v-demo:war:1.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for 
org.apache.maven.plugins:maven-war-plugin is missing. @ line 207, column 21
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten 
the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
[WARNING] 
[INFO] 
[INFO] Using the builder 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder
 with a thread count of 1
[INFO] 
[INFO] 
[INFO] Building Demo project 1.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ v-demo ---
[INFO] Deleting /Users/manolo/eclipse/luna/v-demo/target
[INFO] 
[INFO] --- maven-resources-plugin:2.5:copy-resources (copy-resources) @ v-demo 
---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ v-demo ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/Users/manolo/eclipse/luna/v-demo/src/main/resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ v-demo ---
[INFO] Compiling 3 source files to 
/Users/manolo/eclipse/luna/v-demo/target/v-demo-1.0-SNAPSHOT/WEB-INF/classes
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
v-demo ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/Users/manolo/eclipse/luna/v-demo/src/test/resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
v-demo ---
[INFO] Not compiling test sources
[INFO] 
[INFO] --- maven-surefire-plugin:2.8.1:test (default-test) @ v-demo ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- gwt-maven-plugin:2.7.0-SNAPSHOT:compile (default) @ v-demo ---
[INFO] auto discovered modules [com.vaadin.prototype.wc.gwt.Demo]
[INFO] Compiling module com.vaadin.prototype.wc.gwt.Demo
[INFO] [ERROR] Unexpected internal compiler error
[INFO] java.lang.IncompatibleClassChangeError: class 
com.google.gwt.dev.javac.asm.CollectMethodData has interface 
org.objectweb.asm.MethodVisitor as super class
[INFO]  at java.lang.ClassLoader.defineClass1(Native Method)
[INFO]  at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
[INFO]  at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
[INFO]  at java.net.URLClassLoader.defineClass(URLClassLoader.java:455)
[INFO]  at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
[INFO]  at java.net.URLClassLoader$1.run(URLClassLoader.java:367)
[INFO]  at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
[INFO]  at java.security.AccessController.doPrivileged(Native Method)
[INFO]  at java.net.URLClassLoader.findClass(URLClassLoader.java:360)
[INFO]  at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
[INFO]  at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
[INFO]  at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
[INFO]  at java.lang.Class.getDeclaredMethods0(Native Method)
[INFO]  at java.lang.Class.privateGetDeclaredMethods(Class.java:2688)
[INFO]  at java.lang.Class.getDeclaredMethod(Class.java:2115)
[INFO]  at 
java.io.ObjectStreamClass.getPrivateMethod(ObjectStreamClass.java:1431)
[INFO]  at java.io.ObjectStreamClass.access$1700(ObjectStreamClass.java:72)
[INFO]  at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:494)
[INFO]  at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:468)
[INFO]  at java.security.AccessController.doPrivileged(Native Method)
[INFO]  at java.io.ObjectStreamClass.init(ObjectStreamClass.java:468)
[INFO]  at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:365)
[INFO]  at

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

I could verify the issue.
A clue, It seems that the last emitted permutation is the only one
un-obfuscated.

As a workaround you can collapse-all-properties, and the result is PRETTY

- Manolo

On Wed, Oct 1, 2014 at 11:27 PM, Julien Dramaix julien.dram...@gmail.com
wrote:

Am I the only one to have this problem ?

On Fri, Sep 26, 2014 at 11:46 PM, Julien Dramaix julien.dram...@gmail.com
wrote:

Dear GWT lovers,

I've just tried to compile several projects with the last snapshot of GWT
2.7.0 using the PRETTY mode flag and several permutations. I noticed that
only one js file (corresponding to one permutation) is emitted with non
obfuscated javascript. The other files for each other permutation contains
obfuscated javascript.

I've tested with GWT 2.6.1 and everything works as expected: all the
files contain only non-obfuscated javascript.

Julien

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAu9usDYZNNoC%3D5NN-_sTpEpS4B%2B%3DnayuNsQb2N6iGaTKg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

Roberto, in my case this is the command line:

/Library/Java/JavaVirtualMachines/jdk1.8.0_05.jdk/Contents/Home/jre/bin/java
-Xmx512m -classpath . . . -Dgwt.persistentunitcachedir= target
com.google.gwt.dev.Compiler -logLevel INFO -style PRETTY -war
target/v-demo-1.0-SNAPSHOT -localWorkers 8 -draftCompile -XnocheckCasts
-compileReport -XfragmentCount -1 -sourceLevel 1.7 -XjsInteropMode NONE
-extra target/extra -gen v-demo/target/.generated
com.vaadin.prototype.wc.gwt.Demo

I'm compiling with maven using gwt-maven-2.7-SNAPSHOT and trunk GWT.

On Wed, Oct 1, 2014 at 11:44 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

I could verify the issue.
A clue, It seems that the last emitted permutation is the only one
un-obfuscated.

As a workaround you can collapse-all-properties, and the result is PRETTY

- Manolo

On Wed, Oct 1, 2014 at 11:27 PM, Julien Dramaix julien.dram...@gmail.com
wrote:

Am I the only one to have this problem ?

On Fri, Sep 26, 2014 at 11:46 PM, Julien Dramaix
julien.dram...@gmail.com wrote:

Dear GWT lovers,

I've just tried to compile several projects with the last snapshot of
GWT 2.7.0 using the PRETTY mode flag and several permutations. I noticed
that only one js file (corresponding to one permutation) is emitted with
non obfuscated javascript. The other files for each other permutation
contains obfuscated javascript.

I've tested with GWT 2.6.1 and everything works as expected: all the
files contain only non-obfuscated javascript.

Julien

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtsJqs-Cs%2Bvk0R70mabgyEr9pY%2BZzJM0TkJfMLKkOw6tw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Compiler Faiure

Thank Roberto, that is the key, everything works if I exclude the asm
transitive dependency in my pom

On Wed, Oct 1, 2014 at 11:46 PM, 'Roberto Lublinerman' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

This seems to be the error:

java.lang.IncompatibleClassChangeError: class
com.google.gwt.dev.javac.asm.CollectMethodData has interface
org.objectweb.asm.MethodVisitor as super class

and the problem seems to be that you have ASM 5 in your class path. (It
seems that MethodVisitor was an interface in ASM 4 and is now an abstract
class.

2.7 no longer rebases ASM

On Wed, Oct 1, 2014 at 2:33 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

Hi all,

Do anyone knows what could change lately which makes the compiler fail if
jetty annotations is in your classpath.

The way to reproduce is compiling any project which jetty-annotations.jar
before before gwt-dev.jar.

Attached trace.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtxtLYTr43FBqwm7-CLFMkGVcS2Oi9-vPP6MdpkqqPw_w%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtxtLYTr43FBqwm7-CLFMkGVcS2Oi9-vPP6MdpkqqPw_w%40mail.gmail.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmTDSDYfCPzVg5o1AEXzHNcrXhLL91iWv_n%2BJsVJ-oNxA%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmTDSDYfCPzVg5o1AEXzHNcrXhLL91iWv_n%2BJsVJ-oNxA%40mail.gmail.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAvmpneRqr1LLry_C612U7PsdY-raj9fPo_5ysAJ3qoGaw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

On Thu, Oct 2, 2014 at 1:23 AM, 'Roberto Lublinerman' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

I'll look into it.

Manolo,
Do you know what is the Building Unknown Task that is showing in our
jenkins instance?

There is a hidden task in our server which is only accessible for
authenticated users, I use it for manually building gwt against an specific
commit. I launched this built to check that the broken test was fixed with
John's commit https://gwt-review.googlesource.com/#/c/9400/ . Jenkins show
it to indicate that a worker is busy.

On Wed, Oct 1, 2014 at 2:49 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

Roberto, in my case this is the command line:

I'm compiling with maven using gwt-maven-2.7-SNAPSHOT and trunk GWT.

On Wed, Oct 1, 2014 at 11:44 PM, Manuel Carrasco Moñino
man...@apache.org wrote:

I could verify the issue.
A clue, It seems that the last emitted permutation is the only one
un-obfuscated.

As a workaround you can collapse-all-properties, and the result is PRETTY

- Manolo

On Wed, Oct 1, 2014 at 11:27 PM, Julien Dramaix
julien.dram...@gmail.com wrote:

Am I the only one to have this problem ?

On Fri, Sep 26, 2014 at 11:46 PM, Julien Dramaix
julien.dram...@gmail.com wrote:

Dear GWT lovers,

I've just tried to compile several projects with the last snapshot of
GWT 2.7.0 using the PRETTY mode flag and several permutations. I noticed
that only one js file (corresponding to one permutation) is emitted with
non obfuscated javascript. The other files for each other permutation
contains obfuscated javascript.

I've tested with GWT 2.6.1 and everything works as expected: all the
files contain only non-obfuscated javascript.

Julien

--
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 email to
google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtsJqs-Cs%2Bvk0R70mabgyEr9pY%2BZzJM0TkJfMLKkOw6tw%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtsJqs-Cs%2Bvk0R70mabgyEr9pY%2BZzJM0TkJfMLKkOw6tw%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gkFyx%2B6FySa_i5on1GLTzf3tV9rLi7HOD3sHtdhgysyiA%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gkFyx%2B6FySa_i5on1GLTzf3tV9rLi7HOD3sHtdhgysyiA%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAuqJqy8B2ndD6wh0n%3DX7VWARnLyFWa2Cgsvx7w46GDCqw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: DevMode with -superDevMode hardcoded -noprecompile

2014-09-30 Thread Manuel Carrasco Moñino

On Mon, Sep 29, 2014 at 6:32 PM, Brandon Donnelson branflake2...@gmail.com
wrote:

 We had a reset.css included in the public app folder which was used by
 adding it to the static html header. In this case I just moved it to the
 gwt xml module so it was available on gwt app initialization.


yep, anything from public folder should be prepended by
GWT.getModuleBaseForStaticFiles folder, since it's not available in
index.html you have to reference css files through gwt.xml.  The patch does
not help here.
I don't think it's a good idea to update the war folder with the static
files from public folder since the dev mode launcher does not know anything
about those files.




 Copying the web resources on SDM init would be nifty. I'm not sure what
 the commit is doing yet, but that looks like it should work just fine.

 What I suspect may happen is folks that are used to using DevMode and
 since its resource are available on running it b/c of the compiler locking
 up the web request, some will complain of 404 requests.

 I agree, any speed gains are a bonus so I like the noprecompile and let
 the browser trigger it. DevMode does that but it locks the browser up.

 Thanks,
 Brandon

 On Monday, September 29, 2014 2:45:31 AM UTC-7, Thomas Broyer wrote:



 On Sunday, September 28, 2014 10:06:12 PM UTC+2, Ray Cromwell wrote:

 This was fixed recently I think, where all public resources are copied
 even if no precompile happens.


 That's the change I linked to, but it's copying the resources to the
 CodeServer's own temporary folder IIUC.
 What Brandon is asking for is copying those same files to the folder
 pointed to by the -war passed to DevMode, hence my suggestion.



 On Sun, Sep 28, 2014 at 3:02 AM, Thomas Broyer t.br...@gmail.com
 wrote:

 I'd rather say DevMode's -superDevMode should share the same behavior
 as https://gwt-review.googlesource.com/#/c/9137/4/
 dev/codeserver/java/com/google/gwt/dev/codeserver/Recompiler.java


 On Sunday, September 28, 2014 10:56:17 AM UTC+2, Brandon Donnelson
 wrote:

 I've been thinking it might be good to be able to turn off
 noprecompile when using super dev mode.

 I found with dev mode, the resources in the public folder could be
 added to html page, although with -superDevMode on the resources are not
 available till the first compile happens and this happens after the web
 page is requested and if any public resources are included in the web page
 there will be a 404 until the first compile. DevMode blocks until the
 compile is done so the pattern of resource inclusion has to change for
 those using public resources in the html page.

 Anyway do you think -noprecompile should be an option to turn off when
 running DevMode with SuperDevMode?

 Thoughts?

 Thanks,
 Brandon

  --
 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 email to google-web-toolkit-contributors+unsubscribe@
 googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/
 msgid/google-web-toolkit-contributors/65212555-efa9-
 493c-aead-031566baaf20%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/65212555-efa9-493c-aead-031566baaf20%40googlegroups.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.


  --
 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
 email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/437e1a32-14c9-45de-87a9-7710f4e76fb1%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/437e1a32-14c9-45de-87a9-7710f4e76fb1%40googlegroups.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.


-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtmh0HB275zoVzBV%3DVOn9H79wX7G7%2B_qEEx%3D_b9KcXRTA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: DevMode with -superDevMode hardcoded -noprecompile

2014-09-29 Thread Manuel Carrasco Moñino

Brandon, out of curiosity, how do you use those static files in your .html?
do you use absolute urls like http://codeserver:port/ModuleName/my_asset.css?
Because if you use relative paths they dont work in SDM since you have to
prepend the getModuleBaseForStaticFiles() path.

IMO, we should use -noprecompile always, because we dont know what
permutation is going to be used until the browser hits the codeserver, and
it's a bad idea to spend time precompiling for all permutations. Anyway, I
agree that all static files should be copied.

For legacy versions of GWT we could consider to make optional that
parameter, let's discuss it in the legacy-jar project in github.


On Mon, Sep 29, 2014 at 1:02 AM, Brandon Donnelson branflake2...@gmail.com
wrote:

 Cool that would be nifty.

 I've been testing with GWT 2.7.0-SNAPSHOT and GWT 2.6.1, although I
 haven't noticed those resources getting copied, although maybe its so new
 the snapshot doesn't have it yet.

 On Sunday, September 28, 2014 1:06:12 PM UTC-7, Ray Cromwell wrote:

 This was fixed recently I think, where all public resources are copied
 even if no precompile happens.


 On Sun, Sep 28, 2014 at 3:02 AM, Thomas Broyer t.br...@gmail.com wrote:

 I'd rather say DevMode's -superDevMode should share the same behavior as
 https://gwt-review.googlesource.com/#/c/9137/4/dev/codeserver/java/com/
 google/gwt/dev/codeserver/Recompiler.java


 On Sunday, September 28, 2014 10:56:17 AM UTC+2, Brandon Donnelson wrote:

 I've been thinking it might be good to be able to turn off noprecompile
 when using super dev mode.

 I found with dev mode, the resources in the public folder could be
 added to html page, although with -superDevMode on the resources are not
 available till the first compile happens and this happens after the web
 page is requested and if any public resources are included in the web page
 there will be a 404 until the first compile. DevMode blocks until the
 compile is done so the pattern of resource inclusion has to change for
 those using public resources in the html page.

 Anyway do you think -noprecompile should be an option to turn off when
 running DevMode with SuperDevMode?

 Thoughts?

 Thanks,
 Brandon

  --
 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 email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
 .
 To view this discussion on the web visit https://groups.google.com/d/
 msgid/google-web-toolkit-contributors/65212555-efa9-
 493c-aead-031566baaf20%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/65212555-efa9-493c-aead-031566baaf20%40googlegroups.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.


  --
 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
 email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/0e254f1e-b2c0-46ef-962f-0aa24b52f292%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/0e254f1e-b2c0-46ef-962f-0aa24b52f292%40googlegroups.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.


-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtLBHttgjD7jXh6kXTZhFGcSmH7zyZRiytYrvtc%3D03CrQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: minor sdm bug

2014-09-29 Thread Manuel Carrasco Moñino

On Mon, Sep 29, 2014 at 6:37 PM, Brandon Donnelson branflake2...@gmail.com
wrote:

I'll change my comment some. :)

I know its the nocache.js is getting cached after much testing with GPE
switching back in forth. So the question is should the compiler update
nocache.js each time?

The problem here is not updating the .nocache.js which is being updated,
but remove the nocache.js.gz if the folder was not cleaned previously. I
think this could be added to SuperDevModeListener.

On Monday, September 29, 2014 9:35:35 AM UTC-7, Brandon Donnelson wrote:

If you get the re-compiled issue, delete the target or compiled folder, I
suspect the nocache.js is cached and has to be deleted by hand. This will
happen when switching back in forth between devmode and super dev mode.

On Sunday, September 28, 2014 4:21:45 PM UTC-7, Stephen Haberman wrote:

Hey,

I was trying SDM on a project today, via the -superDevMode flag that
was added to DevMode (great work).

It worked really well on one project, and then on another I kept
getting the GWT needs (re)compiled that's from the old
module.nocache.js.

Turns out I had a module.nocache.js.gz artifact that was from some
previous compile I had done (with Precompress included), and Jetty was
serving this old .js.gz as the preferred version of the nocache.js file.

So, I'm not super familiar with where/when the files get generated, but
maybe SDM could detect/delete/update the potentially-stale .js.gz
version of the nocache.js file?

Thanks,
Stephen

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/e8a1cc47-2870-485c-a948-82c8df3f494b%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/e8a1cc47-2870-485c-a948-82c8df3f494b%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAv37j0piOatMfygz4E-0uj_HTNnYL4Ru2oL_Sdc4RSYEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: gwt-maven-plugin 2.7.0-SNAPSHOT

2014-09-16 Thread Manuel Carrasco Moñino

Works like a charm.

Thanks.
- Manolo

On Tue, Sep 16, 2014 at 11:27 AM, Thomas Broyer t.bro...@gmail.com wrote:

 Fixed in master, and new snapshot deployed.


 On Monday, September 15, 2014 11:52:14 PM UTC+2, Thomas Broyer wrote:

 Doh, don't know why, I'm passing nosuperDevMode if superDevMode is false,
 as if it's enabled by default in GWT. Will fix as soon as I find a computer.
 Le 15 sept. 2014 20:45, Manuel Carrasco Moñino man...@apache.org a
 écrit :

 Hi Thomas,

 I've tried the snapshot and seems that DevMode with -superDevMode option
 is not being passed.
 I tried either, set superDevModetrue/superDevMode in my pom.xml and
 run mvn gwt:run -Dgwt.superDevMode=true  but in both cases DevMode.main
 is not receiving the -superDevMode argument.

 Am I doing something wrong?

 - Manolo


 On Sun, Sep 14, 2014 at 5:07 AM, Thomas Broyer t.bro...@gmail.com
 wrote:

 Hi all,

 I spent some hours updating the gwt-maven-plugin to GWT 2.7.0-SNAPSHOT,
 and just deployed a snapshot to the https://nexus.codehaus.org
 /content/repositories/snapshots/ repository.

 You should thus be able to test GWT 2.7.0-SNAPSHOT more easily by
 switching to gwt-maven-plugin 2.7.0-SNAPSHOT.

 Feedback welcome, both on the plugin and on GWT.

 --
 You received this message because you are subscribed to the Google
 Groups Google Web Toolkit group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-web-toolkit@
 googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.


  --
 You received this message because you are subscribed to a topic in the
 Google Groups Google Web Toolkit group.
 To unsubscribe from this topic, visit https://groups.google.com/d/
 topic/google-web-toolkit/gFPCB3-nJIc/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-web-toolkit@googlegroups.com
 .
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.

  --
 You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-web-toolkit@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: gwt-maven-plugin 2.7.0-SNAPSHOT

2014-09-15 Thread Manuel Carrasco Moñino

Hi Thomas,

I've tried the snapshot and seems that DevMode with -superDevMode option is
not being passed.
I tried either, set superDevModetrue/superDevMode in my pom.xml and run mvn
gwt:run -Dgwt.superDevMode=true  but in both cases DevMode.main is not
receiving the -superDevMode argument.

Am I doing something wrong?

- Manolo


On Sun, Sep 14, 2014 at 5:07 AM, Thomas Broyer t.bro...@gmail.com wrote:

 Hi all,

 I spent some hours updating the gwt-maven-plugin to GWT 2.7.0-SNAPSHOT,
 and just deployed a snapshot to the https://nexus.codehaus.
 org/content/repositories/snapshots/ repository.

 You should thus be able to test GWT 2.7.0-SNAPSHOT more easily by
 switching to gwt-maven-plugin 2.7.0-SNAPSHOT.

 Feedback welcome, both on the plugin and on GWT.

 --
 You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-web-toolkit@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 requiring Java7 for development - Action needed

2014-09-11 Thread Manuel Carrasco Moñino

+1 to java7

On Thu, Sep 11, 2014 at 11:10 PM, Andy Stevko andy.ste...@gmail.com wrote:

+1 on moving to java 7
On Sep 11, 2014 10:50 AM, 'Daniel Kurka' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

Hi all,

while bringing GSS support into GWT, I discovered that the closure
styleheets compiler actually requires Java7.
This means that we either have to do a back port of the compiler (I
haven't looked at it seriously) or require Java7 for development with GWT
(probably only if you are using CssResource).

I really like your input on this and if I do not hear any strong
objections, I will go ahead with using the Java7 version of closure
stylesheets and thus we will require Java7 for GWT development.

Note: This does not impact deployment of any GWT apps. You can still run
a GWT app on a Java6 container, this will only affect developers on their
machines.

-Daniel

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujip-hsvuE7-NghZGJ0HL007yjCaE5mMX2126Gag4KUJ7Ug%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujip-hsvuE7-NghZGJ0HL007yjCaE5mMX2126Gag4KUJ7Ug%40mail.gmail.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CANKsVVkcWHKMuCBkAcqAAWj1DU0AfkHp3PGn%2B7atR4XG5yqKQQ%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CANKsVVkcWHKMuCBkAcqAAWj1DU0AfkHp3PGn%2B7atR4XG5yqKQQ%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAu%2ByBJt51MO2puE9eAaNbOMaQJ615Mg07_Ci5Pz6TUUjg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Is it necessary to use JVM arg -Dgwt.codeserver.port=9876 for serialization?

2014-09-05 Thread Manuel Carrasco Moñino

Brandon, the argument is considered in both: the legacy jar and 2.7.0, and
it's set after the SDM port has been computed.

I have already tested it and works fine, even with the -noserver set since
it's done in the SuperDevModeListener.

- Manolo

On Fri, Sep 5, 2014 at 7:04 PM, Brandon Donnelson branflake2...@gmail.com
wrote:

Hi Manolo,

I wanted to confirm something just to make the jvm rpc serialization arg
is taken into account when working with the legacy jar, which is going to
be embedded in Eclipse. And if not, I could bake it in to the Eclipse the
jvm args if needed when SDM is turned on. I'm going to do some testing
tonight to verify if this path could be a end user issue. I'm wrapping up
the GPE PR requests, but could add this if we thought it was a benefit to
the end user development workflow.

The rpc tests I did didn't show a problem so far, but I suspect thats
because thats because its ok. It's probably only an issue when people use
-noserver. I'll verify.

Thanks for the Help Jens,

Brandon

On Friday, September 5, 2014 9:55:55 AM UTC-7, Jens wrote:

It is only required for GWT-RPC with SDM because SDM might produce new
*.gwt.rpc policy files that the server must know.

As it is a server side property and you don't know which server a
developer will use I don't think the IDE can help to add that parameter.
However if a developer uses DevMode -superDevMode then the embedded Jetty
server spawned by GWT should be configured with GWT-RPC in mind.

-- J.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/51d5f8bf-a881-4583-9ec8-b532e7b2ad01%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/51d5f8bf-a881-4583-9ec8-b532e7b2ad01%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAt7UU%3D8Kd-Q%3DCCGWYuDNL%3Doei18uwxmkdhKebJgcM9%2BbQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Snapshot and maven

2014-08-21 Thread Manuel Carrasco Moñino

The repo structure is ok, your maven should download the metadata file [1]
which has a reference to the last snapshot index then it should continue
downloading the pom [2] and jar [3] files.

Maybe something wrong in your local repo cache, try to force updating
snapshots running:
 mvn -U clean package
or removing
 ~/.m2/repository/com/google/gwt/gwt-user/2.7.0-SNAPSHOT

- Manolo

[1]
https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-user/2.7.0-SNAPSHOT/maven-metadata.xml
[2]
https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-user/2.7.0-SNAPSHOT/gwt-user-2.7.0-20140820.063656-32.pom
[3]
https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-user/2.7.0-SNAPSHOT/gwt-user-2.7.0-20140820.063656-32.jar


On Thu, Aug 21, 2014 at 3:24 PM, Julien Dramaix julien.dram...@gmail.com
wrote:

 Dear GWT lovers,

 I'm trying to test the last GWT snapshot but I cannot configure maven to
 use it.

 I've added the following repo:

 repositories
 repository
 idgwt-sonatype-snapshots/id
 urlhttps://oss.sonatype.org/content/repositories/google/url
 snapshotsenabledtrue/enabled/snapshots
 releasesenabledfalse/enabled/releases
 /repository
 /repositories

 and use the following version: 2.7.0-SNAPSHOT

 But Maven is not able to resolve dependencies:

 Downloading:
 https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-user/2.7.0-SNAPSHOT/gwt-user-2.7.0-SNAPSHOT.pom
 [WARNING] The POM for com.google.gwt:gwt-user:jar:2.7.0-SNAPSHOT is
 missing, no dependency information available
 Downloading:
 https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-dev/2.7.0-SNAPSHOT/gwt-dev-2.7.0-SNAPSHOT.pom
 [WARNING] The POM for com.google.gwt:gwt-dev:jar:2.7.0-SNAPSHOT is
 missing, no dependency information available
 Downloading:
 https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-servlet/2.7.0-SNAPSHOT/gwt-servlet-2.7.0-SNAPSHOT.pom
 [WARNING] The POM for com.google.gwt:gwt-servlet:jar:2.7.0-SNAPSHOT is
 missing, no dependency information available

 I've looked into the directories

 https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-user/2.7.0-SNAPSHOT/

 https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-dev/2.7.0-SNAPSHOT/

 https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-servlet/2.7.0-SNAPSHOT/

 and indeed the pom files are missing.

 Am I missing something ?

 Julien

 --
 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
 email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4eduxbj5Z6FiVtw1H%2Bj%2BHhbzT6h1274Pq9VSJXF4wW0Q%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4eduxbj5Z6FiVtw1H%2Bj%2BHhbzT6h1274Pq9VSJXF4wW0Q%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.


-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAveCmt9UnaQYESVOd9FYhKD-0tHYq%3D8fxxny_4sk3gm1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Snapshot and maven

2014-08-21 Thread Manuel Carrasco Moñino

Right, both contain the same snapshot versions. Our jenkins CI server is
pushing to the google-snapshots folder, hence some process else should be
mirroring to the google one after a while, that is the reason for
differences in sha1/md5. I think the best choice is to point to the url you
suggest.

- Manolo


On Thu, Aug 21, 2014 at 4:35 PM, Colin Alworth niloc...@gmail.com wrote:

 For what its worth, we use a slightly different snapshot url:
 https://oss.sonatype.org/content/repositories/google-snapshots/. This
 appears to only contain snapshots instead of releases and snapshots.

 The /google/ url for whatever reason has a newer md5 and sha1 for the
 maven-metadata.xml file, but the dates/sizes on everything else seem to be
 consistent.


 On Thu, Aug 21, 2014 at 9:33 AM, Julien Dramaix julien.dram...@gmail.com
 wrote:

 indeed mvn clean install -U does the trick...

 Thanks Manolo


 On Thu, Aug 21, 2014 at 4:24 PM, Manuel Carrasco Moñino 
 man...@apache.org wrote:

 The repo structure is ok, your maven should download the metadata file
 [1] which has a reference to the last snapshot index then it should
 continue downloading the pom [2] and jar [3] files.

 Maybe something wrong in your local repo cache, try to force updating
 snapshots running:
  mvn -U clean package
 or removing
  ~/.m2/repository/com/google/gwt/gwt-user/2.7.0-SNAPSHOT

 - Manolo

 [1]
 https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-user/2.7.0-SNAPSHOT/maven-metadata.xml
 [2]
 https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-user/2.7.0-SNAPSHOT/gwt-user-2.7.0-20140820.063656-32.pom
 [3]
 https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-user/2.7.0-SNAPSHOT/gwt-user-2.7.0-20140820.063656-32.jar


 On Thu, Aug 21, 2014 at 3:24 PM, Julien Dramaix 
 julien.dram...@gmail.com wrote:

 Dear GWT lovers,

 I'm trying to test the last GWT snapshot but I cannot configure maven
 to use it.

 I've added the following repo:

 repositories
 repository
 idgwt-sonatype-snapshots/id
 urlhttps://oss.sonatype.org/content/repositories/google
 /url
 snapshotsenabledtrue/enabled/snapshots
 releasesenabledfalse/enabled/releases
 /repository
 /repositories

 and use the following version: 2.7.0-SNAPSHOT

 But Maven is not able to resolve dependencies:

 Downloading:
 https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-user/2.7.0-SNAPSHOT/gwt-user-2.7.0-SNAPSHOT.pom
 [WARNING] The POM for com.google.gwt:gwt-user:jar:2.7.0-SNAPSHOT is
 missing, no dependency information available
 Downloading:
 https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-dev/2.7.0-SNAPSHOT/gwt-dev-2.7.0-SNAPSHOT.pom
 [WARNING] The POM for com.google.gwt:gwt-dev:jar:2.7.0-SNAPSHOT is
 missing, no dependency information available
 Downloading:
 https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-servlet/2.7.0-SNAPSHOT/gwt-servlet-2.7.0-SNAPSHOT.pom
 [WARNING] The POM for com.google.gwt:gwt-servlet:jar:2.7.0-SNAPSHOT is
 missing, no dependency information available

 I've looked into the directories

 https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-user/2.7.0-SNAPSHOT/

 https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-dev/2.7.0-SNAPSHOT/

 https://oss.sonatype.org/content/repositories/google/com/google/gwt/gwt-servlet/2.7.0-SNAPSHOT/

 and indeed the pom files are missing.

 Am I missing something ?

 Julien

 --
 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 email to
 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4eduxbj5Z6FiVtw1H%2Bj%2BHhbzT6h1274Pq9VSJXF4wW0Q%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4eduxbj5Z6FiVtw1H%2Bj%2BHhbzT6h1274Pq9VSJXF4wW0Q%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.


  --
 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 email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
 .
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAveCmt9UnaQYESVOd9FYhKD-0tHYq%3D8fxxny_4sk3gm1Q%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAveCmt9UnaQYESVOd9FYhKD-0tHYq%3D8fxxny_4sk3gm1Q%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.


  --
 You received this message because you are subscribed to the Google Groups
 GWT Contributors group.
 To unsubscribe from this group

Re: [gwt-contrib] Discussion: Elemental Json

2014-08-06 Thread Manuel Carrasco Moñino

On Sat, Aug 2, 2014 at 2:55 AM, 'Ray Cromwell' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

It is likely that all of the non-collections stuff is going to be
totally redone with JsInterop.
The actual collections interfaces (ArrayOf, etc) as well as Json, we
may keep because it is useful to to have JRE implementations to work
in a shared context.

Sounds well, so we can trust that they will remain in Elemental, and the
API should be similar, right?

However, the implementations backing those are likely to be completely
rewritten to use JsInterop. I don't mind splitting things up in
elemental if they want. My gut feeling is that Elemental 2.0 may have
a completely different package structure.

Any plans for Elemental 2.0? Someone working on it?

In the meanwhile, I've done a couple of fixes so as tests can be run in
builds, next will be a patch for passing Json and Collections tests in JRE,
sounds it reasonable for you? could you take a look in gerrit?

On Fri, Aug 1, 2014 at 8:07 AM, Manuel Carrasco Moñino
man...@apache.org wrote:

Hi all

There is a patch [1] from Thomas in gerrit for spliting elemental
apparently
in 3 libraries:
- elemental-collections
- elemental-json
- elemental

1.- What are the plans with elemental-json and elemental-collections?
2.- Are they though to replace some similar stuff in gwt-user like
JsonUtils?
3.- Could it replace Json code in server side depending org.json?
4.- Is someone working on spliting the code?

Thanks
- Manolo

[1] https://gwt-review.googlesource.com/#/c/4210/

https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtc9z3nbmrfz0Ev%3D3SSFk%3DPZJY%2BBtk_03xOgiVwReHTrQ%40mail.gmail.com
.
For more options, visit https://groups.google.com/d/optout.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAPVRV7dvDF1SLoeJzGSidOmuQizEY5TvNfMvf_gPxenA_YYE%3DA%40mail.gmail.com
.
For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAsRWyL4Ve7gOykHGWO0iu9NrMwnxb%3DiK9g%2BypgAaxHSWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Discussion: Elemental Json

2014-08-01 Thread Manuel Carrasco Moñino

Hi all

There is a patch [1] from Thomas in gerrit for spliting elemental
apparently in 3 libraries:
- elemental-collections
- elemental-json
- elemental

1.- What are the plans with elemental-json and elemental-collections?
2.- Are they though to replace some similar stuff in gwt-user like
JsonUtils?
3.- Could it replace Json code in server side depending org.json?
4.- Is someone working on spliting the code?


Thanks
- Manolo

[1] https://gwt-review.googlesource.com/#/c/4210/

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtc9z3nbmrfz0Ev%3D3SSFk%3DPZJY%2BBtk_03xOgiVwReHTrQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Developer Plugin no longer works with Chrome on Linux

2014-07-29 Thread Manuel Carrasco Moñino

Forgot the link to the post:
http://www.sencha.com/blog/getting-started-with-gwt-super-dev-mode


On Tue, Jul 29, 2014 at 8:48 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

 Here you have a post about what is coming in eclipse to run superdev mode
 with just a click.

 For inpatients, just use GWT-2.7.0-SNAPSHOT and include the
 gwt-codeserver.jar in your project classpath,  run dev mode as usual in
 your project, and finally edit the launcher configuration and add the
 -superDevMode parameter.

 - Manolo


 On Mon, Jul 28, 2014 at 10:17 AM, Thomas Broyer t.bro...@gmail.com
 wrote:

 I think the goal is to eventually replace all mentions of DevMode in
 gwtproject.org with SuperDevMode with up-to-date information (now that
 DevMode is only usable in IE and GWTTestCase, but because of GWTTestCase we
 still need to talk about how code is executed in the JVM with a JS/JVM
 bridge, rather than compiled to JS).
 From my POV, this would build on my blog post and StackOverflow answer.
 …but note that in GWT 2.7 we introduce an easier way to run SDM with a
 single command-line, with the two servers in a single process (just like in
 DevMode, with an embedded Jetty server to host the webapp)

 Feel free to propose patches to gwtproject.org if you have ideas (or
 just come discuss them on gwt-contrib); you have my permission to copy text
 from my blog post and StackOverflow answer.


 On Mon, Jul 28, 2014 at 5:35 AM, Blake McBride blake1...@gmail.com
 wrote:

 Embarrassing.  Yes, that is exactly what I was looking for.  I've seen
 the link but never followed it because I thought it was meant to go into
 highly technical details that I wasn't yet up to.

 It is clear that a lot of people are having a lot of trouble with SDM.
  There are a few good pages that contain valuable information on setting up
 SDM.  In spite of this, many people are still having a lot of trouble.
  Perhaps I can propose this.

 1.  Create a single master SDM page.  Perhaps it would start with one
 of the already existing pages that tell a person how to setup SDM.

 2.  The page would contain very detailed information on setting up and
 using SDM in eclipse, intelliJ, and NetBeans.

 3.  It would contain links to all of the places this list points people
 to.

 4.  It would be updated very often - even if the procedure hasn't
 changed.  Every time someone is confused with the instructions, rather than
 just answer them, the master page will get updated to clarify the point
 in question.

 Every time some asks how to setup or use SDM, we can refer them to that
 single (root) page.  If we do this, that page will quickly evolve into a
 single source containing the most up-to-date, complete, and unambiguous
 instructions.

 Just a thought.

 Thanks.

 Blake


 On Sun, Jul 27, 2014 at 3:39 PM, Thomas Broyer t.bro...@gmail.com
 wrote:



 On Sunday, July 27, 2014 5:22:53 PM UTC+2, Blake McBride wrote:

 I spent a little time many months ago trying to get SDM working.  I
 think I succeeded but was very surprised about the number of steps
 required.  The thing that surprised me most, however, was discovering that
 I had to have two servers running (if I am correct) - an app server, and a
 code server.  All of the docs I've seen provide the steps but never 
 explain
 at a higher level what is going on (unless you understand far more 
 internal
 details than many of us).  The biggest difficulty occurs because the
 instructions were leading me down the path of two servers but I kept
 fighting it - trying to get one server to perform both functions.  The
 fight occurred because I didn't understand what was being attempted.  I
 didn't understand that I needed two servers running.

 So, what is needed is a better up-front description of what you end up
 with (two servers), and a block diagram that depicts the parts and the 
 data
 flow between them.  Understanding this would make the instruction much 
 more
 clear.

 (Sorry if I am totally wrong and confused.  Quite possible.)


 http://blog.ltgt.net/how-does-gwts-super-dev-mode-work/
 Does that help?





 --
 Thomas Broyer
 /tɔ.ma.bʁwa.je/ http://xn--nna.ma.xn--bwa-xxb.je/

 --
 You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-web-toolkit@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.




-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit

Re: GWT Developer Plugin no longer works with Chrome on Linux

2014-07-29 Thread Manuel Carrasco Moñino

Here you have a post about what is coming in eclipse to run superdev mode
with just a click.

For inpatients, just use GWT-2.7.0-SNAPSHOT and include the
gwt-codeserver.jar in your project classpath,  run dev mode as usual in
your project, and finally edit the launcher configuration and add the
-superDevMode parameter.

- Manolo


On Mon, Jul 28, 2014 at 10:17 AM, Thomas Broyer t.bro...@gmail.com wrote:

 I think the goal is to eventually replace all mentions of DevMode in
 gwtproject.org with SuperDevMode with up-to-date information (now that
 DevMode is only usable in IE and GWTTestCase, but because of GWTTestCase we
 still need to talk about how code is executed in the JVM with a JS/JVM
 bridge, rather than compiled to JS).
 From my POV, this would build on my blog post and StackOverflow answer.
 …but note that in GWT 2.7 we introduce an easier way to run SDM with a
 single command-line, with the two servers in a single process (just like in
 DevMode, with an embedded Jetty server to host the webapp)

 Feel free to propose patches to gwtproject.org if you have ideas (or just
 come discuss them on gwt-contrib); you have my permission to copy text from
 my blog post and StackOverflow answer.


 On Mon, Jul 28, 2014 at 5:35 AM, Blake McBride blake1...@gmail.com
 wrote:

 Embarrassing.  Yes, that is exactly what I was looking for.  I've seen
 the link but never followed it because I thought it was meant to go into
 highly technical details that I wasn't yet up to.

 It is clear that a lot of people are having a lot of trouble with SDM.
  There are a few good pages that contain valuable information on setting up
 SDM.  In spite of this, many people are still having a lot of trouble.
  Perhaps I can propose this.

 1.  Create a single master SDM page.  Perhaps it would start with one
 of the already existing pages that tell a person how to setup SDM.

 2.  The page would contain very detailed information on setting up and
 using SDM in eclipse, intelliJ, and NetBeans.

 3.  It would contain links to all of the places this list points people
 to.

 4.  It would be updated very often - even if the procedure hasn't
 changed.  Every time someone is confused with the instructions, rather than
 just answer them, the master page will get updated to clarify the point
 in question.

 Every time some asks how to setup or use SDM, we can refer them to that
 single (root) page.  If we do this, that page will quickly evolve into a
 single source containing the most up-to-date, complete, and unambiguous
 instructions.

 Just a thought.

 Thanks.

 Blake


 On Sun, Jul 27, 2014 at 3:39 PM, Thomas Broyer t.bro...@gmail.com
 wrote:



 On Sunday, July 27, 2014 5:22:53 PM UTC+2, Blake McBride wrote:

 I spent a little time many months ago trying to get SDM working.  I
 think I succeeded but was very surprised about the number of steps
 required.  The thing that surprised me most, however, was discovering that
 I had to have two servers running (if I am correct) - an app server, and a
 code server.  All of the docs I've seen provide the steps but never explain
 at a higher level what is going on (unless you understand far more internal
 details than many of us).  The biggest difficulty occurs because the
 instructions were leading me down the path of two servers but I kept
 fighting it - trying to get one server to perform both functions.  The
 fight occurred because I didn't understand what was being attempted.  I
 didn't understand that I needed two servers running.

 So, what is needed is a better up-front description of what you end up
 with (two servers), and a block diagram that depicts the parts and the data
 flow between them.  Understanding this would make the instruction much more
 clear.

 (Sorry if I am totally wrong and confused.  Quite possible.)


 http://blog.ltgt.net/how-does-gwts-super-dev-mode-work/
 Does that help?





 --
 Thomas Broyer
 /tɔ.ma.bʁwa.je/ http://xn--nna.ma.xn--bwa-xxb.je/

 --
 You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-web-toolkit@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Bad link in GWT Documentation

2014-07-08 Thread Manuel Carrasco Moñino

The main problem is that pushState does not work until IE10 so IE8 and IE9
should show the plain web without menu enhancements, but it seems we are
producing a permutation for them with is messing how it works.
Another problem is that IE10 is executing some bad code and menu does not
work at all but links work fine. IE11 is taking gecko permutation and seems
to work fine.

I'll take a look and try to fix.

- Manolo

On Tue, Jul 8, 2014 at 8:29 AM, stuckagain david.no...@gmail.com wrote:

No,

Don't bother... I am starting to believe that it is caused by some reverse
proxy that does some URL rewriting. I can not reproduce when working from
home.
Enterprise security features have a big impact on productivity :-(

Thanks for the support.

On Tuesday, July 8, 2014 3:15:57 AM UTC+2, Michael Vogt wrote:

I checked with document mode set to IE9 with IE11, and ran in all
kinds of strange behavior when navigating through the menu. Is it
worth to investigate further?

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/216cbcfc-e33f-4e05-93a3-293d311ab1cc%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/216cbcfc-e33f-4e05-93a3-293d311ab1cc%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtiMdq-N8JCLSMW8aAV5GGFwt%3DoEoi84FhypGj0k7_K-A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] JettyLauncher class loader

2014-07-02 Thread Manuel Carrasco Moñino

Brandon, I think you are mixing subjects in this thread.

You have introduced another discussion related with how to run superdevmode
from eclipse, so lets move that discussion to a different channel.

What we wanted to discuss here (Thomas suggestion) is how to improve or get
rid of current class loader hacks in the JettyLauncher.
This has been cause of problems and it does not follow a standard way.

I agree with Thomas and Brian to make a transition to the standard way with
a flag to enable the current way.
But first we have to decide how long are we going to support jetty
launcher, because maybe we can consider remove it in 3.0.

- Manolo

On Wed, Jul 2, 2014 at 12:40 AM, Brandon Donnelson branflake2...@gmail.com
wrote:

After looking at the GPE bootstrapping for DevMode, I think I found a good
way to start the CodeServer, which means two launch configs go when dev
mode is started. Then I could sync up the launch configs in case more than
one, or persist one and not the other. At anyrate there are some options
with out having to worry about accidentally stopping one and not the other.
My demo used CodeServer as the main type although it creates more waves in
changes, and I suspect I could change the main types around, DevMode being
main and this would cause less changes. I think I could have this worked up
in a couple of half days and get back with a demo, screencast for thoughts.
This would mean I could have all the steps wrapped up shortly and it would
work seamlessly for a 2.5.1+.

Eclipse Goals

1. no precompile flag on
2. create a no cache file, with just dev mode, that code server
initializes
3. start the code server, which starts the servlet container, dev
mode, -server flag
4. remove code server flag

- clean compile - generates clean no cache with sum logic
- start sdm
- start servlet container
- start browser
- dev mode on

On Tuesday, July 1, 2014 1:07:48 PM UTC-7, Brandon Donnelson wrote:

After looking at it a bit more, I think it would be nice to add in a
-server argument like DevMode has to the change, but that looks like it
also needs a couple other args like -war. Having the -server arg would
allow for another server type to launch other than the embedded jetty, and
maybe its a matter of providing a separate jetty launcher like appengines
so none of the jetty code is in the main type class that provides the GWT
logic. This way it extracts the responsibility and decouples jetty as a
dependency b/c folks use tomcat, jboss, vaadin, or other backend platform.
Thoughts?

On Tuesday, July 1, 2014 12:19:03 PM UTC-7, Brian Slesinsky wrote:

I don't understand the details enough to make an informed
recommendation, but I think introducing a new entry point is a good time to
transition to the standard way (assuming it is standard).

We could add the backward-compatibility flag if needed after some
testing to see what the breakage would be.

- Brian

On Tue, Jul 1, 2014 at 6:36 AM, Manuel Carrasco Moñino
man...@apache.org wrote:

Following the discussion here: https://gwt-review.
googlesource.com/#/c/8150/2

What do you guys think about changing the way of how embedded jetty
class loader works?

Options:
- leave it as current: a bunch of hacks to load certain classes at first
- modify it to use the standard way: first WEB-INF/lib then classpath
- a mix of both, so as the default is #2 but we maintain a flag for
using #1
- more... ?

--
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 email to google-web-toolkit-contributors+unsubscribe@
googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/google-web-toolkit-contributors/CAM28XAtaxEabPDFt-
2CEFR154GOHcBYMj47BQOVXHUfqvbyGBw%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtaxEabPDFt-2CEFR154GOHcBYMj47BQOVXHUfqvbyGBw%40mail.gmail.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/ae294613-6514-4f1a-a202-cc001dd32425%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/ae294613-6514-4f1a-a202-cc001dd32425%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email

Re: JSNI Javascript promises

2014-06-12 Thread Manuel Carrasco Moñino

Out of curiosity, have you guys tried gwt-query promises? they have the
same syntax than jQuery ones, and work in browser and server sides.
You can see how them work in these slides:
http://slides.gquery.org/gwtcreate/gwtcreate.html#18


On Thu, Jun 12, 2014 at 2:46 PM, Jens jens.nehlme...@gmail.com wrote:

 I have written a Promise library that uses native promises of the browser
 if possible and emulated promises otherwise. I had the same problem for
 native promises. I think it is forbidden to define a function with a name
 catch as it is a keyword however browsers have cheated on that in case of
 native promises.

 In my case I could workaround it by using this[catch](..) instead of
 this.catch(...). Maybe thats possible in your case too.


 -- J.

 --
 You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-web-toolkit@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWTproject site menu

2014-05-21 Thread Manuel Carrasco Moñino

All your suggestions are done and committed to gerrit.

Demo instance has been updated with those changes:
http://gwtproject.gquery.org

- Manolo


On Tue, May 13, 2014 at 9:23 PM, 'Goktug Gokdogan' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 SGTM


 On Tue, May 13, 2014 at 4:26 AM, Julien Dramaix 
 julien.dram...@gmail.comwrote:

   Others:
   - Clicking images shows blank page - perhaps just a deployment issue
 
 
  Don't see this issue, what images do you mean?
 
 
  Click devmode screenshot in
 http://gwtproject.gquery.org/gettingstarted.html

 This issue already exists in the production website. I created a bug to
 track it and I propose to fix it later in another patch :
 https://code.google.com/p/google-web-toolkit/issues/detail?id=8707

  So I think we should either keep the old behavior (i.e. auto-collapse)
 or move the new behavior (no content association for ALL parent menus,
 expand and collapse on click,  NO auto-collapse).
  Again the second option is ideal from my point of view but we may want
 to do it later for reducing the amount work.

 I'm more in favor of the second option also.


  I know this is not a regression - as I noted earlier, all of my
 comments on the second part are already existing problems. The code
 examples was broken when we moved to gwtproject.org.
  - We don't have syntax highlighting for example code (you can see that
 in the pages that you have linked)
  - Content is not formatted at all in some sample codes (see
 http://gwtproject.gquery.org/doc/latest/tutorial/JUnit.html#write) - I
 guess I only saw a few of them.

  We can defer all these stuff, just pointed in case if they are easy to
 fix.

 Indeed we should defer these stuff. During the gwt-meetup, I would like
 to propose and discuss of a possible revamp of the website. During this
 revamp, we could fixe all these problems.

 I propose that Manolo (thanks again for the good job) fixes the behavior
 of the menu according to the Goktug second option and then merge his
 patches in order that we can deploy this version in production. This
 version improves a lot the existing web site and I would like to add a
 search box (using google custom search) asap.

 Julien


 On Mon, May 12, 2014 at 9:54 PM, 'Goktug Gokdogan' via GWT Contributors 
 google-web-toolkit-contributors@googlegroups.com wrote:



 On Sat, May 10, 2014 at 8:02 AM, Manuel Carrasco Moñino 
 man...@apache.org wrote:




 On Sat, May 10, 2014 at 2:33 AM, 'Goktug Gokdogan' via GWT Contributors
 google-web-toolkit-contributors@googlegroups.com wrote:

 Pretty cool. Thanks for all the work. Also special kudos for fixing
 the styling for download page, it is much more elegant now!

 Footer:
  - We are now missing the extra space in the bottom of the pages (the
 one before the footer)


 done

  - The area for the footer is larger and the text is closer to the
 bottom - I think the original spacing was better. Also if you take a look
 at the overview page you will see the footer hides part of the image.


 fixed css



 Others:
  - Clicking images shows blank page - perhaps just a deployment issue


 Don't see this issue, what images do you mean?



 Click devmode screenshot in
 http://gwtproject.gquery.org/gettingstarted.html


   - There is a broken Advanced Topics menu item - I think it is
 mixed up with the Logging menu item.


 Fixed, the logging item was indented wrong


   - I would put Optimize to Advanced topics. Perhaps security and
 i18n as well.


 Done, I think i18n could be out. But anyway is difficult to put the
 edge about what are or not advanced topics


  - Perhaps move Community - Developer Spotlight under Resources?


 done

  - In Resources, we can move gwt surveys to the end of the list


 done



 Below are other issues that doesn't look like regressions. Perhaps we
 can have some other quick wins before publishing the final version?

 Menu:
  - Ideally the arrows shouldn't indent the menu items and instead menu
 items should be aligned by text (e.g. gmail). I'm not sure if you are
 reusing any widgets here; if you aren't reusing we might want to change
 that.


 done. We dont use any widget, just html+css. gquery enhances the list
 adding handlers using selectors.


  - We might want to change how menus behave. I actually like GWT
 Developer pages (e.g. https://developers.google.com/appengine/pricing)
 where menu items that are parents of the other menu items are not used as
 links to a content, instead they serve as a placeholder and
 collapses/expands based when clicked. Also it won't auto collapse existing
 items. I think all together that is more useable.


 I have changed parents with not content (href = #)  to expand/collapse
 menu (See 'Advance topics' in docs).

 Having parent-items with content makes the menu shorter and easy to
 use, like 'side bars' in google code wikis
 https://code.google.com/p/support/wiki/WikiSyntax#Side_navigation

 I'd rather auto-collapse on, but I have set

Re: [gwt-contrib] Re: GWTproject site menu

2014-05-21 Thread Manuel Carrasco Moñino

Hi Julien, it seems sourcemap has not been uploaded, Brian uses them.

- Manolo


On Wed, May 21, 2014 at 12:34 PM, Julien Dramaix
julien.dram...@gmail.comwrote:

 Thanks for the good job Manolo ! The mobile version of the site is really
 better now.

 I've deployed the new version in production : http://www.gwtproject.org/

 Julien


 On Wed, May 21, 2014 at 11:08 AM, Manuel Carrasco Moñino 
 man...@apache.org wrote:

 All your suggestions are done and committed to gerrit.

 Demo instance has been updated with those changes:
 http://gwtproject.gquery.org

 - Manolo


 On Tue, May 13, 2014 at 9:23 PM, 'Goktug Gokdogan' via GWT Contributors 
 google-web-toolkit-contributors@googlegroups.com wrote:

 SGTM


 On Tue, May 13, 2014 at 4:26 AM, Julien Dramaix 
 julien.dram...@gmail.com wrote:

   Others:
   - Clicking images shows blank page - perhaps just a deployment
 issue
 
 
  Don't see this issue, what images do you mean?
 
 
  Click devmode screenshot in
 http://gwtproject.gquery.org/gettingstarted.html

 This issue already exists in the production website. I created a bug to
 track it and I propose to fix it later in another patch :
 https://code.google.com/p/google-web-toolkit/issues/detail?id=8707

  So I think we should either keep the old behavior (i.e.
 auto-collapse) or move the new behavior (no content association for ALL
 parent menus, expand and collapse on click,  NO auto-collapse).
  Again the second option is ideal from my point of view but we may
 want to do it later for reducing the amount work.

 I'm more in favor of the second option also.


  I know this is not a regression - as I noted earlier, all of my
 comments on the second part are already existing problems. The code
 examples was broken when we moved to gwtproject.org.
  - We don't have syntax highlighting for example code (you can see
 that in the pages that you have linked)
  - Content is not formatted at all in some sample codes (see
 http://gwtproject.gquery.org/doc/latest/tutorial/JUnit.html#write) - I
 guess I only saw a few of them.

  We can defer all these stuff, just pointed in case if they are easy
 to fix.

 Indeed we should defer these stuff. During the gwt-meetup, I would like
 to propose and discuss of a possible revamp of the website. During this
 revamp, we could fixe all these problems.

 I propose that Manolo (thanks again for the good job) fixes the
 behavior of the menu according to the Goktug second option and then merge
 his patches in order that we can deploy this version in production. This
 version improves a lot the existing web site and I would like to add a
 search box (using google custom search) asap.

 Julien


 On Mon, May 12, 2014 at 9:54 PM, 'Goktug Gokdogan' via GWT Contributors
 google-web-toolkit-contributors@googlegroups.com wrote:



 On Sat, May 10, 2014 at 8:02 AM, Manuel Carrasco Moñino 
 man...@apache.org wrote:




 On Sat, May 10, 2014 at 2:33 AM, 'Goktug Gokdogan' via GWT
 Contributors google-web-toolkit-contributors@googlegroups.comwrote:

 Pretty cool. Thanks for all the work. Also special kudos for fixing
 the styling for download page, it is much more elegant now!

 Footer:
  - We are now missing the extra space in the bottom of the pages
 (the one before the footer)


 done

  - The area for the footer is larger and the text is closer to the
 bottom - I think the original spacing was better. Also if you take a 
 look
 at the overview page you will see the footer hides part of the image.


 fixed css



 Others:
  - Clicking images shows blank page - perhaps just a deployment issue


 Don't see this issue, what images do you mean?



 Click devmode screenshot in
 http://gwtproject.gquery.org/gettingstarted.html


   - There is a broken Advanced Topics menu item - I think it is
 mixed up with the Logging menu item.


 Fixed, the logging item was indented wrong


   - I would put Optimize to Advanced topics. Perhaps security and
 i18n as well.


 Done, I think i18n could be out. But anyway is difficult to put the
 edge about what are or not advanced topics


  - Perhaps move Community - Developer Spotlight under Resources?


 done

  - In Resources, we can move gwt surveys to the end of the list


 done



 Below are other issues that doesn't look like regressions. Perhaps
 we can have some other quick wins before publishing the final version?

 Menu:
  - Ideally the arrows shouldn't indent the menu items and instead
 menu items should be aligned by text (e.g. gmail). I'm not sure if you 
 are
 reusing any widgets here; if you aren't reusing we might want to change
 that.


 done. We dont use any widget, just html+css. gquery enhances the list
 adding handlers using selectors.


  - We might want to change how menus behave. I actually like GWT
 Developer pages (e.g.
 https://developers.google.com/appengine/pricing) where menu items
 that are parents of the other menu items are not used as links to a
 content, instead they serve as a placeholder and collapses/expands based
 when

Re: [gwt-contrib] Re: GWTproject site menu

2014-05-10 Thread Manuel Carrasco Moñino

On Sat, May 10, 2014 at 2:33 AM, 'Goktug Gokdogan' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

Pretty cool. Thanks for all the work. Also special kudos for fixing the
styling for download page, it is much more elegant now!

Footer:
- We are now missing the extra space in the bottom of the pages (the one
before the footer)

done

- The area for the footer is larger and the text is closer to the bottom -
I think the original spacing was better. Also if you take a look at the
overview page you will see the footer hides part of the image.

fixed css

Others:
- Clicking images shows blank page - perhaps just a deployment issue

Don't see this issue, what images do you mean?

- There is a broken Advanced Topics menu item - I think it is mixed up
with the Logging menu item.

Fixed, the logging item was indented wrong

- I would put Optimize to Advanced topics. Perhaps security and i18n as
well.

Done, I think i18n could be out. But anyway is difficult to put the edge
about what are or not advanced topics

- Perhaps move Community - Developer Spotlight under Resources?

done

- In Resources, we can move gwt surveys to the end of the list

done

Below are other issues that doesn't look like regressions. Perhaps we can
have some other quick wins before publishing the final version?

Menu:
- Ideally the arrows shouldn't indent the menu items and instead menu
items should be aligned by text (e.g. gmail). I'm not sure if you are
reusing any widgets here; if you aren't reusing we might want to change
that.

done. We dont use any widget, just html+css. gquery enhances the list
adding handlers using selectors.

- We might want to change how menus behave. I actually like GWT Developer
pages (e.g. https://developers.google.com/appengine/pricing) where menu
items that are parents of the other menu items are not used as links to a
content, instead they serve as a placeholder and collapses/expands based
when clicked. Also it won't auto collapse existing items. I think all
together that is more useable.

I have changed parents with not content (href = #) to expand/collapse menu
(See 'Advance topics' in docs).

Having parent-items with content makes the menu shorter and easy to use,
like 'side bars' in google code wikis
https://code.google.com/p/support/wiki/WikiSyntax#Side_navigation

I'd rather auto-collapse on, but I have set it off as you prefer.

General:
- We have smaller size font for links (probably regular text font is
larger than it suppose to be).

Fixed

- Looks like you made the body wider which I think is good but making the
whole page right aligned (i.e. all extra space goes to left) is not a good
idea. It looks really bad in widescreen (which many developers has). We
should probably follow a different approach for distributing the space
(e.g. add the extra space to left until a max value is reached).

I dont know if I understand correctly. The width is adjusted based on media
sizes, and I have set 3 sizes: wide desktop, small desktop tablets and
mobile. Also I have changed the font size (16 - 14px) so as there is more
text in the same place, and text alignment (left - justify).

I have adjusted content padding for big desktop, I see correctly the pages,
let me know if that works for you.

- All code samples lost formatting and even some lost line wrapping after
site migration.

Code styling has not changed for code blocks, I see these pages (current
site, demo site) in the same way, maybe there is some other page wrong or
some style interfering

http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsClient.html
http://gwtproject.gquery.org/v2/doc/latest/DevGuideCodingBasicsClient.html

Can you check if you see them in the same way? or send me a link or
screenshot of the page which works wrong?

You can test new changes at http://gwtproject.gquery.org

- Manolo

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAsipeC_DX-bjA9hstM%2B03QBkd6x6SeztgwOtPswX7xdkw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWTproject site menu

2014-05-09 Thread Manuel Carrasco Moñino

@Goktug I have deployed a new demo with the changes in the menu you
suggested. http://gwtproject.gquery.org/v2/

@Jamie In this version I've set 200ms for animations

@Brian, the fact of collapsing unrelated branches is intentional in order
to focus on the active branch. You can open branches clicking on the arrow,
but once you click on a subject, that branch is selected. I've been playing
a long with the menu and see this behaviour much more usable since I don't
have click on other branches for closing them. Anyway I have deployed
another version in http://gwtproject.gquery.org/v3/ with the feature of
collapse-unrelated-branches disabled so as other people can give an opinion.
In this demo sourcemaps are disabled, but in gwtproject they should be
enabled

@Ray, I think that what you say is something called 'sticky footer' which
means that the footer is at the bottom unless the content is large enough.
I have fixed the css in both demos.

Julien and me want to deploy this version at the beginning of next week.

Please check it in desktop and mobile and let us know if you have any
suggestion.

Thanks
- Manolo

On Fri, May 9, 2014 at 12:12 AM, 'Ray Cromwell' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

While not part of this CL, the bottom footer being in the center of the
page on some short pages looks ugly. The footer should always be at least
at the bottom, or offscreen.

On Thu, May 8, 2014 at 2:27 PM, 'Brian Slesinsky' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

If you click Tutorial and then Documentation the animation is a bit
unfortunate. Because the previous menu closes at the same time that the new
one opens, the new menu expands both up and down so that your cursor ends
up pointing to the middle of the new menu, and then you have to wait until
it stops moving to figure out where to move the mouse next. In the old UI,
the menu item you just clicked on never moves.

But I'm not sure what to do about it. Maybe skip animating closing a menu
when it's not the one you clicked on?

Also, it's not in the demo, but we should make sure sourcemap debugging
works with the new version. I sometimes include a link to gwtproject.orgin
browser bug reports since I don't know any other public websites that
have GWT with sourcemaps on. Unfortunately this is going to break any
specific directions I put into the bug reports, but hopefully something
equivalent should work.

- Brian

On Thu, May 8, 2014 at 1:59 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

That's intentional, it is the same behavior than tree menus in google
wikis and GWT trees.
Now the parent item link is only clickable when it has a page associated
(it was not possible in the last version), so the click is handled to load
that page.

On Thu, May 8, 2014 at 6:19 PM, Jens jens.nehlme...@gmail.com wrote:

I noticed that it is not possible anymore to close a menu category by
clicking on the menu item text again. You can now only close a category by
using the triangle icon.

-- J.

--
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 email to
google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/2f99fddc-668c-449a-8e98-2abf26d8a3bd%40googlegroups.comhttps://groups.google.com/d/msgid/google-web-toolkit-contributors/2f99fddc-668c-449a-8e98-2abf26d8a3bd%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAsxeDCVrEHLrMm4icr%2BY-OVh89RBqfDdnbBUi_qyudZaA%40mail.gmail.comhttps://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAsxeDCVrEHLrMm4icr%2BY-OVh89RBqfDdnbBUi_qyudZaA%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2B%2BRBT8z5gtVUbMpkmtLdoykvYv%2BrGgYDT79agjLBG0VzC1X_Q%40mail.gmail.comhttps://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2B%2BRBT8z5gtVUbMpkmtLdoykvYv%2BrGgYDT79agjLBG0VzC1X_Q%40mail.gmail.com

Re: [gwt-contrib] Re: GWTproject site menu

On Thu, May 8, 2014 at 5:07 PM, Jamie Nelson james.nel...@appian.comwrote:

Looks really slick.

My only suggestion is that we turn the animations down to a quarter second
or less.

It is set to 300ms, I will change it to 200 when deploy the demo again.

They look good on big menus, but for single items, it feels needlessly
slow when the animation takes any amount of time.

This message and any attachments are solely for the intended recipient. If
you are not the intended recipient, disclosure, copying, use, or
distribution of the information included in this message is prohibited --
please immediately and permanently delete this message.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/c69adbb1-4ca7-4771-b005-97a31d0f78fa%40googlegroups.comhttps://groups.google.com/d/msgid/google-web-toolkit-contributors/c69adbb1-4ca7-4771-b005-97a31d0f78fa%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAvsxkBFcdx%3DMSW%2BCHGr_eYVzp%2B_LxSevep4g0JoH13U6A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWTproject site menu

I will deploy a new demo with these changes tomorrow.

On Tue, May 6, 2014 at 8:33 PM, 'Goktug Gokdogan' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

Looks better; thanks for the work.

Some suggestions:
- Removes the versions submenu from Downloads as it is already included
as a link from Downloads page.
- Move GWT surveys under resources
- Perhaps we can group Making GWT Better, Life of an Issue, Steering
Committee under a submenu
- Release Notes - drop it from menu? its already linked from Downloads
page.
- In Documentation menu:
- We need to re-order stuff for people who are reading documentation
in a sequential manner.
e.g. Communicate with a server should probably earlier, maybe in
basics?
- We may want Organize Projects and Compile/Debug to be part of coding
basics.
- Drop IE9 specific page from menu
- Perhaps group RequestFactory, Act.Places, Validation, Access., I18N
etc. in Advanced Topics

On Tue, May 6, 2014 at 8:57 AM, Manuel Carrasco Moñino
man...@apache.orgwrote:

Hello,

I have committed some patcheshttps://gwt-review.googlesource.com/#/c/7180/,
and deployed a demo version http://gwtproject.gquery.org so as you
guys can test the new menu distribution.

What I've done based on Thomas suggestion is to maintain a
tochttps://gwt-review.googlesource.com/#/c/7180/17/src/main/resources/toc.mdfile
instead of moving or renaming pages.

Apart from the menu distribution, the demo includes some navigation
fixes, small css changes, and the ability to adapt to mobile screens when
the window is narrowed.

Once this distribution is reviewed I want to focus on updating some
contents, especially outdated pages.

Feel free to give feedback.

- Manolo

[1] https://gwt-review.googlesource.com/#/c/7180/
[2] http://gwtproject.gquery.org
[3]
https://gwt-review.googlesource.com/#/c/7180/17/src/main/resources/toc.md

On Wed, Apr 9, 2014 at 1:36 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

Sorry forgot the link to the document :-(

https://docs.google.com/document/d/1LJm-xDAK23uASwK59JUAnAeaNjPH5dF9N4LWdgSI9Ik/edit

- Manolo

On Wed, Apr 9, 2014 at 1:36 PM, Manuel Carrasco Moñino
man...@apache.org wrote:

Hi all,

Julien and me have created a document with some plans about the
gwtproject.org site.
Please, feel free to add any comment you have.

On Wed, Apr 9, 2014 at 9:28 AM, Julien Dramaix
julien.dram...@gmail.com wrote:

Hi Manolo,

It's something I wanted to do for a while. Let's organize a conf call
to talk about that.

Julien

On Mon, Apr 7, 2014 at 8:40 PM, Daniel Kurka danku...@google.comwrote:

If you move stuff around you will need to make sure that links (also
external) won't break. (we still get a lot of traffic from external
links)

But I think working on the navigation menu of the page is quite
overdue.

-Daniel

On Mon, Apr 7, 2014 at 4:53 PM, Jens jens.nehlme...@gmail.comwrote:

Sounds reasonable :)

-- J.

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
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 email to
google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Google Germany GmbH
*Dienerstr. 12*
*80331 München*

Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Graham Law, Katherine Stephens

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
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 email to
google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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
email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAv_-4R_uR-G40yKbPgV4PpGxLcctXZ%3DR__K%3DuFcoqe8vA%40mail.gmail.comhttps://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAv_-4R_uR-G40yKbPgV4PpGxLcctXZ%3DR__K%3DuFcoqe8vA%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options

Re: [gwt-contrib] Re: GWTproject site menu

On Thu, May 8, 2014 at 6:19 PM, Jens jens.nehlme...@gmail.com wrote:

 I noticed that it is not possible anymore to close a menu category by
 clicking on the menu item text again. You can now only close a category by
 using the triangle icon.

 -- J.

 --
 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
 email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/2f99fddc-668c-449a-8e98-2abf26d8a3bd%40googlegroups.comhttps://groups.google.com/d/msgid/google-web-toolkit-contributors/2f99fddc-668c-449a-8e98-2abf26d8a3bd%40googlegroups.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.


-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtLbo%2BDDYj6LkfdwYQWuFFavK6kDwrosfHhivoGDLCqkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWTproject site menu