Re: GWT Plugin 3.0 fails to download connection reset after a while

[Brandon Donnelson]

@Kommon If you try what Jens tried, downloading from the browser would it 
work for you? 

Are you dropping packets on your nic? 

On Monday, February 26, 2018 at 6:58:26 AM UTC-8, Jens wrote:
>
> Unable to read repository at 
>> http://storage.googleapis.com/gwt-eclipse-plugin/v3/release/plugins/com.gwtplugins.gdt.eclipse.platform_3.0.0.201710131939.jar
>> .
>>
>
> I can download that jar without issues using a browser. Maybe it is some 
> virus scanner or proxy causing the issue.
>
> -- J. 
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Issues with GWT Eclipse Plugin and Eclise Oxygen 1.a

[Brandon Donnelson]

The fix is getting pushed up to the GWT Eclipse Plugin snapshot and release 
now. 

On Friday, October 13, 2017 at 11:18:47 AM UTC-7, Brandon Donnelson wrote:
>
> I'm working on the issue for the GWT Eclipse Plugin. It's fixed in a later 
> version. The Eclipse API has had a regression. 
>
> On Friday, October 13, 2017 at 4:16:53 AM UTC-7, Sebastian wrote:
>>
>> I too use the new GWT Plugin, not the deprecated Google one. 
>> I had to downgrade Eclipse to be able to work and don't remember the 
>> exact complete stack trace, but the top was certainly something like
>>
>> org.eclipse.jdt.internal.core.JavaProject.computePackageFragmentRoots([Lorg/eclipse/jdt/core/IClasspathEntry;ZLjava/util/Map;)[Lorg/eclipse/jdt/core/IPackageFragmentRoot;
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Issues with GWT Eclipse Plugin and Eclise Oxygen 1.a

[Brandon Donnelson]

I'm working on the issue for the GWT Eclipse Plugin. It's fixed in a later 
version. The Eclipse API has had a regression. 

On Friday, October 13, 2017 at 4:16:53 AM UTC-7, Sebastian wrote:
>
> I too use the new GWT Plugin, not the deprecated Google one. 
> I had to downgrade Eclipse to be able to work and don't remember the exact 
> complete stack trace, but the top was certainly something like
>
> org.eclipse.jdt.internal.core.JavaProject.computePackageFragmentRoots([Lorg/eclipse/jdt/core/IClasspathEntry;ZLjava/util/Map;)[Lorg/eclipse/jdt/core/IPackageFragmentRoot;
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Plugin 3.0 fails to download connection reset after a while

[Brandon Donnelson]

All I can suggest is wait and try again. This repo is on Google Cloud 
Storage, so there shouldn't be any issues. 

On Friday, September 15, 2017 at 8:13:43 AM UTC-7, kommon kommon wrote:
>
> I am trying to install GWT plugin 3.0 on latest version of Eclipse Oxygen 
> 2.7. from 
> http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html
>
> I get the following error when it reaches about 26%.
>
> "
> An error occurred while collecting items to be installed
> session context was:(profile=epp.package.jee, 
> phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, 
> action=).
> Unable to read repository at 
> http://storage.googleapis.com/gwt-eclipse-plugin/v3/release/plugins/com.gwtplugins.gdt.eclipse.platform_3.0.0.201707251900.jar
> .
> Connection reset
> Unable to read repository at 
> http://storage.googleapis.com/gwt-eclipse-plugin/v3/release/plugins/com.gwtplugins.gwt.eclipse.core_3.0.0.201707251900.jar
> .
> Connection reset
> "
>
> download speed drops to zero after 50Mb dnld of 
> /com.gwtplugins.gwt.eclipse.core_3.0.0.201707251900.jar
> and after 36 mb for gwtplugins.gdt.eclipse.platform_3.0.0.201707251900.jar.
>
>
> Any idea whats going on and who can solve it?
>
> I added following params to eclipse ini and still no help:
>
> "-Djava.net.preferIPv4Stack=true
> -Dorg.eclipse.equinox.p2.transport.ecf.retry=5
> -Dorg.eclipse.ecf.provider.filetransfer.retrieve.readTimeout=1
> "
>
>
> Thanks for your help.
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Trying to run Super Dev Mode, but getting "Sorry, the GWT Developer Plugin no longer works with Chrome"

[Brandon Donnelson]

I notice you're using the older GPE plugin, I'll suggest jumping to the new 
GWT Eclipse Plugin. It's wired up to handle the switches for super dev 
mode. 

On Thursday, April 20, 2017 at 1:45:06 AM UTC-7, gitzzz87 wrote:
>
> Check the flag
>
>
>
> четверг, 20 апреля 2017 г., 6:07:41 UTC+7 пользователь Tharpa Roberts 
> написал:
>>
>> I am maintaining a legacy application, which uses GWT 2.6.1.  I am trying 
>> to run it in Eclipse.  I have added the line 
>>
>> 
>>
>> to my Acme.gwt.xml file.   I am selecting, "Debug As GWT Development Mode 
>> with Jetty".  When I open it, Chrome tells me, "Sorry, the GWT Developer 
>> Plugin no longer works with Chrome".  
>>
>> I want to use Super Dev Mode.  Why does it think that I want to use 
>> DevMode ?
>>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

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

[Brandon Donnelson]

Nice job!

On Wed, Apr 5, 2017 at 2:42 PM 'Julien Dramaix' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

>
> The beta version of Elemental2 using the JsInterop specification has been
> released on Sonatype today and is available on Maven central.
>
>
> This release introduces the concept of union types (which are heavily used
> in JavaScript) and many more improvements. More information about union
> types can be found in this document
> <https://docs.google.com/document/d/14mQeAGQ9M_5uTTUbzRQzCYETA887dTO-xFLtQhgUXXk/edit?usp=sharing>
> .
>
>
> We also split Elemental into smaller jar files:
>
>
> Jar file
>
> artifact-id
>
> GWT module
>
> elemental2-core.jar
> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-core/1.0.0-beta-1/elemental2-core-1.0.0-beta-1.jar>
>
> elemental2-core
>
> elemental2.core.Core
>
> elemental2-promise.jar
> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-promise/1.0.0-beta-1/elemental2-promise-1.0.0-beta-1.jar>
>
> elemental2-promise
>
> elemental2.promise.Promise
>
> elemental2-dom.jar
> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-dom/1.0.0-beta-1/elemental2-dom-1.0.0-beta-1.jar>
>
> elemental2-dom
>
> elemental2.dom.Dom
>
> elemental2-svg.jar
> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-svg/1.0.0-beta-1/elemental2-svg-1.0.0-beta-1.jar>
>
> elemental2-svg
>
> elemental2.svg.Svg
>
> elemental2-webgl.jar
> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-webgl/1.0.0-beta-1/elemental2-webgl-1.0.0-beta-1.jar>
>
> elemental2-webgl
>
> elemental2.webgl.WebGl
>
> elemental2-media.jar
> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-media/1.0.0-beta-1/elemental2-media-1.0.0-beta-1.jar>
>
> elemental2-media
>
> elemental2.media.Media
>
> elemental2-indexeddb.jar
> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-indexeddb/1.0.0-beta-1/elemental2-indexeddb-1.0.0-beta-1.jar>
>
> elemental2-indexeddb
>
> elemental2.indexeddb.IndexedDb
>
> elemental2-webstorage.jar
> <https://oss.sonatype.org/content/repositories/releases/com/google/elemental2/elemental2-webstorage/1.0.0-beta-1/elemental2-webstorage-1.0.0-beta-1.jar>
>
> elemental2-webstorage
>
> elemental2.webstorage.WebStorage
>
>
>
> You can try them by downloading the jar files or adding Maven dependencies:
>
>
> 
>
>  com.google.elemental2
>
>  ${artifact-id}
>
>  1.0.0-beta-1
>
> 
>
>
> Then inherit the right gwt module in your gwt.xml file.
>
>
> This beta version works only with the latest HEAD_SNAPSHOT release of GWT
> <https://oss.sonatype.org/content/repositories/google-snapshots/com/google/gwt/gwt/HEAD-SNAPSHOT/>
> .
>
>
> We’ve also released a beta version of JsInterop.base. This library
> contains base classes and utilities that provide access to JavaScript
> language constructs that are not available in pure Java.
>
>
> You can try it by downloading the jar file
> <https://oss.sonatype.org/content/repositories/releases/com/google/jsinterop/base/1.0.0-beta-1/base-1.0.0-beta-1.jar>
> or use the following Maven dependency:
>
>
> 
>
>  com.google.jsinterop
>
>  base
>
>  1.0.0-beta-1
>
> 
>
>
> Don’t hesitate to report any bugs, issues, concerns you have on this
> mailing list.
>
>
> Important note: They are beta releases and future updates (up until the
> final release) may break code!
>
>
> -Julien
>
>
> --
>
> Julien Dramaix |  Software Engineer |  dram...@google.com |  650-750-6053
> <(650)%20750-6053>
>
> --
> 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/CABXeq2QsTarhDKbYmz0y1SOrjpuFNdoNmAnvAYKacO1f4rLcLg%40mail.gmail.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABXeq2QsTarhDKbYmz0y1SOrjpuFNdoNmAnvAYKacO1f4rLcLg%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
*Brandon Donnelson*
GXT Support Engineer
<http://www.facebook.com/senchainc> <http://twitter.c

[gwt-contrib] Stopping Dev Mode (DevMode) Launcher Enhancements

[Brandon Donnelson]

I'd like to discontinue enhancements with anything related to DevMode and 
focus on all development, fixes, enhancements around the Code Server 
launcher only. Not that it needs to be fixed, but with any development 
going forward, I'd push folks into using the Code Server to launch GWT Dev 
Mode (super development mode). There are so many edge cases with using the 
embedded jetty or Dev Mode launcher, it's finally got to me. I think things 
need to be made simpler and focus on the modern debugging should be out 
front. 

I may be in a mood, because there is a lot of code to maintain around this. 
So I'm asking if this seems to drastic at this point? 

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/02ef6806-5c87-4dc2-b658-3cd1900546c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: GWT Eclipse Plugin, Option to share analytics.

[Brandon Donnelson]

It's on by default. Not sure there is much to be afraid of with stats, 
since lots of folks have moved over to the plugin. 

I'm attaching the latest stats for it. This is good to have, it provides 
some fuel to modify it. 

On Wednesday, March 1, 2017 at 2:46:44 AM UTC-8, Matic Petek wrote:
>
> +1 for On by default. This plugin is Brain + Community work and it is fear 
> to know what the usage is.
>
> On Tuesday, February 28, 2017 at 10:58:51 PM UTC+1, Brandon Donnelson 
> wrote:
>>
>> I'm adding a "share anonymous usage" stats checkbox, so the analytics 
>> capture can be turned off. Any thoughts on verbiage? 
>>
>

-- 
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/f61f7d21-f5ce-4a0c-8e02-2ea9ab7acf68%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: org.eclipse.jetty.apache.jsp.JuliLog not a subtype

[Brandon Donnelson]

Do you think I could exclude something from gwt-dev in the dev mode 
launcher classpath and fix this in Eclipse? 

On Wednesday, February 1, 2017 at 2:14:25 AM UTC-8, Thomas Broyer wrote:
>
> FWIW: https://youtrack.jetbrains.com/issue/IDEA-165234
> Fixed in 2016.3.4 released today.
>
> On Friday, January 27, 2017 at 3:04:43 PM UTC+1, ca...@linxa.com 
>  wrote:
>>
>> Hey I am experiencing the same issue these days and cannot figure it out. 
>> Could you please tell the solution out here? 
>>
>>
>> On Wednesday, January 25, 2017 at 5:52:34 PM UTC+3, Bogdan Petridean 
>> wrote:
>>>
>>> Fixed it!
>>>
>>> On Tuesday, January 24, 2017 at 10:43:09 AM UTC+1, Bogdan Petridean 
>>> wrote:

 I am experiencing the same issue, but I am using Eclipse Neon IDE.
 I cannot figure out which is the problematic dependency

>>>

-- 
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/676d7e60-febd-47f9-ab0e-9a166f772b35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8.0 Eclipse

[Brandon Donnelson]

GPE is deprecated and will no longer continuing support for GWT. The
features have been split between the GWT Eclipse Plugin and Google Cloud
Tools Plugin for Eclipse.

The older versions of GPE still work, but not recommended.

http://gwt-plugins.github.io/documentation/ - GWT Eclipse Plugin

On Thu, Feb 23, 2017 at 4:05 AM Rodolfo Raya  wrote:

> The standard plugin for eclipse neon available at
> https://dl.google.com/eclipse/plugin/4.6 works fine with GWT 2.8
>
> Regards,
> Rodolfo
>
>
> On Fri, Feb 17, 2017 at 1:45 PM  wrote:
>
> Hi, I have noticed that GWT 2.7 is 3 years old. GWT 2.8 final was released
> like half a year ago. How should one develop GWT applications - in which
> IDE? Will there be an update for GWT Eclipse plugin this year?
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" 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 https://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 "GWT Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit/5Bby0Y7K9qw/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 https://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 "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8.0 Eclipse

[Brandon Donnelson]

I plan on adding more patches and enhancements this year to the plugin. 

On Friday, February 17, 2017 at 1:02:33 PM UTC-8, Slava Pankov wrote:
>
> This one works with GWT 2.8 perfectly: 
> http://storage.googleapis.com/gwt-eclipse-plugin/v3/release
>
> Sources are here: https://github.com/gwt-plugins/gwt-eclipse-plugin
>
> On Friday, February 17, 2017 at 8:45:25 AM UTC-8, l.s...@behaimits.com 
> wrote:
>>
>> Hi, I have noticed that GWT 2.7 is 3 years old. GWT 2.8 final was 
>> released like half a year ago. How should one develop GWT applications - in 
>> which IDE? Will there be an update for GWT Eclipse plugin this year?
>>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: WindowBuilder for GWT

[Brandon Donnelson]

Good idea. I'll see if I can do that this week.

On Sun, Jan 8, 2017 at 5:01 PM Alain Ekambi <jazzmatad...@gmail.com> wrote:

> would nt it be better if you could document what you  did and let others
> help
>
> I m interested in contribuating
>
> Am 09.01.2017 01:14 schrieb "Brandon Donnelson" <branflake2...@gmail.com>:
>
> I've got it to work with GWT 2.7 so I think it's possible, I started to
> reverse engineer the wiring. The internal compiler wiring is quite old and
> has to be updated. I did update the wiring and got it to work although I
> haven't pushed it up to the repo yet. There are some plugins being used to
> do screenshots, this wiring I don't know if it needs upgrading yet. That
> said, the amount of energy that would be needed to climb the hill is quite
> time expensive. I've had it on my wish list, although I haven't been able
> to find a carrot to motivate me to get there yet. I'm distracted on a hobby
> project, something to detox from my last go of upgrading the Eclipse
> plugin, but I suspect I'll have another go at the setup this year, just
> don't know when yet.
>
> On Sunday, January 8, 2017 at 2:31:08 AM UTC-8, Thomas Broyer wrote:
>
> It's simple: you can't. GWT Designer is unmaintained and hasn't had a
> release for recent versions of Eclipse.
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "GWT Users" 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 https://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 "GWT Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit/87IJEF8w5EE/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 https://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 "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: WindowBuilder for GWT

[Brandon Donnelson]

I've got it to work with GWT 2.7 so I think it's possible, I started to 
reverse engineer the wiring. The internal compiler wiring is quite old and 
has to be updated. I did update the wiring and got it to work although I 
haven't pushed it up to the repo yet. There are some plugins being used to 
do screenshots, this wiring I don't know if it needs upgrading yet. That 
said, the amount of energy that would be needed to climb the hill is quite 
time expensive. I've had it on my wish list, although I haven't been able 
to find a carrot to motivate me to get there yet. I'm distracted on a hobby 
project, something to detox from my last go of upgrading the Eclipse 
plugin, but I suspect I'll have another go at the setup this year, just 
don't know when yet. 

On Sunday, January 8, 2017 at 2:31:08 AM UTC-8, Thomas Broyer wrote:
>
> It's simple: you can't. GWT Designer is unmaintained and hasn't had a 
> release for recent versions of Eclipse.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: What is the status of J2CL?

[Brandon Donnelson]

No, JSNI will no longer be supported with J2CL, it won't be needed. That 
said, we are waiting on a core library with elemental to be released so 
that JSNI doesn't have to be used anymore, meaning you can work with arrays 
elements. It's a small lib.

Google is working on J2CL, they're close but more work is needed before the 
release. I can't speak to the timeline, but it sounded not to far off. 


On Monday, November 28, 2016 at 7:25:07 AM UTC-8, Kirill Prazdnikov wrote:
>
> It is interesting: does J2CL support JSNI or not. 
> Currently, @JsIndexer annotation does exist, so that it is impossible to 
> work with js-arrays without JSNI. 
> There are possibilities for J2CL: to have @JsIndexer, to support JSNI, 
> both, something else.
>
> Konstantin, have you ever considered using Kotlin-js ?
>
>
>

-- 
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/3fcf2415-cb8d-4edb-814e-3c1d467fe911%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Plugin for Eclipse Mars

[Brandon Donnelson]

http://storage.googleapis.com/gwt-eclipse-plugin/v3/release is the correct
url. It just doesn't have index page.

On Mon, Nov 14, 2016 at 9:03 AM DavidN <david.no...@gmail.com> wrote:

> Hi Brian,
>
> I'm trying to get my hands on the new gwt-eclipse-plugin. But it seems the
> link provided in the download documentation does not work.
> http://storage.googleapis.com/gwt-eclipse-plugin/v3/release
>
> This resolves to a page not found error.
>
> What would be the correct URL ? I don't have access to the Eclipse Market
> Place on my dev machine (corporate firewall). So they need to set up a
> mirror somehow since I can't find an offline update site archive.
>
> David
>
>
> On Tuesday, October 18, 2016 at 5:16:24 PM UTC+2, Brandon Donnelson wrote:
>
> Michael is right, GPE and GPE fork is deprecated.
>
> - GPE is deprecated (or will be in 4th quarter)
> - The new GWT Eclipse Plugin V3 can be installed on mars and neon. The
> install will conflict with GPE or GPE-Fork so it will ask you to remove GPE
> if it is installed.
> - I haven't tested the install GWT Eclipse Plugin V3 with the GPE
> uninstall path very much so I'm interested if that works, and if it doesn't
> please report back :)
>
> http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html
>  - 3 options to dowload, the market place is best
>
> Thanks,
> Brandon
>
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit/1OMqAZ9rOdY/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 https://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 "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Google Plugin for Eclipse Mars

[Brandon Donnelson]

I just ran through the install routine again for Eclipse Neon and GWT 
Eclipse Plugin with SDBG Javascript debugger with out an issue. So I can't 
replicate the issue yet. What operating system are you using? Could you 
screencast the process, maybe I'm missing something?

On Wednesday, November 2, 2016 at 11:35:28 AM UTC-7, Brandon Donnelson 
wrote:
>
> Can you file an issue in the SDBG issues? I think I need to test Neon 1a, 
> I've got 1. Howd you get 1a? 
>
> https://github.com/sdbg/sdbg/issues
>
>
> On Wednesday, November 2, 2016 at 6:08:11 AM UTC-7, Thomas Lacroix wrote:
>>
>> Sorry Brandon, I was out of touch for a few days.
>> I tried to install the GWT Eclipse Plugin V3 on a fresh install of 
>> eclipse Neon.1a Release (4.6.1) (no plugin previously installed) targeting 
>> a new workspace and it shows the same error result:
>> An error occurred during the 
>> org.eclipse.equinox.internal.p2.engine.phases.CheckTrust phase. ...
>> I had GPE installed on my previous eclipse mars but it installed in a 
>> completely different location.
>> Eclipse oomph -> Bundle Pools shows that the artifact 
>> com.github.sdbg.debug.core_1.0.10.201610081555.jar is damaged, but 
>> repairing it doesn't do the trick (same error).
>> I am waiting for security clearance to post on the eclipse forum about 
>> this issue.
>> In the meantime, the GWT Eclipse Plugin V3 without SGBD + browser dev 
>> tool works fine for me.
>> Thomas
>>
>> Le vendredi 28 octobre 2016 17:20:38 UTC+2, Brandon Donnelson a écrit :
>>>
>>> What version of Eclipse, mars or neon? Was there an earlier version 
>>> installed? 
>>>
>>> If GPE was previously installed and you're replacing it with the GWT 
>>> Eclipse Plugin V3 there is a possibility there are some left over bits from 
>>> the previous install causing issues. I added a conflict, although there are 
>>> cases I've seen where the uninstall wasn't perfect. Check your plugins 
>>> list, and be sure any previous plugins that were owned by GPE were removed 
>>> before install. 
>>>
>>> If that doesn't work, I'd suggest installing a clean version of Eclipse 
>>> and installing the plugin. I haven't seen any issues with a clean install, 
>>> at least not yet. You're should be ok to use the same working directory. 
>>>
>>> Would that help? 
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Google Plugin for Eclipse Mars

[Brandon Donnelson]

Can you file an issue in the SDBG issues? I think I need to test Neon 1a, 
I've got 1. Howd you get 1a? 

https://github.com/sdbg/sdbg/issues


On Wednesday, November 2, 2016 at 6:08:11 AM UTC-7, Thomas Lacroix wrote:
>
> Sorry Brandon, I was out of touch for a few days.
> I tried to install the GWT Eclipse Plugin V3 on a fresh install of eclipse 
> Neon.1a Release (4.6.1) (no plugin previously installed) targeting a new 
> workspace and it shows the same error result:
> An error occurred during the 
> org.eclipse.equinox.internal.p2.engine.phases.CheckTrust phase. ...
> I had GPE installed on my previous eclipse mars but it installed in a 
> completely different location.
> Eclipse oomph -> Bundle Pools shows that the artifact 
> com.github.sdbg.debug.core_1.0.10.201610081555.jar is damaged, but 
> repairing it doesn't do the trick (same error).
> I am waiting for security clearance to post on the eclipse forum about 
> this issue.
> In the meantime, the GWT Eclipse Plugin V3 without SGBD + browser dev tool 
> works fine for me.
> Thomas
>
> Le vendredi 28 octobre 2016 17:20:38 UTC+2, Brandon Donnelson a écrit :
>>
>> What version of Eclipse, mars or neon? Was there an earlier version 
>> installed? 
>>
>> If GPE was previously installed and you're replacing it with the GWT 
>> Eclipse Plugin V3 there is a possibility there are some left over bits from 
>> the previous install causing issues. I added a conflict, although there are 
>> cases I've seen where the uninstall wasn't perfect. Check your plugins 
>> list, and be sure any previous plugins that were owned by GPE were removed 
>> before install. 
>>
>> If that doesn't work, I'd suggest installing a clean version of Eclipse 
>> and installing the plugin. I haven't seen any issues with a clean install, 
>> at least not yet. You're should be ok to use the same working directory. 
>>
>> Would that help? 
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Bazel rules now available for GWT

[Brandon Donnelson]

Cool! Nice job!

On Thursday, October 27, 2016 at 2:10:54 PM UTC-7, Erik Kuefler wrote:
>
> In case anyone is looking into using Bazel  as 
> part of a GWT project, there are now some simple GWT rules available in the 
> Bazel repositories at https://github.com/bazelbuild/rules_gwt. These 
> rules have been updated to support GWT 2.8 and define a build target that 
> creates a .war file containing the GWT-compiled artifacts and a run target 
> that executes Super Dev Mode. Please report any problems on the issue 
> tracker .
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Google Plugin for Eclipse Mars

[Brandon Donnelson]

What version of Eclipse, mars or neon? Was there an earlier version 
installed? 

If GPE was previously installed and you're replacing it with the GWT 
Eclipse Plugin V3 there is a possibility there are some left over bits from 
the previous install causing issues. I added a conflict, although there are 
cases I've seen where the uninstall wasn't perfect. Check your plugins 
list, and be sure any previous plugins that were owned by GPE were removed 
before install. 

If that doesn't work, I'd suggest installing a clean version of Eclipse and 
installing the plugin. I haven't seen any issues with a clean install, at 
least not yet. You're should be ok to use the same working directory. 

Would that help? 

On Friday, October 28, 2016 at 2:26:54 AM UTC-7, Thomas Lacroix wrote:
>
>
> Le jeudi 27 octobre 2016 16:42:57 UTC+2, Brandon Donnelson a écrit :
>>
>> I'm not sure why the SDBG plugin failed to install. Those artifacts come 
>> from another repo. I would try again. 
>>
>>  
> It looks like my eclipse has a problem with installing the SGBD plugin, I 
> don't know why yet.
> I have opened a thread on the SGBD group for their input.
> In the meantime, when I install the GWT Eclipse Plugin V3 without SGBD it 
> seems to work fine.
> It says it could not create the view: com.google.gwt.eclipse.DevModeView 
> but I am able to debug in the browser dev tool.
> Thomas 
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Google Plugin for Eclipse Mars

[Brandon Donnelson]

I'm not sure why the SDBG plugin failed to install. Those artifacts come 
from another repo. I would try again. 

On Thursday, October 27, 2016 at 5:06:54 AM UTC-7, Thomas Lacroix wrote:
>
>
> Le mercredi 26 octobre 2016 19:47:13 UTC+2, Brandon Donnelson a écrit :
>>
>> If you're looking for the GWT features, use this plugin instead. It is 
>> has replaced the GPE plugin. 
>>
>> https://marketplace.eclipse.org/content/gwt-eclipse-plugin 
>>
>
>
> Hello,
> I tried installing the GWT Eclipse Plugin V3 on eclipse neon (without GPE 
> previously installed) and got the following error message :
> An error occurred during the 
> org.eclipse.equinox.internal.p2.engine.phases.CheckTrust phase.
> session context 
> was:(profile=C__Users_XXX_Programmes_eclipse_jee-neon_eclipse, 
> phase=org.eclipse.equinox.internal.p2.engine.phases.CheckTrust, operand=, 
> action=).
> Error reading signed content.
> Exception in opening zip file: 
> C:\Users\XXX\.p2\pool\plugins\com.github.sdbg.debug.core_1.0.10.201610081555.jar
> ?
> Thomas 
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Google Plugin for Eclipse Mars

[Brandon Donnelson]

On Thursday, October 27, 2016 at 7:31:24 AM UTC-7, Alain wrote:
>
> To get this straight- We now have 2 plugins for Google stuff ? 
>
- The GWT Eclipse Plugin or GWT Features is no longer the responsibility of 
Google, it has gone open source. They are and have helped with the GWT 
Eclipse Plugin but it's only that now. So any features GWT related are the 
responsibility of the GWT community to maintain and develop. I've taken a 
big bite out of the job already and look forward to helping with it more. 
 

> The GWT plugin and that Cloud Platform Plugin ? 
>
Yes, there are two plugins.  


> On 27 October 2016 at 16:28, Brandon Donnelson <branfl...@gmail.com 
> > wrote:
>
>> The GWT Eclipse Plugin doesn't have the App Engine features, but the new 
>> Official Google Cloud Tools Plugin does. The neat thing about the new Cloud 
>> tools plugin, it supports both App Engine Standard and Flex. You'll want to 
>> wait till it comes out if you're using App Engine, unless you want to run 
>> app engine with another launcher. So unfortunately, there will be a small 
>> gap of time in waiting for the install site for the cloud tools plugin. The 
>> plugin some major effort going behind it currently. 
>>
>> https://github.com/GoogleCloudPlatform/google-cloud-eclipse 
>>
>>
>>
>> On Thursday, October 27, 2016 at 4:23:00 AM UTC-7, Stefano Ciccarelli 
>> wrote:
>>>
>>> Thanks for the info.
>>>
>>> What about the Google App Engine integration?
>>>
>>>
>>> Il giorno mar 18 ott 2016 alle ore 17:16 Brandon Donnelson <
>>> branfl...@gmail.com> ha scritto:
>>>
>>>> Michael is right, GPE and GPE fork is deprecated. 
>>>>
>>>> - GPE is deprecated (or will be in 4th quarter)
>>>> - The new GWT Eclipse Plugin V3 can be installed on mars and neon. The 
>>>> install will conflict with GPE or GPE-Fork so it will ask you to remove 
>>>> GPE 
>>>> if it is installed. 
>>>> - I haven't tested the install GWT Eclipse Plugin V3 with the GPE 
>>>> uninstall path very much so I'm interested if that works, and if it 
>>>> doesn't 
>>>> please report back :)
>>>>
>>>>
>>>> http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html
>>>>  
>>>>  - 3 options to dowload, the market place is best 
>>>>
>>>> Thanks,
>>>> Brandon
>>>>
>>>>  
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "GWT Users" 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-we...@googlegroups.com.
>>>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> -- 
>>> *Stefano Ciccarelli* 
>>> GAE Application Division 
>>> / Director 
>>> stefano.c...@mmbsoftware.it 
>>>
>>> *M.M.B. s.r.l.* 
>>> via Granarolo, 177/7 - 48018 Faenza (RA) - Italy 
>>> tel. +39.0546.637711 - fax +39.0546.46077 
>>> www.mmbsoftware.it - in...@mmbsoftware.it
>>>
>>> Le informazioni contenute in questa comunicazione sono riservate e 
>>> destinate esclusivamente alla/e persona/e o all'ente sopra indicati. E' 
>>> vietato ai soggetti diversi dai destinatari qualsiasi uso, copia, 
>>> diffusione di quanto in esso contenuto sia ai sensi dell'art. 616 c.p., sia 
>>> ai sensi del DL n. 196/03. Se questa comunicazione Vi e' pervenuta per 
>>> errore, Vi preghiamo di rispondere a questa e-mail e successivamente 
>>> cancellarla dal Vostro sistema.
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "GWT Users" 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-we...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
>
> Alain Ekambi
>
> Co-Founder
>
> Ahomé Innovation Technologies
>
> http://www.ahome-it.com/ <http://ahome-it.com/>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Google Plugin for Eclipse Mars

[Brandon Donnelson]

If you're looking for the GWT features, use this plugin instead. It is has
replaced the GPE plugin.

https://marketplace.eclipse.org/content/gwt-eclipse-plugin

On Wed, Oct 26, 2016 at 10:45 AM Brandon Donnelson <branflake2...@gmail.com>
wrote:

> The Google Plugin for Eclipse is still available. The new Cloud Tools
> Plugin for Eclipse will be out soon.
>
> https://developers.google.com/eclipse/docs/download
>
> On Wed, Oct 26, 2016 at 8:08 AM Piotr Morgwai Kotarbinski <
> morg...@gmail.com> wrote:
>
> This plugin, although soon to be deprecated, worked ok for many ppl. Now
> they are suddenly forced to migrate without any warning... Does anybody has
> a cash of last available version for eclipse 4.5 (mars) maybe?
>
> Thanks!
>
>
> On Wednesday, October 19, 2016 at 12:01:29 AM UTC+7, Brandon Donnelson
> wrote:
>
> Google will officially deprecate GPE soon, in the 4th quarter. Obviously I
> can't speak officially for them, but take my word it's coming. So I'm
> warning it's coming, and presenting the deprecation earlier, as I've been
> separated the GWT features from the cloud tools. The
> https://github.com/GoogleCloudPlatform/google-cloud-eclipse will be
> replacing GPE in November as the official plugin. This plugin is far better
> than GPE, although it's not polished to beta yet.
>
> The documentation switch is on the agenda to update still.
>
> On Tue, Oct 18, 2016 at 9:23 AM Jim Douglas <jdo...@basis.com> wrote:
>
> Is there an announcement of the deprecation anywhere, Brandon?  Those URLs
> all look like works in progress.
>
> When a random developer goes looking for the Google Plugin for Eclipse, he
> finds this:
>
> https://developers.google.com/eclipse/
>
> Which leads to these install instructions:
>
> https://developers.google.com/eclipse/docs/getting_started
>
> Which leads to these instructions:
>
> Plugin for Eclipse 4.6 (Neon)
> <https://developers.google.com/eclipse/docs/install-eclipse-4.6>
>
> Plugin for Eclipse 4.5 (Mars)
> <https://developers.google.com/eclipse/docs/install-eclipse-4.5>
>
> Plugin for Eclipse 4.4 (Luna)
> <https://developers.google.com/eclipse/docs/install-eclipse-4.4>
>
>
> On Tuesday, October 18, 2016 at 8:16:24 AM UTC-7, Brandon Donnelson wrote:
>
> Michael is right, GPE and GPE fork is deprecated.
>
> - GPE is deprecated (or will be in 4th quarter)
> - The new GWT Eclipse Plugin V3 can be installed on mars and neon. The
> install will conflict with GPE or GPE-Fork so it will ask you to remove GPE
> if it is installed.
> - I haven't tested the install GWT Eclipse Plugin V3 with the GPE
> uninstall path very much so I'm interested if that works, and if it doesn't
> please report back :)
>
> http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html
>  - 3 options to dowload, the market place is best
>
> Thanks,
> Brandon
>
>
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit/1OMqAZ9rOdY/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 https://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 "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Google Plugin for Eclipse Mars

[Brandon Donnelson]

The Google Plugin for Eclipse is still available. The new Cloud Tools
Plugin for Eclipse will be out soon.

https://developers.google.com/eclipse/docs/download

On Wed, Oct 26, 2016 at 8:08 AM Piotr Morgwai Kotarbinski <morg...@gmail.com>
wrote:

> This plugin, although soon to be deprecated, worked ok for many ppl. Now
> they are suddenly forced to migrate without any warning... Does anybody has
> a cash of last available version for eclipse 4.5 (mars) maybe?
>
> Thanks!
>
>
> On Wednesday, October 19, 2016 at 12:01:29 AM UTC+7, Brandon Donnelson
> wrote:
>
> Google will officially deprecate GPE soon, in the 4th quarter. Obviously I
> can't speak officially for them, but take my word it's coming. So I'm
> warning it's coming, and presenting the deprecation earlier, as I've been
> separated the GWT features from the cloud tools. The
> https://github.com/GoogleCloudPlatform/google-cloud-eclipse will be
> replacing GPE in November as the official plugin. This plugin is far better
> than GPE, although it's not polished to beta yet.
>
> The documentation switch is on the agenda to update still.
>
> On Tue, Oct 18, 2016 at 9:23 AM Jim Douglas <jdo...@basis.com> wrote:
>
> Is there an announcement of the deprecation anywhere, Brandon?  Those URLs
> all look like works in progress.
>
> When a random developer goes looking for the Google Plugin for Eclipse, he
> finds this:
>
> https://developers.google.com/eclipse/
>
> Which leads to these install instructions:
>
> https://developers.google.com/eclipse/docs/getting_started
>
> Which leads to these instructions:
>
> Plugin for Eclipse 4.6 (Neon)
> <https://developers.google.com/eclipse/docs/install-eclipse-4.6>
>
> Plugin for Eclipse 4.5 (Mars)
> <https://developers.google.com/eclipse/docs/install-eclipse-4.5>
>
> Plugin for Eclipse 4.4 (Luna)
> <https://developers.google.com/eclipse/docs/install-eclipse-4.4>
>
>
> On Tuesday, October 18, 2016 at 8:16:24 AM UTC-7, Brandon Donnelson wrote:
>
> Michael is right, GPE and GPE fork is deprecated.
>
> - GPE is deprecated (or will be in 4th quarter)
> - The new GWT Eclipse Plugin V3 can be installed on mars and neon. The
> install will conflict with GPE or GPE-Fork so it will ask you to remove GPE
> if it is installed.
> - I haven't tested the install GWT Eclipse Plugin V3 with the GPE
> uninstall path very much so I'm interested if that works, and if it doesn't
> please report back :)
>
> http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html
>  - 3 options to dowload, the market place is best
>
> Thanks,
> Brandon
>
>
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit/1OMqAZ9rOdY/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 https://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 "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Eclipse Plugin and Update Maven Project

[Brandon Donnelson]

Could you file a bug with a maven project I could replicate the issue with? 

The maven configurator should provide the war source, target directory and 
the GWT nature to Eclipse. If it isn't doing it, I'd like to know why and 
to do that I need to run the project and check to see if there is something 
a muck. 

https://github.com/gwt-plugins/gwt-eclipse-plugin

Thanks,
Brandon

On Sunday, October 23, 2016 at 6:23:06 AM UTC-7, Gražvydas Valeika wrote:
>
>  Hi,
>
> I observe one problem of  GWT Eclipse Plugin(3.0.0.201610212207) when 
> using it with maven project.
>
> Debugging works very well.  
>
> But:
>
> - my project contains WAR directory, and GWT project setting "This project 
> has WAR directory" (src/main/webapp) is checked.
>
> - GWT debug configuration arguments contain -war ./src/main/webapp.
>
> - when I check GWT project setting "Launch and deploy from this directory 
> (disabled because this is a Maven project)" - everything works perfectly.
>
>
> Problem occurs when I Update Maven Project (Alt+F5).
>
> Then GWT project setting "Launch and deploy from this directory (disabled 
> because this is a Maven project)" is unchecked and more unpleasant - when 
> launching debugger something cleans this directory - removes web.xml, 
> static resources etc.
>
> What is proper way to mitigate this?
>
>
> Thanks, 
>
>
> Gražvydas
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: PROPOSAL: a devserver to replace devmode

[Brandon Donnelson]

Nevermind you answered my question above. 

-- 
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/afca68ae-f8d5-4636-b8db-156668250792%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: PROPOSAL: a devserver to replace devmode

[Brandon Donnelson]

I find most of our customer base uses GWT RPC. The story on using this may 
make using gwt feel complicated. 

If we can just compile into the web app directory for the entire process, 
then there would be no need for a proxy. From what I could tell it would be 
3 args, -war, -browser (or maybe some user agent) and module. I'll see if I 
can prototype the service this week and provide it for chewing on. Do you 
think this is even possible? 

-Brandon


On Monday, October 24, 2016 at 7:40:48 AM UTC-7, Daniel Kurka wrote:
>
> I am seeing a lot of arguments pop up about GWT RPC, but I think it should 
> not be considered for this discussion at all. In my mind GWT 2.8 will be 
> the last release that has GWT RPC and people should start migrating. I 
> think its perfectly fine do design a replacement to devmode without GWT RPC 
> support.
>
> On Mon, Oct 24, 2016 at 4:18 PM Jens  
> wrote:
>
>> Well it is just what I would ask for in order to replace local apache / 
>> nginx on developer machines with GWT devserver. It's not a problem to 
>> simply continue using a dedicated proxy either with CodeServer or a "no-op" 
>> devserver. 
>>
>> Basically our setup is more a less the result of two decisions: Not 
>> serving static content from servlet containers (instead it's severed by 
>> load balancer/proxy) and using GWT-RPC. We need to be in control of which 
>> app version a customer gets served, even before logging in, and that 
>> backend requests will be redirected to a matching server app version 
>> (because of GWT-RPC policy files and rolling updates). Thats why our 
>> production mapping is https://app.example.com// => 
>> /_/ for backend requests and the load 
>> balancer does the mapping using URL rewriting.
>>
>> During development we just have a single app so the rewriting is a lot 
>> simpler but it still exists. Given that our server code sets cookies for 
>> the production domain only (I guess some paranoid security decision), the 
>> cookie domain needs to be rewritten during development to a local ip / 
>> localhost.
>>
>> Given that static content is served by the load balancer / proxy itself, 
>> all caching headers (*.nocache.*, *.cache.*) are configured outside the 
>> servlet container. For consistency cache headers for dynamic host page are 
>> also configured outside the servlet container. So we don't have any 
>> ServletFilter doing it.
>>
>>
>>
>> Hey, this is a currently just a prototype coded over the week-end ;-)
>>> I'd personally prefer not writing anything to the webapp, but as 
>>> acknowledged in the OP we could have a -launcherDir option for 
>>> serialization policies and possibly public resources
>>>
>> (but then why not just use CodeServer with -launcherDir directly? one 
>>> difference could be that devserver would never overwrite a file for 
>>> example…)
>>>
>>
>> Well I could also ask: Why not just having a single solution that simply 
>> works? Personally I don't like having different "entry points" for 
>> development. IMHO its more straight forward (especially for beginners) to 
>> just have CodeServer or just have devserver, but not both (even with 
>> different behavior for stub.nocache.js !). 
>>
>> Adding gwt.codeserver.host and renaming -launcherDir to 
>> -publicResourcesDir would be fine I guess.
>>  
>>
>>
>> Next there are people embedding the module.nocache.js file directly into 
 their host page (like me ;-) basically our host page is a servlet) and 
 that 
 should work also during development.

>>>
>>> I can't think of any other way to make it work (I did that too in one 
>>> app) than having a way to switch from inlined *.nocache.js to external 
>>> *.nocache.js on your server. There's absolutely no risk shipping that in 
>>> production (it's only a network optimisation to avoid one HTTP request) so 
>>> it looks like an acceptable compromise to me.
>>>
>>
>> Well devserver could special case host page loading ("/" or a 
>> configurable host page url) and inspect the result of the backend server to 
>> decide wether or not some inline *.nocache.js file needs to be replaced. To 
>> keep it simply I would require special enclosing start / end comments in 
>> the dynamic host page to make it compatible with devserver. Then the 
>> content in between these comments will be replaced with the stub.nocache.js.
>>
>>
>>  
>>
>>> …or you could just continue using CodeServer with -launcherDir.
>>>
>>
>> Single solution preferred ;-)
>>
>> -- 
>> 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/361aafb5-d40d-433c-a6ba-6209069e5550%40googlegroups.com
>>  
>> 

[gwt-contrib] Re: PROPOSAL: a devserver to replace devmode

[Brandon Donnelson]

I like the sounds on this, although my initial thoughts feel like it's 
another layer. But I also know typically it takes me a bit longer to warm 
up to new approaches. I have trying to think how I can cut the code server 
out of the loop. 

So I've been wondering if I could start the gwt super dev mode compile, 
provide the user agent in the args, so the code server isn't needed. Then 
compile the initial compile into the web app directory. Skip the working 
directory, skip a temp directory, do it into the web app. There would be no 
need for injection, b/c it'd be acting like the real web app, minus the 
optimizations and multi permutation builds. So in that same process, listen 
for changes to the app, and then recompile after the change, or based on a 
trigger, like a change in file.

Here's how Eclipse web tools platform could take advantage of that. Compile 
into a web app directory, when ever contents are added or changed in that 
directory it refreshes the server and if you refresh the web page, the 
contents get loaded. 

Do you think we could get rid of the any additional web server (code 
server) and push the bits into the web app directory, or some directory we 
could push to the web app server? The arguments needed for the compiler 
could be provided in the program args, and changes could trigger the 
recompile. 

-- 
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/3b792d01-9fdc-46fb-9ec2-b43fa57861b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cannot Debug GWT with Eclipse

[Brandon Donnelson]

There are only two arguments needed to run GWT Development Mode (a.k.a
Super Dev Mode.) If you're using the new GWT Eclipse Plugin V3, use the GWT
Development Mode to start up the Super Dev Mode CodeServer. The arguments
will be -launcherDir path/to/WAS/webapp/dir and gwt module.  Then, you'll
notice a directory show up in your web app directory. Then go to the web
page and it should start to compile.

The exact same configuration as the tomcat can be done in this video.
https://www.youtube.com/watch?v=-_YcBeI_Feo=PLBbgqtDgdc_TqzA-qXrjgTFMC_6DKAQyT=5_channel=BrandonDonnelson


On Thu, Oct 20, 2016 at 5:26 PM Namline <blahblo...@gmail.com> wrote:

> My setting is straightforward although I have to say this is simply for me
> to start learning about debugging GWT, and more so, doing it on an external
> server (so I don't have much restrictions). I am running WebSphere
> Application Server (8.5.5) and have my GWT application deployed (war) which
> I can access/view.
>
> The WAS runs on localhost IP with 9080 port. What arguments do I have to
> pass to be able to hook the debugging session to my web application
> deployed on the application server?
>
>
>
> On Thursday, October 20, 2016 at 12:41:41 AM UTC-4, Brandon Donnelson
> wrote:
>
> Sure you can debug on any server, that said, if the web server is on a
> different ip than the code server there's an issue to workaround, b/c the
> project.nocache.js has hostname issue. I'm not sure if this is the case for
> you yet, but usually when you want to debug on a different server they have
> a different ip.
>
> Before I go into this, I'd like to know if the web server ip is the same
> as the code server ip? Let's say you get the project.nocache.js, by
> pointing the launcherDir at war output path, or by using a publishing
> routine, then you load the page, it should compile. Except the nocache.js
> script uses $window.location.hostname to get the code server address.
> Instead you can hand change the ip before pushing it the server, which is
> laborious, or use a class clobber, by using this on the classpath
> https://github.com/gwt-plugins/codeserver/blob/master/codeserver/src/main/java/com/google/gwt/dev/codeserver/LauncherDir.java#L127.
> Or maybe I get my patch accepted to make it possible to easily debug on a
> external server with a different ip than the code server.
>
> https://github.com/gwtproject/gwt/issues/9446 - patch proposal for easily
> debugging on a server with different ip.
>
> Describe your networking config for you servers and I can help more.
>
> -Brandon
>
> On Wednesday, October 19, 2016 at 6:17:54 PM UTC-7, Namline wrote:
>
> Is there a way to debug the GWT application (client and server) just like
> your plugin allows while running in SuperDevMod while it has been deployed
> on an application server, e.g. WebSphere with say, localhost:9080/MyApp
> context root?
>
>
> On Tuesday, October 18, 2016 at 11:51:22 PM UTC-4, Brandon Donnelson wrote:
>
> Thanks for the update. Sounds like some of the name space had to be reset
> in the configuration. I've seen this happen until the project is refreshed
> or reimported.
>
> On Tue, Oct 18, 2016 at 7:00 PM Namline <blahb...@gmail.com> wrote:
>
> Brandon,
>
> Sorry for the delay in response (happy hours). So, here's what happened (I
> am running Eclipse Mars 4.5.2 (R2) with Google Plugin for Eclipse already
> installed (Windows 7)):
>
> I installed GWT Eclipse Plugin 3.0.0 from Eclipse market place, and as
> you had suggested, on the second page, I chose the second radio to
> uninstall Google Plugin for Eclipse. Moreover I had GWT 2.8 unchecked (I
> won't be using it).
> I did not run into any issue with the installation itself, however, when I
> attempted to run, debug, or compile my existing "HelloWorld" GWT
> application, it wasn't even recognizing it as a GWT project!
> First, I had to reset the GWT library in the build config as it somehow
> had messed it up.
> Second, I went to my existing GWT project's Properties -> Project Facets
> and select GWT option as it somehow had been removed.
>
> Afterward, I was able to run and debug as normal.
>
>
> On Monday, October 17, 2016 at 11:28:02 PM UTC-4, Brandon Donnelson wrote:
>
> Good question. The goal is to uninstall GPE or GPE-Fork. I put in a
> conflict so it will ask you to uninstall it. I recommend using Java EE Neon
> and starting with a clean install. I haven't tested enough of the
> uninstalling. In theory it should work fine. I did find some hiccups along
> the way, but I hadn't finished fixing bugs either, and did that along the
> way. If you're game, I'd be interested in hearing if you can just install
> the new plugin with GWT Eclipse Version 3, and have

Re: Cannot Debug GWT with Eclipse

[Brandon Donnelson]

Sure you can debug on any server, that said, if the web server is on a 
different ip than the code server there's an issue to workaround, b/c the 
project.nocache.js has hostname issue. I'm not sure if this is the case for 
you yet, but usually when you want to debug on a different server they have 
a different ip. 

Before I go into this, I'd like to know if the web server ip is the same as 
the code server ip? Let's say you get the project.nocache.js, by pointing 
the launcherDir at war output path, or by using a publishing routine, then 
you load the page, it should compile. Except the nocache.js script uses 
$window.location.hostname to get the code server address. Instead you can 
hand change the ip before pushing it the server, which is laborious, or use 
a class clobber, by using this on the 
classpath 
https://github.com/gwt-plugins/codeserver/blob/master/codeserver/src/main/java/com/google/gwt/dev/codeserver/LauncherDir.java#L127.
 
Or maybe I get my patch accepted to make it possible to easily debug on a 
external server with a different ip than the code server. 

https://github.com/gwtproject/gwt/issues/9446 - patch proposal for easily 
debugging on a server with different ip. 

Describe your networking config for you servers and I can help more. 

-Brandon

On Wednesday, October 19, 2016 at 6:17:54 PM UTC-7, Namline wrote:
>
> Is there a way to debug the GWT application (client and server) just like 
> your plugin allows while running in SuperDevMod while it has been deployed 
> on an application server, e.g. WebSphere with say, localhost:9080/MyApp 
> context root?
>
>
> On Tuesday, October 18, 2016 at 11:51:22 PM UTC-4, Brandon Donnelson wrote:
>>
>> Thanks for the update. Sounds like some of the name space had to be reset 
>> in the configuration. I've seen this happen until the project is refreshed 
>> or reimported. 
>>
>> On Tue, Oct 18, 2016 at 7:00 PM Namline <blahb...@gmail.com> wrote:
>>
>>> Brandon,
>>>
>>> Sorry for the delay in response (happy hours). So, here's what happened 
>>> (I am running Eclipse Mars 4.5.2 (R2) with Google Plugin for Eclipse 
>>> already installed (Windows 7)):
>>>
>>> I installed GWT Eclipse Plugin 3.0.0 from Eclipse market place, and as 
>>> you had suggested, on the second page, I chose the second radio to 
>>> uninstall Google Plugin for Eclipse. Moreover I had GWT 2.8 unchecked (I 
>>> won't be using it).
>>> I did not run into any issue with the installation itself, however, when 
>>> I attempted to run, debug, or compile my existing "HelloWorld" GWT 
>>> application, it wasn't even recognizing it as a GWT project!
>>> First, I had to reset the GWT library in the build config as it somehow 
>>> had messed it up.
>>> Second, I went to my existing GWT project's Properties -> Project Facets 
>>> and select GWT option as it somehow had been removed.
>>>
>>> Afterward, I was able to run and debug as normal.
>>>
>>>
>>> On Monday, October 17, 2016 at 11:28:02 PM UTC-4, Brandon Donnelson 
>>> wrote:
>>>
>>>> Good question. The goal is to uninstall GPE or GPE-Fork. I put in a 
>>>> conflict so it will ask you to uninstall it. I recommend using Java EE 
>>>> Neon 
>>>> and starting with a clean install. I haven't tested enough of the 
>>>> uninstalling. In theory it should work fine. I did find some hiccups along 
>>>> the way, but I hadn't finished fixing bugs either, and did that along the 
>>>> way. If you're game, I'd be interested in hearing if you can just install 
>>>> the new plugin with GWT Eclipse Version 3, and have the GPE uninstalled 
>>>> along the way. When it asks you to instal the plugin, be sure to check the 
>>>> second radio, uninstalling GPE. You'll see what I mean if you go that 
>>>> route. 
>>>>
>>>> Hope that helps,
>>>> Brandon
>>>>
>>>> On Mon, Oct 17, 2016 at 7:58 PM Namline <blahb...@gmail.com> wrote:
>>>>
>>> Brandon,
>>>>>
>>>>> Thanks. I just watched your video on YouTube. Excellent job for 
>>>>> newbies like me.
>>>>>
>>>>> Quick question. As a starter, I have Google Plugin for Eclipse 
>>>>> installed. Do I have to uninstall it before installing GWT Eclipse Plugin 
>>>>> V3?
>>>>>
>>>>>
>>>>>
>>>>> On Monday, October 17, 2016 at 1:40:43 PM UTC-4, Brandon Donnelson 
>>>>> wrote:
>>>>>>
>>>>>>

Re: Cannot Debug GWT with Eclipse

[Brandon Donnelson]

Thanks for the update. Sounds like some of the name space had to be reset
in the configuration. I've seen this happen until the project is refreshed
or reimported.

On Tue, Oct 18, 2016 at 7:00 PM Namline <blahblo...@gmail.com> wrote:

> Brandon,
>
> Sorry for the delay in response (happy hours). So, here's what happened (I
> am running Eclipse Mars 4.5.2 (R2) with Google Plugin for Eclipse already
> installed (Windows 7)):
>
> I installed GWT Eclipse Plugin 3.0.0 from Eclipse market place, and as
> you had suggested, on the second page, I chose the second radio to
> uninstall Google Plugin for Eclipse. Moreover I had GWT 2.8 unchecked (I
> won't be using it).
> I did not run into any issue with the installation itself, however, when I
> attempted to run, debug, or compile my existing "HelloWorld" GWT
> application, it wasn't even recognizing it as a GWT project!
> First, I had to reset the GWT library in the build config as it somehow
> had messed it up.
> Second, I went to my existing GWT project's Properties -> Project Facets
> and select GWT option as it somehow had been removed.
>
> Afterward, I was able to run and debug as normal.
>
>
> On Monday, October 17, 2016 at 11:28:02 PM UTC-4, Brandon Donnelson wrote:
>
> Good question. The goal is to uninstall GPE or GPE-Fork. I put in a
> conflict so it will ask you to uninstall it. I recommend using Java EE Neon
> and starting with a clean install. I haven't tested enough of the
> uninstalling. In theory it should work fine. I did find some hiccups along
> the way, but I hadn't finished fixing bugs either, and did that along the
> way. If you're game, I'd be interested in hearing if you can just install
> the new plugin with GWT Eclipse Version 3, and have the GPE uninstalled
> along the way. When it asks you to instal the plugin, be sure to check the
> second radio, uninstalling GPE. You'll see what I mean if you go that
> route.
>
> Hope that helps,
> Brandon
>
> On Mon, Oct 17, 2016 at 7:58 PM Namline <blahb...@gmail.com> wrote:
>
> Brandon,
>
> Thanks. I just watched your video on YouTube. Excellent job for newbies
> like me.
>
> Quick question. As a starter, I have Google Plugin for Eclipse installed.
> Do I have to uninstall it before installing GWT Eclipse Plugin V3?
>
>
>
> On Monday, October 17, 2016 at 1:40:43 PM UTC-4, Brandon Donnelson wrote:
>
> SDBG is the way to go for debugging, like they said.
>
> Keep in mind if the Chrome dev tools are open it will take over the
> breakpoints, and they are stated in Chrome dev tools. If Chrome dev tools
> are closed, and you opened debugging the browser with the SDBG Javascript
> debugger shortcut, then Eclipse is in charge of the break points, console
> output and trace inspection.
>
> I'll create a video and guide here shortly. And talk about it at GWT Con.
> https://github.com/gwt-plugins/gwt-eclipse-plugin/projects/2
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit/TOVusERKYhU/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-we...@googlegroups.com.
>
>
> Visit this group at https://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 "GWT Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit/TOVusERKYhU/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 https://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 "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Proposed LauncherDir change, add template bindAddress replacement

[Brandon Donnelson]

I filed a github for it. 

https://github.com/gwtproject/gwt/issues/9446

-- 
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/d1fa1662-9f0d-4aa8-a26a-f940cedd6175%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Plugin for Eclipse Mars

[Brandon Donnelson]

Google will officially deprecate GPE soon, in the 4th quarter. Obviously I
can't speak officially for them, but take my word it's coming. So I'm
warning it's coming, and presenting the deprecation earlier, as I've been
separated the GWT features from the cloud tools. The
https://github.com/GoogleCloudPlatform/google-cloud-eclipse will be
replacing GPE in November as the official plugin. This plugin is far better
than GPE, although it's not polished to beta yet.

The documentation switch is on the agenda to update still.

On Tue, Oct 18, 2016 at 9:23 AM Jim Douglas <jdou...@basis.com> wrote:

> Is there an announcement of the deprecation anywhere, Brandon?  Those URLs
> all look like works in progress.
>
> When a random developer goes looking for the Google Plugin for Eclipse, he
> finds this:
>
> https://developers.google.com/eclipse/
>
> Which leads to these install instructions:
>
> https://developers.google.com/eclipse/docs/getting_started
>
> Which leads to these instructions:
>
> Plugin for Eclipse 4.6 (Neon)
> <https://developers.google.com/eclipse/docs/install-eclipse-4.6>
>
> Plugin for Eclipse 4.5 (Mars)
> <https://developers.google.com/eclipse/docs/install-eclipse-4.5>
>
> Plugin for Eclipse 4.4 (Luna)
> <https://developers.google.com/eclipse/docs/install-eclipse-4.4>
>
>
> On Tuesday, October 18, 2016 at 8:16:24 AM UTC-7, Brandon Donnelson wrote:
>
> Michael is right, GPE and GPE fork is deprecated.
>
> - GPE is deprecated (or will be in 4th quarter)
> - The new GWT Eclipse Plugin V3 can be installed on mars and neon. The
> install will conflict with GPE or GPE-Fork so it will ask you to remove GPE
> if it is installed.
> - I haven't tested the install GWT Eclipse Plugin V3 with the GPE
> uninstall path very much so I'm interested if that works, and if it doesn't
> please report back :)
>
> http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html
>  - 3 options to dowload, the market place is best
>
> Thanks,
> Brandon
>
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit/1OMqAZ9rOdY/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 https://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 "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Google Plugin for Eclipse Mars

[Brandon Donnelson]

Michael is right, GPE and GPE fork is deprecated. 

- GPE is deprecated (or will be in 4th quarter)
- The new GWT Eclipse Plugin V3 can be installed on mars and neon. The 
install will conflict with GPE or GPE-Fork so it will ask you to remove GPE 
if it is installed. 
- I haven't tested the install GWT Eclipse Plugin V3 with the GPE uninstall 
path very much so I'm interested if that works, and if it doesn't please 
report back :)

http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html 
 - 3 options to dowload, the market place is best 

Thanks,
Brandon

 

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Cannot Debug GWT with Eclipse

[Brandon Donnelson]

Good question. The goal is to uninstall GPE or GPE-Fork. I put in a
conflict so it will ask you to uninstall it. I recommend using Java EE Neon
and starting with a clean install. I haven't tested enough of the
uninstalling. In theory it should work fine. I did find some hiccups along
the way, but I hadn't finished fixing bugs either, and did that along the
way. If you're game, I'd be interested in hearing if you can just install
the new plugin with GWT Eclipse Version 3, and have the GPE uninstalled
along the way. When it asks you to instal the plugin, be sure to check the
second radio, uninstalling GPE. You'll see what I mean if you go that
route.

Hope that helps,
Brandon

On Mon, Oct 17, 2016 at 7:58 PM Namline <blahblo...@gmail.com> wrote:

> Brandon,
>
> Thanks. I just watched your video on YouTube. Excellent job for newbies
> like me.
>
> Quick question. As a starter, I have Google Plugin for Eclipse installed.
> Do I have to uninstall it before installing GWT Eclipse Plugin V3?
>
>
>
> On Monday, October 17, 2016 at 1:40:43 PM UTC-4, Brandon Donnelson wrote:
>
> SDBG is the way to go for debugging, like they said.
>
> Keep in mind if the Chrome dev tools are open it will take over the
> breakpoints, and they are stated in Chrome dev tools. If Chrome dev tools
> are closed, and you opened debugging the browser with the SDBG Javascript
> debugger shortcut, then Eclipse is in charge of the break points, console
> output and trace inspection.
>
> I'll create a video and guide here shortly. And talk about it at GWT Con.
> https://github.com/gwt-plugins/gwt-eclipse-plugin/projects/2
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit/TOVusERKYhU/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 https://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 "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Cannot Debug GWT with Eclipse

[Brandon Donnelson]

SDBG is the way to go for debugging, like they said. 

Keep in mind if the Chrome dev tools are open it will take over the 
breakpoints, and they are stated in Chrome dev tools. If Chrome dev tools 
are closed, and you opened debugging the browser with the SDBG Javascript 
debugger shortcut, then Eclipse is in charge of the break points, console 
output and trace inspection. 

I'll create a video and guide here shortly. And talk about it at GWT 
Con. https://github.com/gwt-plugins/gwt-eclipse-plugin/projects/2

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Proposed LauncherDir change, add template bindAddress replacement

[Brandon Donnelson]

ping

-- 
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/2177a1c9-ec27-4cbc-8ef9-3fa2c722fbd2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Clean up PRs on gwt-site

[Brandon Donnelson]

What do you think of merging the PRs on the gwt-site? 

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/5a82274e-b957-4d92-8b2f-6f7341ee12a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Proposed LauncherDir change, add template bindAddress replacement

[Brandon Donnelson]

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

-- 
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/0b5bbedc-f18f-4a9e-8057-01a53ae3e0c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Proposed LauncherDir change, add template bindAddress replacement

[Brandon Donnelson]

GWT Eclipse Plugin (V3) 
Issue: https://github.com/gwt-plugins/gwt-eclipse-plugin/issues/274

-- 
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/17884aee-81df-4045-905d-e8177847e50d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Proposed LauncherDir change, add template bindAddress replacement

[Brandon Donnelson]

What would you think of adding a bindAddress replacement to the 
template.nocache.js file. __bindAddress__ instead of 
$window.location.hostname?


Example Source - Used for testing Hack
https://github.com/gwt-plugins/codeserver/blob/master/codeserver/src/main/java/com/google/gwt/dev/codeserver/LauncherDir.java#L127

Reason
Running code server on a local private ip and deploying the web app on a 
different ip, this simplifies the setup. 

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/ec540ba9-4350-4f9c-b894-76abed57b81d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Where did org.eclipse.jetty.util.ajax.JSON.toString(map); go?

[Brandon Donnelson]

 

Hi Team,


gwt-dev.jar: org.eclipse.jetty.util.ajax.JSON.toString(map);  was in GWT 
2.7, but with the Jetty upgrade I think it was pulled. Do you know what I 
could use in replacement? 


Eclipse uses it in the wiring and I want to upgrade to 2.8. 


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/b929f9c3-9ccd-46dd-b44b-496427e3405f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT Eclipse Plugin (V3) Shortcuts/Launchers

[Brandon Donnelson]

I've started and revised the Getting started story to reflect what's going 
in GWT Eclipse Plugin (V3). 
http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/GettingStarted.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/b6eb9858-d9f4-45bd-b5dd-049957a46bc2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT Eclipse Plugin (V3) Shortcuts/Launchers

[Brandon Donnelson]

I do like the specificity to that, in showing the difference. Although I'm
sort of thinking the simplification to GWT Development Mode helps. Although
now that I've thought about what Thomas has said, I like describing
development as `Development Mode` without any special emphasis on super or
not. Since Super is the default these days. Another note, whenever I'm on
site with large GWT engineering teams, describing super or not didn't
really help my story. Rather providing the specificity of what goes on
muddys the development story. I feel like there are too many roads
sometimes to get gethings launched.

On Fri, Oct 7, 2016 at 9:29 AM Ignacio Baca Moreno-Torres <
igna...@bacamt.com> wrote:

> Something like this will be pretty self-explanatory:
> Super Development Mode (debug in JavaScript, using SDBG or browser tools)
> Legacy Development Mode (debug in Java, requires deprecated browser plugin)
>
> Even better, each parenthesis has the next link respectively:
> http://www.gwtproject.org/articles/superdevmode.html
>
> http://www.gwtproject.org/doc/latest/DevGuideCompilingAndDebugging.html#dev_mode
>
>
> But as my other comment, this might be too verbose, right now is more
> compact and perfect for people that already know the difference between
> legacy and super.
>
> On Fri, Oct 7, 2016 at 5:11 PM Brandon Donnelson <branflake2...@gmail.com>
> wrote:
>
> If anybody has problems with the labels above please speak up. Otherwise
> EA is coming soon with what's above. I'll be starting to write docs with
> screenshots shortly.
>
> Any thoughts on changing the GWT Settings labels?
>
> --
> 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/037efdcb-4b33-455e-a36e-19001de03979%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/037efdcb-4b33-455e-a36e-19001de03979%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/CABVWDC7WDvKC-aZOMV_PHEqKg0dMUPO_gvm-Hz3rOwLzKuMfvw%40mail.gmail.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABVWDC7WDvKC-aZOMV_PHEqKg0dMUPO_gvm-Hz3rOwLzKuMfvw%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
*Brandon Donnelson*
GXT Support Engineer
<http://www.facebook.com/senchainc> <http://twitter.com/sencha>
<https://www.linkedin.com/company/sencha-inc>
<http://www.youtube.com/SenchaInc>
<https://plus.google.com/117303203295549187007?prsrc=3>
[image: SenchaCon 2016 Aria Resort, Las Vegas, November 7-9]
<https://www.senchacon.com/>
*Join me at SenchaCon 2016!*

-- 
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/CAA_mbNO38nnhHksDES1ZrFegZC%3DX3OKdwmR5TMyKoYWB7y4t4w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT Eclipse Plugin (V3) Shortcuts/Launchers

[Brandon Donnelson]

So I'm having a hard time reframing my mind around the changes, so I might 
need more tuning yet. :)

Here's what I have so far. 

Thoughts? 

-- 
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/0052ceff-3544-4c97-985f-68ae071186a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT Eclipse Plugin (V3) Shortcuts/Launchers

[Brandon Donnelson]

Hm, I've been on a different page. I'm still having a problem divorcing 
super dev mode. :) I'm trying to disconnect from the old ways. :)

-- 
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/26b0b51f-a9fe-4fdd-9ed7-4bd67309f630%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT Eclipse Plugin (V3) Shortcuts/Launchers

[Brandon Donnelson]

Or would removing it be better? 

-- 
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/877cd0df-0029-468a-9b7f-1ced660ff9e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT Eclipse Plugin (V3) Shortcuts/Launchers

[Brandon Donnelson]

Hm. Would s/Device/Mobile/ make more sense?

On Thu, Oct 6, 2016 at 9:07 AM Thomas Broyer <t.bro...@gmail.com> wrote:

> External "device"‽ Sounds strange to me (as a non-native English speaker
> at least)
>
>
> On Thursday, October 6, 2016 at 5:50:27 PM UTC+2, Brandon Donnelson wrote:
>
> I've made some adjustments. This time I put numbers on each label for
> referencing if needed. Do you think I should change it further?
>
>
> On Thursday, October 6, 2016 at 8:04:47 AM UTC-7, Brandon Donnelson wrote:
>
> I don't have lots of control over order. I have control grouping them and
> then they sort alphabetically.
>
> Legacy makes more sense now, you're right. I like it better than classic.
>
> I like where you're going with external server and embedded server. That's
> something I've been trying to make a distinction with and makes sense.
> You're refinements look to have a better distinction.
>
> I'll revise it some more and see if I can get closer.
>
>
> On Thursday, October 6, 2016 at 12:33:57 AM UTC-7, Thomas Broyer wrote:
>
> May I suggest "GWT Development Mode" and "GWT Legacy Development Mode"?
> Maybe "GWT Development Mode with external server" and "GWT Development
> Mode with embedded server"?
> IMO, making the distinction between "classic devmode" and "super devmode"
> was OK last year and before; but since 2.7 (released more than 1 year and a
> half ago already!) "sdm" is the default and it makes no sense to talk about
> "classic" devmode for something that's basically dead now (only supported
> in IE, where IE11 already supports source maps; and SDM works back to IE8,
> without sourcemaps then, but you can still use -style PRETTY in SDM in 2.8
> –was the default in 2.7 IIRC– to get something readable).
>
> It's 2016, we're about to release GWT 2.8, GWT 2.7 which brought SDM on by
> default was released in early 2015, I think it's time we call SDM simply
> "GWT Development Mode". You can stick a "(SDM)" in there if you want ("GWT
> Development Mode (SDM)") but I don't think it's even needed.
> As for the "with Jetty", I don't think it's important that it's Jetty; it
> could be Tomcat or Undertow it wouldn't change much things. It's more
> important that it's an embedded server vs. and external server.
> If you want to make it extra obvious that "with external server" is
> CodeServer and not just "DevMode with -noserver", then stick a
> "(CodeServer)" suffix: "GWT Development Mode with external server
> (CodeServer)".
>
> WDYT?
>
> On Wednesday, October 5, 2016 at 11:22:44 PM UTC+2, Ignacio Baca
> Moreno-Torres wrote:
>
> This is how I think that newbies will understand it easier... I suppose
> the change is too big, but maybe some part might be interesting. Any way
> current state is pretty good! good work. I have re-ordered, leaving the
> classic devmode the last one.
> 1. GWT Super DevMode - a client side GWT CodeServer (a.k.a. super devmode)
> 2. GWT Super DevMode and Jetty - a server side using Jetty and client side
> using GWT Script CodeServer (a.k.a. super devmode)
> 3. GWT Classic DevMode and Jetty - a server side using Jetty and client
> side using GWT Java CodeServer (a.k.a. classic devmode)
>
> This might not be technically correct, but I think that the codeserver and
> super devmode is practically the same (at least codeserver is implicit in
> super devmode), and is confusing for users. Even better, if you change
> "Classic" to "Java" and "Super" to "Script" is even easier to understand,
> but I suppose is not a good idea because Super DevMode is everywhere.
>
> On Wed, Oct 5, 2016 at 7:17 PM Brandon Donnelson <branfl...@gmail.com>
> wrote:
>
> What do you think of the labels for the GWT Eclipse Plugin (V3) Shortcuts
> and Launchers?
>
> FYI... I'm on track to releasing the EA soon and aim to reach beta before
> GWTCon. GPE (and the gpe-fork) is planning to be deprecated in the 4th
> quarter.
>
> --
> 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/7ddf1a06-5ede-4abe-adf4-74799669da42%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/7ddf1a06-5ede-4abe-adf4-74799669da42%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more option

Re: [gwt-contrib] GWT Eclipse Plugin (V3) Shortcuts/Launchers

[Brandon Donnelson]

I don't have lots of control over order. I have control grouping them and 
then they sort alphabetically. 

Legacy makes more sense now, you're right. I like it better than classic. 

I like where you're going with external server and embedded server. That's 
something I've been trying to make a distinction with and makes sense. 
You're refinements look to have a better distinction. 

I'll revise it some more and see if I can get closer. 


On Thursday, October 6, 2016 at 12:33:57 AM UTC-7, Thomas Broyer wrote:
>
> May I suggest "GWT Development Mode" and "GWT Legacy Development Mode"?
> Maybe "GWT Development Mode with external server" and "GWT Development 
> Mode with embedded server"?
> IMO, making the distinction between "classic devmode" and "super devmode" 
> was OK last year and before; but since 2.7 (released more than 1 year and a 
> half ago already!) "sdm" is the default and it makes no sense to talk about 
> "classic" devmode for something that's basically dead now (only supported 
> in IE, where IE11 already supports source maps; and SDM works back to IE8, 
> without sourcemaps then, but you can still use -style PRETTY in SDM in 2.8 
> –was the default in 2.7 IIRC– to get something readable).
>
> It's 2016, we're about to release GWT 2.8, GWT 2.7 which brought SDM on by 
> default was released in early 2015, I think it's time we call SDM simply 
> "GWT Development Mode". You can stick a "(SDM)" in there if you want ("GWT 
> Development Mode (SDM)") but I don't think it's even needed.
> As for the "with Jetty", I don't think it's important that it's Jetty; it 
> could be Tomcat or Undertow it wouldn't change much things. It's more 
> important that it's an embedded server vs. and external server.
> If you want to make it extra obvious that "with external server" is 
> CodeServer and not just "DevMode with -noserver", then stick a 
> "(CodeServer)" suffix: "GWT Development Mode with external server 
> (CodeServer)".
>
> WDYT?
>
> On Wednesday, October 5, 2016 at 11:22:44 PM UTC+2, Ignacio Baca 
> Moreno-Torres wrote:
>>
>> This is how I think that newbies will understand it easier... I suppose 
>> the change is too big, but maybe some part might be interesting. Any way 
>> current state is pretty good! good work. I have re-ordered, leaving the 
>> classic devmode the last one.
>> 1. GWT Super DevMode - a client side GWT CodeServer (a.k.a. super devmode)
>> 2. GWT Super DevMode and Jetty - a server side using Jetty and client 
>> side using GWT Script CodeServer (a.k.a. super devmode)
>> 3. GWT Classic DevMode and Jetty - a server side using Jetty and client 
>> side using GWT Java CodeServer (a.k.a. classic devmode)
>>
>> This might not be technically correct, but I think that the codeserver 
>> and super devmode is practically the same (at least codeserver is implicit 
>> in super devmode), and is confusing for users. Even better, if you change 
>> "Classic" to "Java" and "Super" to "Script" is even easier to understand, 
>> but I suppose is not a good idea because Super DevMode is everywhere.
>>
>> On Wed, Oct 5, 2016 at 7:17 PM Brandon Donnelson <branfl...@gmail.com 
>> > wrote:
>>
>>> What do you think of the labels for the GWT Eclipse Plugin (V3) 
>>> Shortcuts and Launchers? 
>>>
>>> FYI... I'm on track to releasing the EA soon and aim to reach beta 
>>> before GWTCon. GPE (and the gpe-fork) is planning to be deprecated in the 
>>> 4th quarter. 
>>>
>>> -- 
>>> 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/7ddf1a06-5ede-4abe-adf4-74799669da42%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/7ddf1a06-5ede-4abe-adf4-74799669da42%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/5896f0b7-9d42-405c-9628-a89efa1ceab6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Eclipse Code Server Launcher Icon

[Brandon Donnelson]

Oops, wrong screenshot. 


-- 
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/7dae0c53-76c6-4516-90f2-418c5d6dd58b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Eclipse Code Server Launcher Icon

[Brandon Donnelson]

I changed web application icon to have an icon with a server. I renamed the 
launcher name to super dev mode which is the code server launcher. 




-- 
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/2e0079ee-2cb6-4722-9f66-91d76ee65cf5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Eclipse Code Server Launcher Icon

[Brandon Donnelson]

I'm all for the CodeServer being the main entrypoint for SDM launching. 
Although we need IDEA to get on board and add the launcher too. I do think 
some of the pain can be taken out of the process when running the code 
server with another web server/device process. Like Eclipse has server 
runtimes, which you can automatically work with. I suspect once the kinks 
get worked out with working with the Code Server and web server/device 
runtimes, DevMode will decrease in use. I'd really like to have a code 
server nocache.js implement the -bindAddress as the hostName instead of 
window.location to really make it effective with external servers, so a 
proxy doesn't have to be setup and launcherDir can plan the xxx.nocache.js 
sdm launcher script. For most enterprise operations, I running the baked in 
jetty web server is not effective and not very flexible but for a few. 
Anyway, Eclipse is getting upgrades to the code server launcher. The next 
version will focus on the code server as the main entry point I think. I'll 
ask for more feedback as that comes together. 

On Saturday, August 27, 2016 at 12:38:05 AM UTC-7, Ignacio Baca 
Moreno-Torres wrote:
>
> Em... this is kind of related, some days ago I speak about this with 
> manolo in gitter; currently the CodeServer use the standard nocache.js 
> instead of the compile-on-refresh (actually uses the compile-on-refresh the 
> first time, but subsequent compilations uses the standard one). And... does 
> not makes more sense that the codeserver compilations always uses the 
> compile-on-refresh nocache.js? I think that this is in general quite 
> useful, but is even more useful for client only project so the codeserver 
> serves all the resources (just need to move your index.html into a public 
> folder like this 
> https://github.com/ibaca/rxcanvas-gwt/blob/master/src/main/java/rxcanvas/public/index.html).
>  
> Hopefully this will promove using codeserver alone even more.
>
> On Friday, August 26, 2016 at 5:34:28 PM UTC+2, JonL wrote:
>>
>> I guess I didn't word it correctly.  I think I am talking more of the 
>> experience of running the CodeServer and the embedded Jetty Server serving 
>> the app, in one shot utilizing the eclipse plugin has become synonymous in 
>> my head with SDM.  Where as running the web app on an external server and 
>> manually starting the CodeServer, I don't so much attribute to being 
>> "super", but more "cumbersome" dev mode.  So I guess what I am trying to 
>> say is that from the eclipse development perspective, utilizing the plugin, 
>> there should always be a one shot command that starts up the CodeServer and 
>> deploys the app for you and then maybe you start a browser using SDBG 
>> Plugin, should remain the most cumbersome experience for utilizing the 
>> plugin, by default.  
>>
>> I don't use the maven plugin, but I would guess by discussion that there 
>> is a similar experience where the maven plugin starts up the codeserver and 
>> uses DevMode plugin for deployment.  
>>
>> So ultimately, I think, unless there is a better way, across all these 
>> plugins to provide a similar getting started experience where you run one 
>> command to start the CodeServer and a deployment server, my vote, if it 
>> counts for anything, would be to keep c.g.g.dev.DevMode with only SDM and 
>> refactor it possibly so that its clear to what it is and separate it, 
>> cognitively, from the old classic DevMode utilizing the browser plugin.
>>
>> On Friday, August 26, 2016 at 7:58:24 AM UTC-7, Thomas Broyer wrote:
>>>
>>>
>>>
>>> On Friday, August 26, 2016 at 4:30:48 PM UTC+2, JonL wrote:

 I have always considered the deprecation of "DevMode" to mean the 
 deprecation of the "HostedMode"/GWT Dev Mode plugin combo and that SDM was 
 the non-deprecated version. It sounds like some are considering losing SDM 
 as the default run mode.  I think that would be a mistake and would make 
 it 
 appear that GWT is more cumbersome to use than it is.  Hosted Mode w./ Dev 
 Mode Plugin was broken due to the deprecation of the NPAPI plugin, other 
 than possibly refactoring out SDM from the DevMode class, I would 
 personally consider removing SDM as breaking something that isn't broken 
 for no particular reason.

>>>
>>> I don't understand what you mean.
>>>
>>> DevMode can mean either "dev mode using the browser plugin", or "the 
>>> c.g.g.dev.DevMode entrypoint class".
>>> SDM, to me, can only mean "dev mode using compiled-on-the-fly JS", so 
>>> it'd be the opposite of "dev mode using the browser plugin", without saying 
>>> "how" you run it.
>>> The opposite of "the c.g.g.dev.DevMode class" is CodeServer (i.e. "the 
>>> c.g.g.dev.codeserver.CodeServer class").
>>> And SDM could be used either through c.g.g.dev.DevMode or CodeServer.
>>> So for SDM, there's no terminology problem, and yet I don't understand 
>>> what you mean by "removing SDM".
>>>
>>> CodeServer will stay, that's a given. 

Re: [gwt-contrib] Re: CodeServer with Bookmarklets not working in GWT 2.7 (2nd request)

[Brandon Donnelson]

Proxying wasn't an option for developers because of the I.T. security
protocols. Besides it feels a bit overcomplicated to have to set up a
channel back to the code server. I think it would be easier to clobber the
codeserver api with a workaround and setting the hosteName and hand that to
the developers. I'm contemplating on forking the code server for GWT 2.7
users to provide a workaround for the hostName through the program
arguments.

On Sat, Sep 10, 2016 at 1:43 AM Thomas Broyer <t.bro...@gmail.com> wrote:

> How about proxying through a local server that would intercept the
> nocache.js and route everything else to your external server? This is
> basically how webpack devserver and browserSync work in the JS land.
>
> --
> 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/13bfb1ba-f2fb-40cf-afda-c9902d016cb3%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
*Brandon Donnelson*
GXT Support Engineer
<http://www.facebook.com/senchainc> <http://twitter.com/sencha>
<https://www.linkedin.com/company/sencha-inc>
<http://www.youtube.com/SenchaInc>
<https://plus.google.com/117303203295549187007?prsrc=3>
[image: SenchaCon 2016 Aria Resort, Las Vegas, November 7-9]
<https://www.senchacon.com/>
*Join me at SenchaCon 2016!*

-- 
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/CAA_mbNO97_gUCZiAPKOAG%2BNRG3pD0AWyt8wLrjFhSdGwSdioEA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: CodeServer with Bookmarklets not working in GWT 2.7 (2nd request)

[Brandon Donnelson]

I haven't dug in yet, just wanting to use it. That sounds promising. Using 
bookmarlets doesn't work when the module is embedded in another iframe. so 
the next issue I need to deal with is helping detect the module when it's 
not in the main body but in another iframe of the document. 

The other workaround is to implant the project.nocache.js js launching in 
the war and send it off to the external server. So this makes another 
problem I have hit a couple times. Where I change the var hostName = 
"127.0.0.1";  to a specific ip because I loaded the app with 
project.nocache.js. I like this hack but I'm wishing I could set that in 
the code server launcher arguments. 

Anyway it's all about using an external server. 

-- 
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/41735d5b-1848-44e6-be31-3a34d87ddec7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: CodeServer with Bookmarklets not working in GWT 2.7 (2nd request)

[Brandon Donnelson]

Workaround, hit dev mode off then compile again. 

-- 
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/2f411e2b-688f-4028-b8f9-95f052952e57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] CodeServer with Bookmarklets not working in GWT 2.7 (2nd request)

[Brandon Donnelson]

There are some complicated enterprise configurations where the application 
is dependent on other applications. And staging this on an external web 
server is challenging. I've seen enough web server configurations to want 
bookmarklets to work. I know it's not the preferred way to boot up SDM, but 
it would be quite handy to have bookmarklets fire of the compile and link 
up the resources. 

Does anybody have a workaround for the bookmarklet's javascript? And could 
we get this fixed in GWT 2.8? 


The project below, the first compile works just fine using the CodeServer 
and firing off the compile from the bookmarklet. But then the second 
compile request to the code server fails because it must not be sending 
some query string property so it only binds to one permutation. 
```

Turning off precompile in incremental mode.

Super Dev Mode starting up

   workDir: 
/var/folders/x8/9wz7qtw96t7grkdyjw1l61p4gn/T/gwt-codeserver-5458587005926250195.tmp

   Loading Java files in com.gonevertical.snowy.SnowyMountainProject.

   Module setup completed in 19801 ms

Sep 09, 2016 11:45:00 AM org.eclipse.jetty.server.Server doStart

INFO: jetty-8.y.z-SNAPSHOT

Sep 09, 2016 11:45:00 AM org.eclipse.jetty.server.AbstractConnector doStart

INFO: Started SelectChannelConnector@127.0.0.1:9876


The code server is ready at http://localhost:9876/

GET /recompile/SnowyMountainProject

   Job com.gonevertical.snowy.SnowyMountainProject_1_0

  starting job: com.gonevertical.snowy.SnowyMountainProject_1_0

  binding: gxt.device=desktop

  binding: gxt.user.agent=chrome

  binding: locale=default

  binding: user.agent=safari

  binding: user.agent.os=mac

  Compiling module com.gonevertical.snowy.SnowyMountainProject

 Unification traversed 32527 fields and methods and 3143 types. 
3090 are considered part of the current module and 3090 had all of their 
fields and methods traversed.

 Compiling 1 permutation

Compiling permutation 0...

Linking per-type JS with 3074 new types.

   prelink JS size = 5557062

   prelink sourcemap = 5557062 bytes and 143563 lines

   postlink JS size = 5235031

   postlink sourcemap = 5235031 bytes and 135811 lines

Source Maps Enabled

 Compile of permutations succeeded

 Compilation succeeded -- 14.026s

  Linking into 
/var/folders/x8/9wz7qtw96t7grkdyjw1l61p4gn/T/gwt-codeserver-5458587005926250195.tmp/com.gonevertical.snowy.SnowyMountainProject/compile-2/war/SnowyMountainProject;
 
Writing extras to 
/var/folders/x8/9wz7qtw96t7grkdyjw1l61p4gn/T/gwt-codeserver-5458587005926250195.tmp/com.gonevertical.snowy.SnowyMountainProject/compile-2/extras/SnowyMountainProject

 Link succeeded

 Linking succeeded -- 0.693s

  14.859s total -- Compile completed

GET /recompile/SnowyMountainProject

   Job com.gonevertical.snowy.SnowyMountainProject_1_1

  starting job: com.gonevertical.snowy.SnowyMountainProject_1_1

  binding: locale=default

  binding: user.agent=safari

  Compiling module com.gonevertical.snowy.SnowyMountainProject

 [ERROR] Current binding properties are expanding to more than one 
permutation but per-file compilation requires that each compile operate on 
only one permutation.

  [WARN] recompile failed

  [WARN] continuing to serve previous version

GET /recompile/SnowyMountainProject

   Job com.gonevertical.snowy.SnowyMountainProject_1_2

  starting job: com.gonevertical.snowy.SnowyMountainProject_1_2

  binding: locale=default

  binding: user.agent=safari

  Compiling module com.gonevertical.snowy.SnowyMountainProject

 [ERROR] Current binding properties are expanding to more than one 
permutation but per-file compilation requires that each compile operate on 
only one permutation.

  [WARN] recompile failed

  [WARN] continuing to serve previous version

```


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/d901d28f-f713-4a0b-a0dc-17dce01e5da4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Eclipse Code Server Launcher Icon

[Brandon Donnelson]

Hm, I hadn't thought about making the CodeServer the default yet. I've been
helping folks convert to super dev mode every chance I get so my feeling is
that keeping the legacy the default method that starts up with SDM probably
is the way to go on for a bit longer.  I've got to be careful I don't bite
off more than I can chew so my goal is to get the CodeServer launcher
running swimmingly. That said, I'm afraid of upsetting the applecart too
much by doing any big changes. Since the CodeServer launcher came later,
I've been keeping it as a new launcher. I think it's effective to use with
custom integrated and external server runtimes. The integrated jetty server
usually doesn't fit most enterprises production structures so it causes all
kinds of dev strategy workarounds to make things work well. And using
DevMode with -noserver works great for most things but the proxy of the
arguments from DevMode doesn't work for every situation like CodeServer
does.

Although there is another branch for the GWT Eclipse plugin that I'm
working on which will be the new and improved version. This I think might
be the ticket to change the feature here. In fact I like the idea for this
branch. I'm having to separate out the Google cloud tools to make way for
combining up with the cooler stuff coming from the Google Cloud Plugin.

Good idea, thanks.

-Brandon





On Thu, Aug 25, 2016 at 5:24 PM Jens  wrote:

> I guess the future is CodeServer + optional external servlet container.
>
> So IMHO it would be more straight forward to just have "GWT Web
> Application" which always launches CodeServer.main() directly and not
> through DevMode.main(). Within this run configuration you can optionally
> choose to automatically launch an external servlet container as well, e.g.
> through Eclipse WTP or by running a second run configuration like a maven
> goal / gradle task or a terminal command.
>
> => normal GWT icon
>
>
> If you want to support the legacy guys there would be "GWT Web Application
> (legacy)" which would launch classic DevMode
>
> => GWT icon with some standard Eclipse server icon
>
>
> -- J.
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Contributors" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit-contributors/WGLtekU5U5U/unsubscribe
> .
> To unsubscribe from this group and all its topics, 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/6e8f5a16-6d20-41b2-bb99-bb3964cbfda7%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/CAPnsdHQQcbPw0yxGUwGVEGa2bDN6Q6R6Yo7SMbogc0h_eNVNWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Eclipse Code Server Launcher Icon

[Brandon Donnelson]

Hm, based on the guidelines the server icon might make the most sense. That 
would be an easy manipulation then. The other option could be to just add 
the run arrow.

-- 
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/8eed5f6f-763b-4f94-bc2e-101fddc1b61d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Eclipse Code Server Launcher Icon

[Brandon Donnelson]

The problem with the current GWT logo is that I've already assigned that to
the web application launcher and both look alike. I'd like to provide a
little bit of distinction between the Web App launcher and Code Server
Launcher icons, so that way it's obvious. The icon design looks promising
tho. It has to be 16x16 so it's a bit too tall I think.


On Thu, Aug 25, 2016 at 10:31 AM Ignacio Baca Moreno-Torres <
igna...@bacamt.com> wrote:

> I'll personally prefer the current logo (GWT logo) for the codeserver,
> because I think that the codeserver is the actual GWT part, and for the
> devmode and web application (which I suppose are a devmode or variants
> using some java web server) I will suggest a standard server icon plus a
> small GWT logo, so the GWT logo always means codeserver. You can even
> combine the jetty icon + gwt logo, or app engine + gwt logo, etc.
>
>
> <https://lh3.googleusercontent.com/-TfYGgsk5_v8/V78q4ksOpVI/AAABDr4/BzoNisvwhD4iN9V-OUwDuR_w1WFbDe7KACLcB/s1600/devmode.png>
>
> On Thursday, August 25, 2016 at 6:36:17 PM UTC+2, Brandon Donnelson wrote:
>>
>> That reminds me I need to change the classpath for it too.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Contributors" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit-contributors/WGLtekU5U5U/unsubscribe
> .
> To unsubscribe from this group and all its topics, 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/97a5c6ff-fd45-42e5-9f67-3929467c9e1b%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/97a5c6ff-fd45-42e5-9f67-3929467c9e1b%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/CAPnsdHQ3QiY9W15MfeV%2BDPmLobG0NA7xZcq2XSmTwNsobpkSBg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Eclipse Code Server Launcher Icon

[Brandon Donnelson]

That reminds me I need to change the classpath for it too. 

-- 
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/fc5cb231-1745-47ef-86c6-0cba2db51892%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Hide GWT Development Mode window

[Brandon Donnelson]

Figured I'd addon. If you're familiar with the GWT Eclipse plugin, a fork 
of GPE there are launchers for both GWT and the CodeServer. Both of the GWT 
launcher types can run Super Dev Mode without a remote ui window and do so 
by default. The launchers just make launching the Java process with a 
preset arguments that run the remote ui in headless mode. If I remember 
correctly I think it's the -remoteUI argument that will cause the window to 
display. Having the service runs it without seeing it. If you're using 
IDEA, then a java launcher with the CodeServer could be used as well. 
Anyway, these are some other ways to running the service without seeing the 
RemoteUI. 

http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html

-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/f0235aab-0b1a-4d9e-a9bc-b91ec953fa93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Brandon Donnelson]

I was trying to test the Maven samples, although each one of them seem to 
have some sort of issue. Could be I'm missing a step, or maybe some code 
configuration tuning is needed. I haven't noticed any blockers or other 
issues outside of that for IE9 on Win7. I'll aim for another browser 
tomorrow. 

I'm assuming that mvn gwt:run doesn't exist b/c I don't see it in the goals 
list, so I'm wondering what's the best testing goal for the smoke test. 

-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/a3772510-e65f-4aaa-9005-035708449bec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Brandon Donnelson]

Where's the link to the GWT 2.8.0-rc1.zip? 

On Thursday, July 21, 2016 at 7:22:11 AM UTC-7, Thomas Broyer wrote:
>
>
>
> On Thursday, July 21, 2016 at 4:11:09 PM UTC+2, Michael Joyner wrote:
>>
>> Can it be tagged and pulled via jitpack.io ?
>>
>
> Ha ha, jitpack wouldn't know how to build and deploy it: 
> https://jitpack.io/docs/BUILDING/
> …and the RC1 tag can still "move" if we find bugs during the smoke tests 
> (it **would** move, as I found small issues, e.g. 
> https://gwt-review.googlesource.com/15445)
>
> Ideally, you should use the gwt-2.8.0-rc1.zip provided by Daniel as input 
> to the maven/push-gwt.sh script from the GWT repo (select 2.8.0-rc1 and 
> 1.0.0 for gwt and jsinterop versions respectively)
> Currently, 2.8.0-SNAPSHOT are the same as 2.8.0-rc1, so you could also use 
> that (but if you're planning on doing formal DOA/smoke tests before the RC1 
> release, you should use the maven/push-gwt.sh script)
>

-- 
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/80338352-9133-4404-ad51-8147b01431d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Brandon Donnelson]

Good to hear Manolo. So, I've got Windows 7 with IE9 and IE10 and can start
with those then. I don't have Windows 7 IE11, instead I have Windows 8
IE11. Come to think of it, there seems to be to many of the windows 7's. I
think Windows 8 would work for IE11, would that be ok? And would it be of
interest to test MS Edge on Windows 10?

-Brandon



On Wed, Jul 20, 2016 at 10:07 AM Manuel Carrasco Moñino <man...@apache.org>
wrote:

> 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 a topic in the
> Google Groups "GWT Contributors" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit-contributors/WegHJlSMoos/unsubscribe
> .
> To unsubscribe from this group and all its topics, 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/CAM28XAte3oXuCVTTxxxBeR4oTOJ5OWr_wzSngEwgv6KzMMbBJw%40mail.gmail.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAte3oXuCVTTxxxBeR4oTOJ5OWr_wzSngEwgv6KzMMbBJw%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/CAPnsdHTohcasakWAQTbLj-86zja3PkH9hUhmBdWhVRvygw-cyw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Brandon Donnelson]

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.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Proposal for making Object literals more intuitive to define

[Brandon Donnelson]

Using what Thomas said works good. I've had the same question about using 
Object literals.  So I wrote down some examples and stored them here. You 
may need 2.8 +(nightly) to use some of the example options.
http://docs.sencha.com/gxt/4.x/gwt/jsinterop/jsinterop_object_literals.html

On Thursday, April 7, 2016 at 6:14:28 AM UTC-7, Paul Stockley wrote:
>
> Bloat and performance is one reason. However, the real reason is that 
> frameworks like react and redux choke if you pass anything but a plain 
> JavaScript object to some of their API's. I don't really care what the 
> annotation is e.g. JsStruct or JsLiteral would work just as well.
>
>
>  

> On Thursday, April 7, 2016 at 6:51:06 AM UTC-4, Thomas Broyer wrote:
>>
>>
>>
>> On Wednesday, April 6, 2016 at 5:46:49 PM UTC+2, Paul Stockley wrote:
>>>
>>> This is the only way you can create a true object literal equivalent in 
>>> JsInterop (i.e. no prototype other than Object) 
>>>
>>
>> The real question is whether (and why) you need "no prototype other than 
>> Object", other than for the bloat in the generated JS (and then 
>> @JsType(isNative=true, namespace=JsPackage.GLOBAL, name="Object") is what 
>> you're after, no need for syntactic sugar –moreover if it has approximate 
>> naming semantics)
>> Plus: your proposed literal=true as a synonym for 
>> isNative=true,namespace=JsPackage.GLOBAL,name="Object", in addition to 
>> being misleading, is likely to collide with future proper object literal 
>> support, at least as currently proposed in 
>> https://docs.google.com/document/d/1DFrC-GtcK7cu6DGxaWCswvb2fai9cnrWPvGcdgsKlBw/edit?usp=sharing
>>  
>> (I, for one, quite like the JsStruct; and I'd go as far as making it a 
>> special type, without the @JsType(literal=true) at all)
>>
>

-- 
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/7ae5f5ac-08fc-47ff-bd89-fed4c24f3e60%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Status of Patch

[Brandon Donnelson]

What's the status of this patch? This is simply changing the address of the 
server to make it consistent. 

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


This patch will help fix source maps in IE, I think it would be a benefit 
to getting it in. 

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/a05c0aae-5e3c-48ec-96fd-00c24c87c87a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: JsInterop Object Literal

[Brandon Donnelson]

Thanks Paul. I haven't seen use of the JsOverlay yet, that's nifty.

Nice Ignacio.

On Tue, Mar 22, 2016 at 6:01 AM Paul Stockley  wrote:

> That's a nice approach.
>
>
> On Tuesday, March 22, 2016 at 3:25:13 AM UTC-4, Ignacio Baca Moreno-Torres
> wrote:
>>
>> If your concert is to be able to write one-line initializers, and you are
>> using java8 syntax you also do something like that:
>>
>> public static  T apply(T t, Consumer fn) {
>> fn.accept(t);
>> return t;
>> }
>>
>> @JsType(isNative = true, namespace = JsPackage.GLOBAL, name = "Object")
>> class SomeObjectLiteral {
>> int field1;
>> String field2;
>> }
>>
>> {
>> SomeObjectLiteral sol = apply(new SomeObjectLiteral(), o -> { o.field1 = 
>> 1; o.field2 = "str"; });
>>
>> }
>>
>>
>> Copied from kotlin (although without method extensions and method inline
>> is not the same ;)), this is usable for client and server code when you
>> need to initialize small pojos without fluent api.
>>
>> On Tuesday, March 22, 2016 at 5:42:23 AM UTC+1, Paul Stockley wrote:
>>>
>>> I have come up with 3 approaches to creating object literals given the
>>> current JsInterop capabilities:
>>>
>>> *1) Construct and set the fields individually*
>>>
>>> @JsType(isNative = true, namespace = JsPackage.GLOBAL, name = "Object")
>>> class SomeObjectLiteral {
>>>
>>>int field1;
>>>
>>>String field2;
>>>
>>> }
>>>
>>>
>>> SomeObjectLiteral o = new SomeObjectLiteral();
>>>
>>> o.field1 = 1;
>>>
>>> o.field2 = "Some value";
>>>
>>>
>>> *2) Define a fluent interface*
>>>
>>>
>>> @JsType(isNative = true, namespace = JsPackage.GLOBAL, name = "Object")
>>> class SomeObjectLiteral {
>>>
>>>int field1;
>>>
>>>String field2;
>>>
>>>
>>>
>>>@JsOverlay
>>>public final SomeObjectLiteral Field1(int v) {
>>>   field1 = v;
>>>   return this;
>>>}
>>>
>>>
>>>@JsOverlay
>>>public final SomeObjectLiteral Field2(String v) {
>>>   field2 = v;
>>>   return this;
>>>}
>>>
>>> }
>>>
>>>
>>> You can then write
>>>
>>>
>>> new SomeObjectLiteral().Field1(1).Field2("A value");
>>>
>>>
>>> Note I didn't call the setter setFieldx. This is because you currently get 
>>> a runtime error if you do this.
>>>
>>>
>>>
>>> *2) Use an ObjectLiteral Helper*
>>>
>>>
>>> You can define a helper similar to
>>>
>>>
>>> public class ObjectLiteral {
>>> public static  O $(O base, Object ...fieldValues) {
>>> String fieldName = null;
>>>
>>> for(Object f : fieldValues) {
>>> if (fieldName == null)
>>> fieldName = (String)f;
>>> else {
>>> if (f instanceof Integer)
>>> setField(base, fieldName, ((Integer) f).intValue());
>>> else if (f instanceof Double)
>>> setField(base, fieldName, ((Double) f).doubleValue());
>>> else if (f instanceof Boolean)
>>> setField(base, fieldName, ((Boolean) f).booleanValue());
>>> else
>>> setField(base, fieldName, f);
>>>
>>> fieldName = null;
>>> }
>>> }
>>>
>>> return base;
>>> }
>>>
>>> private final static native void setField(Object literal, String 
>>> fieldName, int i) /*-{
>>> literal[fieldName] = i;
>>> }-*/;
>>>
>>> private final static native void setField(Object literal, String 
>>> fieldName, double d) /*-{
>>> literal[fieldName] = d;
>>> }-*/;
>>>
>>> private final static native void setField(Object literal, String 
>>> fieldName, boolean b) /*-{
>>> literal[fieldName] = b;
>>> }-*/;
>>>
>>> private final static native void setField(Object literal, String 
>>> fieldName, Object o) /*-{
>>> literal[fieldName] = o;
>>> }-*/;
>>> }
>>>
>>>
>>> You can then write
>>>
>>>
>>> import static com.xxx.ObjectLiteral.$;
>>>
>>>
>>> @JsType(isNative = true, namespace = JsPackage.GLOBAL, name = "Object")
>>> class SomeObjectLiteral {
>>>
>>>int field1;
>>>
>>>String field2;
>>>
>>> }
>>>
>>>
>>> $(new SomeObjectLiteral(), "field1",123, "field2","some value")
>>>
>>>
>>> You would probably want to add some more error checking to the helper. This 
>>> approach probably isn't
>>>
>>> particularly efficient, especially if you pass a lot of field values that 
>>> get boxed into Object primitives.
>>>
>>> It would be nice if the compiler unboxed varargs passed to isNative=true 
>>> methods. If this was true you
>>>
>>> could write a much more efficient javascript version.
>>>
>>>
>>>
>>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Contributors" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit-contributors/bix56s-OJ-E/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this 

Re: JsInterop and Sencha Ext js framework

[Brandon Donnelson]

Thomas has a point. I am biased, because work for Sencha. :)

This is my opinion. ExtJs has some nice Api docs, but they're written in 
javascript of course. And when using a external javascript library, I think 
hugging it as closely as possible helps tremendously. And the first reason 
I mean when I say, "hug it closely as possible" means the docs will easily 
guide the way. The second reason is, javascript has dynamic types and this 
both affects the return and function parameters. I'm all about getting the 
job done in the shortest path with iterative development in mind. I think 
this may be true for me on most libraries. I've found after building the 
Google maps api wrapper in JSNI, that it added a complexity and labor of 
maintenance that I would have rather concentrated on developing business 
logic to get the job done. That said, there are many ways to do things and 
this is just one of them. 

I found it quite simple to through together the object literals which leads 
to the creation of the javascript objects in the ExtJs world. I didn't 
follow the Java format in creation on this example in the gist. I kept it 
simple using Object for the types. Once i figured out Object literal 
creation, in the case ExtJs wants object literals instead of an Object, it 
was a snap to throw together a wrapper of just what I needed. 

https://gist.github.com/branflake2267/5ea05b1cf0c956953026 - Example of 
generically wrapping some javascript. 

Anyway, I'm digging JsInterops flexibility in writing Javascript. 


On Monday, March 21, 2016 at 1:08:46 AM UTC-7, ateletin wrote:
>
> I just want to let you know that my "Person" example which is written 
> using 
> ExtJs works ok with JsInterop. 
> It seems that the problem was the ExtJs library that I used.. something 
> was 
> broken in it. I've changed the library and now I get the expected results. 
>
> Thank you all for your time. 
>
>
>
> -- 
> View this message in context: 
> http://google-web-toolkit.2317884.n4.nabble.com/JsInterop-and-Sencha-Ext-js-framework-tp15385p15429.html
>  
> Sent from the Google Web Toolkit mailing list archive at Nabble.com. 
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: JsInterop Object Literal

[Brandon Donnelson]

Thank you! That's awesome. 

On Sunday, March 20, 2016 at 12:08:10 AM UTC-7, Ray Cromwell wrote:
>
> Right now, the best you can do is 
>
> @JsType(isNative = true, namespace =JsPackage.GLOBAL, name = "Object") 
> class MyLiteral { 
> } 
>
> And put js properties on the object 
>
>
> On Sat, Mar 19, 2016 at 11:11 PM, Brandon Donnelson 
> <branfl...@gmail.com > wrote: 
> > I found a doc talking about object literal creation 
> > 
> https://docs.google.com/document/d/1DFrC-GtcK7cu6DGxaWCswvb2fai9cnrWPvGcdgsKlBw/edit.
>  
>
> > 
> > -- 
> > 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/3c62911e-0304-4181-b6d3-03b4689debb9%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/1fee2041-b886-45a7-8396-1545449b72f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] JsInterop Object Literal

[Brandon Donnelson]

Can JsInterop create an object literal? 

var foo = {a:0, b:1};


-- 
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/cfdf6ba5-f414-47b1-9dd7-eb4a9d81e245%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: JsInterop Object Literal

[Brandon Donnelson]

I found a doc talking about object literal creation 
https://docs.google.com/document/d/1DFrC-GtcK7cu6DGxaWCswvb2fai9cnrWPvGcdgsKlBw/edit.
 

-- 
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/3c62911e-0304-4181-b6d3-03b4689debb9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Constructing a new JsType(isNative=true) object

[Brandon Donnelson]

isNative means there has to be some existing javascript class the java type 
is wrapping. Is there a javascript class? 

On Monday, March 14, 2016 at 1:37:21 PM UTC-7, Paul Stockley wrote:
>
> Is it legal to call new on a class marked as JsType(isNative=true)? When I 
> try it, I get a runtime error.
>
>
> @JsType(isNative=true, name="HTMLProps", namespace=JsPackage.GLOBAL)
> public class HTMLProps {
> ...
> }
>
> new HTMLProps() results in the following code
>
> new $wnd.HTMLProps which is undefined. This is using superdev mode.
>
>

-- 
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/14ffd048-db87-45af-ac7c-9bc47d35a0e8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: JsInterop and Sencha Ext js framework

[Brandon Donnelson]

Good question. I've wrapped an api or two and I've found it's alot of work.
Since then, wrapping using JSNI feels painful. So I've been working on a
generator to build the jsinterop for the extjs api with the flip of a
switch. Besides that, the extjs team is cruising on the future iterations
and I wanted something to keep up with what they put out.

On Thu, Mar 17, 2016 at 7:10 AM Alain Ekambi <jazzmatad...@gmail.com> wrote:

> Which brings me back to the question of why not help improving ext4j
> instead of having tons of micro solutions ?
> On 17 Mar 2016 14:50, "Brandon Donnelson" <branflake2...@gmail.com> wrote:
>
>> ateletin, I've been working using jsinterop with extjs 6+, if you have
>> some questions ping me and I can help with that. There are two ways to
>> configure it, first is using ext.define. The other is using the ext class
>> and instantiate it with a config object. Ext.define is far more documented
>> than instantiating the classes, so it's easier. I've got a generator for
>> generating all the class types, but it's not finished yet.
>>
>> Thanks,
>> Brandon
>>
>> On Thursday, March 17, 2016 at 1:44:47 AM UTC-7, ateletin wrote:
>>>
>>> Maybe I wasn't clear enough. What I want to do is to wrap the following
>>> javascript into a java object like.
>>>
>>> Ext.define('com.acme.client.Person', {
>>>  firstName : 'Kimi',
>>>  lastName : 'Raikkonen',
>>>
>>> fullName : function() {
>>> return firstName + " " + lastName;
>>> }
>>> });
>>>
>>> into
>>>
>>> package com.acme.client;
>>> @JsType(isNative = true)
>>> public class Person {
>>> public String firstName;
>>> public String lastName;
>>>
>>> public native String fullName();
>>> }
>>>
>>> So by calling java fullName() to return the result of javascript
>>> fullName(),
>>> or when I call java firstName to return "Kimi".
>>> Can ExtJs Wrapper API help me with this? If so, can you give me a
>>> direction?
>>> And yes, we don't plan to wrap the ExtJs library.
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://google-web-toolkit.2317884.n4.nabble.com/JsInterop-and-Sencha-Ext-js-framework-tp15385p15403.html
>>> Sent from the Google Web Toolkit mailing list archive at Nabble.com.
>>>
>> --
>>
> You received this message because you are subscribed to the Google Groups
>> "GWT Users" 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 https://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 "GWT Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit/4tyws5bK11s/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 https://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 "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: JsInterop and Sencha Ext js framework

[Brandon Donnelson]

ateletin, I've been working using jsinterop with extjs 6+, if you have some 
questions ping me and I can help with that. There are two ways to configure 
it, first is using ext.define. The other is using the ext class and 
instantiate it with a config object. Ext.define is far more documented than 
instantiating the classes, so it's easier. I've got a generator for 
generating all the class types, but it's not finished yet. 

Thanks,
Brandon

On Thursday, March 17, 2016 at 1:44:47 AM UTC-7, ateletin wrote:
>
> Maybe I wasn't clear enough. What I want to do is to wrap the following 
> javascript into a java object like. 
>
> Ext.define('com.acme.client.Person', { 
>  firstName : 'Kimi', 
>  lastName : 'Raikkonen', 
> 
> fullName : function() { 
> return firstName + " " + lastName; 
> } 
> }); 
>
> into 
>
> package com.acme.client; 
> @JsType(isNative = true) 
> public class Person { 
> public String firstName; 
> public String lastName; 
> 
> public native String fullName(); 
> } 
>
> So by calling java fullName() to return the result of javascript 
> fullName(), 
> or when I call java firstName to return "Kimi". 
> Can ExtJs Wrapper API help me with this? If so, can you give me a 
> direction? 
> And yes, we don't plan to wrap the ExtJs library. 
>
>
>
>
> -- 
> View this message in context: 
> http://google-web-toolkit.2317884.n4.nabble.com/JsInterop-and-Sencha-Ext-js-framework-tp15385p15403.html
>  
> Sent from the Google Web Toolkit mailing list archive at Nabble.com. 
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

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

[Brandon Donnelson]

I would choose Java 1.8 all the way if you have to choose. I would do this 
because this is going to be a long standing maintenance release. Just a 
note, the Eclipse neon out in June will require Java 1.8. I think it makes 
sense to upgrade. I think folks can go through the pain of upgrading there 
servlet containers to Java 1.8 if they want to move forward. 


On Friday, February 12, 2016 at 8:39:41 AM UTC-8, Colin Alworth wrote:
>
> Switching to gwt-contrib, we're losing voices who are involved in this 
> discussion. 
>
> Maybe I am missing something, but I had that that the discussion moved 
> toward the fact that the compiler and dev mode will require Java8, but that 
> gwt-servlet could still be compiled to Java7, allowing deployment on Java7. 
>
> The supersource classes do require Java8 language level in the GWT 
> compiler (in order to have "default" mean anything), but these emulation 
> classes are not compiled to bytecode, and not required to compile the rest 
> of GWT. 
>
> We already have cases where GWT will not work without Java8 (specifically 
> Dev Mode and anything that leans on it), so this isn't a change from the 
> beta. I agree with Daniel that effort will be required to compile to Java7 
> bytecode (as previously discussed), and while I would be interested in 
> helping to achieve this, we've also clearly stated that Java8 support is a 
> more important goal (both in terms of keeping GWT modern and up to date in 
> the Java world, but also in terms of staying relevant for web development 
> with lambdas and JSInterop).
>
> Even if we manage to compile to Java7 bytecode from a Java8 JDK, it has 
> been encouraged that we extensively test to ensure that all of the code 
> does as we expect, as regressions have been seen in the past. RetroLambda 
> was another suggestion that also may have merit.
>
> On Fri, Feb 12, 2016 at 10:28 AM Daniel Kurka  > 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 > > 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 >> >:
>>> > +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, is that there are many big companies and
>>> >> government agencies moving very slow, their standard server 
>>> configuration is
>>> >> java7, as well as their code standards.
>>> >>
>>> >> Their GWT projects are compiled in one phase (not client and server
>>> >> sides). It could be very difficult for them to compile their byte 
>>> code for
>>> >> 1.7.
>>> >> It's true that if they don't use java 8 many features in 2.8 are 
>>> useless
>>> >> for them, but we have to facilitate and encourage users to be in 
>>> latest
>>> >> version.
>>> >>
>>> >> I don't know how complex it could be, but if for example, ignoring 
>>> java8
>>> >> /emul/ classes could fix the problem I think it's worth to consider.
>>> >>
>>> >> On Fri, Feb 12, 2016 at 3:42 PM, 'Daniel Kurka' 

[gwt-contrib] Addresses are different when running SDM with bindAddress 0.0.0.0?

[Brandon Donnelson]

What would it take to sync both addresses?  

- "-bindAddress 0.0.0.0" was used, but didn't affect the code server. 
- The code server has a different address than jetty server. 



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/2a3d3534-6685-4736-8906-fd5aef496d92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Addresses are different when running SDM with bindAddress 0.0.0.0?

[Brandon Donnelson]

Thanks Jens,
Brandon

On Thu, Jan 28, 2016 at 3:52 PM, Jens <jens.nehlme...@gmail.com> wrote:

> Make both lines the same:
>
>
> https://gwt.googlesource.com/gwt/+/master/dev/core/src/com/google/gwt/dev/DevModeBase.java#156
>
> https://gwt.googlesource.com/gwt/+/master/dev/codeserver/java/com/google/gwt/dev/codeserver/Options.java#529
>
> One uses getHostName() while the other uses getHostAddress()
>
> -- 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/45e5da4d-6895-4174-8205-fd71040dd127%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/45e5da4d-6895-4174-8205-fd71040dd127%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Regards,
*Brandon Donnelson*
GXT Support Engineer
Office: +1-650-243-0623

[image: Sencha Inc.] <https://www.sencha.com/>

[image: http://cdn.sencha.com/img/2016-email-sig/icon-facebook-24x24.png]
<http://www.facebook.com/senchainc>

[image: http://cdn.sencha.com/img/2016-email-sig/icon-twitter-24x24.png]
<http://twitter.com/sencha>

[image: http://cdn.sencha.com/img/2016-email-sig/icon-linkedin-24x24.png]
<https://www.linkedin.com/company/sencha-inc>

[image: http://cdn.sencha.com/img/2016-email-sig/icon-youtube-24x24.png]
<http://www.youtube.com/SenchaInc>

[image: http://cdn.sencha.com/img/2016-email-sig/icon-googleplus-24x24.png]
<https://plus.google.com/117303203295549187007?prsrc=3>

*Winner of the SD Times 100 2015 Award*
<https://www.sencha.com/company/press/sencha-wins-2015-sd-times-100-award-in-user-experience-category/>

-- 
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/CAA_mbNNvdwEatmaHcs2ddpHVniTwQt%2BD%3DV%3DH%2BtEO31XBimcv3A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: It should be registered via or entry in your .gwt.xml ?

[Brandon Donnelson]

Looks like the element is missing from the 
dtd? 
https://gwt.googlesource.com/gwt.git/+/master/distro-source/core/src/gwt-module.dtd

On Wednesday, December 30, 2015 at 4:22:44 PM UTC-8, Thomas Broyer wrote:
>
>
>
> On Thursday, December 31, 2015 at 12:45:11 AM UTC+1, cellepo wrote:
>>
>> It doesn't look like  is a possible Element type in GWT 2.7?
>>
>> I can add , but when I add a ...
>>
>> *The content of element type "module" must match 
>> "(inherits|source|public|super-source|entry-point|stylesheet|*
>>
>> * 
>> script|servlet|replace-with|generate-with|define-property|extend-property|set-property|set-property-fallback|*
>>
>> * 
>> clear-configuration-property|define-configuration-property|extend-configuration-property|set-configuration-*
>>
>> * 
>> property|property-provider|define-linker|add-linker|collapse-all-properties|collapse-property)*".*
>>
>>  
>> Unless I'm missing it, I don't see resource in that list, which seems to 
>> be why I can't add a .  Unless I'm missing something? 
>>
>
> GWT doesn't validate the XML (using a DTD or schema); so this error 
> message doesn't come from GWT.
> …and yes the DTD is out of date. Patch welcome (real "schema" is defined 
> in ModuleDefSchema class)
>  
>
>>
>> On Tuesday, March 24, 2015 at 1:58:01 PM UTC-4, MacWiz wrote:
>>>
>>> Thanks Thomas.  Adding a  fixed these.  I 
>>> thought I had tried that, but apparently not.  As far as the location of 
>>> the images, we are discussing moving them, as you suggest.  They've been in 
>>> our public area since the beginning of our GWT based work many years ago 
>>> (starting with GWT v1.3, I believe.)
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

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

[Brandon Donnelson]

Turns out I imported the wrong JsType. Thanks for the help. 

On Wednesday, December 9, 2015 at 2:13:04 PM UTC-8, Rene Hangstrup Møller 
wrote:
>
> That is the old (and to be deleted) JsType annotation. The 
> jsinterop.annotations.JsType still has isNative as per the spec
>
> Den onsdag den 9. december 2015 kl. 22.59.30 UTC+1 skrev Brandon Donnelson:
>>
>> I noticed that isNative has been removed and exists in the doc. 
>>
>>
>> https://github.com/gwtproject/gwt/commit/d506bec0a55936fb49138e86ad7520e926c76f59
>>
>

-- 
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/7d0c900c-c63b-47db-ac5b-13580f3daa59%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Brandon Donnelson]

I noticed that isNative has been removed and exists in the doc. 

https://github.com/gwtproject/gwt/commit/d506bec0a55936fb49138e86ad7520e926c76f59

-- 
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/41888d3f-231d-46de-9c8e-d7633bc15920%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.8.0-beta1 available for testing

[Brandon Donnelson]

I think you may have two libraries on the classpath. Regarding Eclipse, it
is ready.

Find the download that will work with mars and GWT 2.8.
http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html

On Tue, Dec 8, 2015 at 8:52 AM, Pedro Lamarão <pedro.lama...@gmail.com>
wrote:

> Em sexta-feira, 4 de dezembro de 2015 07:51:13 UTC-2, Daniel Kurka
> escreveu:
>
>
>> Please start testing and let us know about any issues you encounter by
>> either discussion here or filing bugs on github
>> <https://github.com/gwtproject/gwt/issues/new>.
>>
>
>
> Is it ready for use with Google Plugin for Eclipse?
> I added it as a new SDK and retargeted my projects -- in the build path,
> in the compiler path for annotations.
> A build with the GWT compilers ends with:
>
> [ERROR] Unexpected internal compiler error
> java.lang.NoSuchMethodError:
> com.google.gwt.util.tools.shared.Md5Utils.getMd5Digest(Ljava/lang/String;)[B
> at
> com.google.gwt.dev.util.CompilerVersion.getHash(CompilerVersion.java:42)
> at
> com.google.gwt.dev.javac.PersistentUnitCacheDir.(PersistentUnitCacheDir.java:53)
> at
> com.google.gwt.dev.javac.PersistentUnitCache$BackgroundService.(PersistentUnitCache.java:275)
> at
> com.google.gwt.dev.javac.PersistentUnitCache.(PersistentUnitCache.java:104)
> at
> com.google.gwt.dev.javac.UnitCacheSingleton.get(UnitCacheSingleton.java:98)
> at com.google.gwt.dev.Compiler.getOrCreateUnitCache(Compiler.java:89)
> at com.google.gwt.dev.Compiler.run(Compiler.java:183)
> at com.google.gwt.dev.Compiler.run(Compiler.java:156)
> at com.google.gwt.dev.Compiler$1.run(Compiler.java:117)
> at
> com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55)
> at
> com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50)
> at com.google.gwt.dev.Compiler.main(Compiler.java:124)
>
> P.
>
> --
> 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/77dac21c-66d7-43ed-8b50-88f78de5eda7%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/77dac21c-66d7-43ed-8b50-88f78de5eda7%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 

*Brandon Donnelson* / GXT Support Engineer

-- 
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/CAA_mbNNxC%3Dhxr%2BzO_adCT7YgJ-dmOzGyYN7-TXA9mTxuv9cCBA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Will GWT stay ALIVE

[Brandon Donnelson]

Sencha's GXT framework depends on GWT. Since GXT depends on GWT 
commercially they are invested in it's future. 

On Monday, December 7, 2015 at 12:50:42 AM UTC-8, mohammed al-hammouri 
wrote:
>
> I am confused about the future of GWT 
> Will it survive for the next years ?
> Also I see GWT 2.8.0 RC1 is launched but there is no announcement in the 
> official site ... no tutorials how to use new things like JsInterop.
> Is there a references that I can go to where I can find the information I 
> need ? 
> Thanks .. and please provide me will the resources that I can use to be up 
> to date with GWT .
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" 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.

[gwt-contrib] Fix for web app creator template

[Brandon Donnelson]

GWT 2.8.0 patch:

I've added a patch to help with importing the samples or web application 
project into Eclipse after ant eclipse.generate is used in the sample 
generation. Normally Eclipse would use the web app creator to generate the 
project and in so it would add the nature, but in the case of the sample 
creation, it's done by the script so it won't turn on the nature by 
default. This is done in the template, which is modified in the patch. 

Problem:
- running `ant eclipse.generate` on the samples does not create a .project 
file with the GWT nature enabled. 

Solution:
This adds the GWT nature to the Eclipse .project file so importing a GWT 
project will automatically be set up. 
https://gwt-review.googlesource.com/#/c/14032

-- 
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/9c50bf92-f01e-4339-b7eb-81d090cfb4ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] GWT Maven Samples update for GWT 2.8

[Brandon Donnelson]

I updated the Maven samples.

https://gwt-review.googlesource.com/14050


I'm not sure why I had to turn on GSS in the module. Possible I missed 
where it was getting turned off at. Anyway, the patch up above fixes the 
gss errors. By the way if you're wondering why I had to turn on gss 
conversion, it's b/c there is some legacy css in the core. 


-- 
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/9ea6e5fa-dcc7-4329-84b0-8957d95fa993%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Help testing the GWT 2.8 release

[Brandon Donnelson]

Regards to testing, I've added a patch to help with importing the samples 
or web application project into Eclipse. 

Problem:
- running ant eclipse.generate on the samples does not create a .project 
file with the GWT nature enabled. 

Solution:
This adds the GWT nature to the Eclipse .project file so importing a GWT 
project will automatically be set up. 
https://gwt-review.googlesource.com/#/c/14032

Thanks,
Brandon

On Monday, November 2, 2015 at 12:14:07 PM UTC-8, Daniel Kurka wrote:
>
> Hi all,
>
> the GWT team needs help testing the GWT 2.8.1-beta1 release. As always, 
> before we publicize the release we are doing a bunch of DOA (dead on 
> arrival tests) before we open the release to the broader community.
>
> Platforms that need testing:
>
>- Chrome (Linux or mac),
>- Window IE11,
>- Windows IE8
>- Window IE9
>- OSX safari
>- Firefox (Linux or mac)
>
> We should have either chrome on mac and firefox on linux or the other way 
> around.
>
> If you are interested in helping to test the release send me an email and 
> I'll share details with you!
>
> -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/bf8342a4-7583-4f99-9ec7-849bc4d2206f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Help testing the GWT 2.8 release

[Brandon Donnelson]

@stuckagain, contact Colin for getting signed up to test one of the OSes. 

@Petrica it will be GWT 2.8.0-beta1

On Tuesday, November 10, 2015 at 3:40:51 AM UTC-8, Petrică Clement Chiriac 
wrote:
>
> Daniel is GWT 2.8.1-beta1 or GWT 2.8.0-beta1 ?
>
> Thanks,
> Petrica Chiriac
>
>
> On Monday, November 2, 2015 at 10:14:07 PM UTC+2, Daniel Kurka wrote:
>>
>> Hi all,
>>
>> the GWT team needs help testing the GWT 2.8.1-beta1 release. As always, 
>> before we publicize the release we are doing a bunch of DOA (dead on 
>> arrival tests) before we open the release to the broader community.
>>
>> Platforms that need testing:
>>
>>- Chrome (Linux or mac),
>>- Window IE11,
>>- Windows IE8
>>- Window IE9
>>- OSX safari
>>- Firefox (Linux or mac)
>>
>> We should have either chrome on mac and firefox on linux or the other way 
>> around.
>>
>> If you are interested in helping to test the release send me an email and 
>> I'll share details with you!
>>
>> -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/660a0547-38ac-4a84-aca7-201732aeef9b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: GWT Smoke Test Checklist - Invitation to comment

[Brandon Donnelson]

I'll help out starting tomorrow. 

On Monday, November 9, 2015 at 11:40:22 AM UTC-8, Daniel Kurka wrote:
>
> Daniel Kurka  has invited you to *comment on* the following 
> spreadsheet:
> GWT Smoke Test Checklist 
> 
> Open in Sheets 
> 
> Google Sheets: Create and edit spreadsheets online.[image: Logo for 
> Google Sheets] 
>

-- 
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/ee6e9dda-e1ed-4c03-9ad6-6eaa5dc8bad9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Help testing the GWT 2.8 release

[Brandon Donnelson]

I can help, send me the instructions. 

On Monday, November 2, 2015 at 12:14:07 PM UTC-8, Daniel Kurka wrote:
>
> Hi all,
>
> the GWT team needs help testing the GWT 2.8.1-beta1 release. As always, 
> before we publicize the release we are doing a bunch of DOA (dead on 
> arrival tests) before we open the release to the broader community.
>
> Platforms that need testing:
>
>- Chrome (Linux or mac),
>- Window IE11,
>- Windows IE8
>- Window IE9
>- OSX safari
>- Firefox (Linux or mac)
>
> We should have either chrome on mac and firefox on linux or the other way 
> around.
>
> If you are interested in helping to test the release send me an email and 
> I'll share details with you!
>
> -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/c77d2e95-48fc-4cd9-8e3d-883adbe98b5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: GWT Smoke Test Checklist - Invitation to comment

[Brandon Donnelson]

Which JDK should I use?

On Monday, November 9, 2015 at 2:20:37 PM UTC-8, Brandon Donnelson wrote:
>
> I'll help out starting tomorrow. 
>
> On Monday, November 9, 2015 at 11:40:22 AM UTC-8, Daniel Kurka wrote:
>>
>> Daniel Kurka has invited you to *comment on* the following spreadsheet:
>> GWT Smoke Test Checklist 
>> <https://docs.google.com/spreadsheets/d/1DmF8V3fSxN1N2UgQ9zToZz6xCwtx53lOSy8_u1xTC6Q/edit?usp=sharing_eid=5640f6a3>
>> Open in Sheets 
>> <https://docs.google.com/spreadsheets/d/1DmF8V3fSxN1N2UgQ9zToZz6xCwtx53lOSy8_u1xTC6Q/edit?usp=sharing_eid=5640f6a3>
>> Google Sheets: Create and edit spreadsheets online.[image: Logo for 
>> Google Sheets] <https://drive.google.com>
>>
>

-- 
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/8d83449c-c479-4081-b769-ea7a2ca4c3a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Probleme GWT 2.7, Gwtp 1.4 with tomcat

[Brandon Donnelson]

No class found... I think IsSerializable will need to be in some jar that's 
on the server side or in web-inf/lib. 

On Sunday, July 19, 2015 at 2:20:33 AM UTC-7, Ignacio Baca Moreno-Torres 
wrote:

 Try adding gwt-servlet as a server dependency.

 On Sunday, July 19, 2015 at 9:36:19 AM UTC+2, Sabri Hammami wrote:

 my project works with eclipse but did not works with tomcat after 
 compilation !!

 Thanks



-- 
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.

[gwt-contrib] Submit an issue destination on Google Code

[Brandon Donnelson]

Would you like to change the submit an issue link target on Google Code?

https://code.google.com/p/google-web-toolkit/

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/ea1f006d-3a2d-4ed1-88f3-7e5e9bb2fd46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GPE does not like GWT trunk SDK?

[Brandon Donnelson]

The plugin has been forked although it still has the App Engine features. 
Although the Google login isn't working on the GWT plugin for Eclipse at 
the moment. Eventually we should see a Eclipse plugin that only has the 
Google features and the GWT features can live on there own, yet both will 
come together to do the same thing. GPE is closed source, although the fork 
has all of its source plus some more. The Fork is a community version and 
can accept patches where GPE is closed and can not at this time. 

Does that help?

Thanks,
Brandon

On Tuesday, June 30, 2015 at 10:55:10 AM UTC-7, Joel Handwell wrote:

 That means 
 1. Google Plugin for Eclipse will change its name to GWT Eclipse Plugin? 
 (then the name I think does not include features like App Engine SDK)
 or 
 2. Google Plugin for Eclipse will be continued to be closed source, and 
 GWT Eclipse Plugin will be developed as fork independent from GPE?

 On Tuesday, June 30, 2015 at 4:58:06 AM UTC-4, Jens wrote:


 As of 2015 June 29, Eclipse 4.5 is available. Any updates about GPE on 
 github ?


 https://github.com/gwt-plugins/gwt-eclipse-plugin

 This is an open source fork of the original GPE.

 -- 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/1a32a526-5e0a-46b5-af51-d49525565df2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: GWT Meet-up 2015 Videos

[Brandon Donnelson]

Thanks, nice job. 

On Wednesday, June 10, 2015 at 10:39:10 PM UTC-7, Bhaskar Janakiraman wrote:

 For those who missed the G+ post, the talks at the Meet-up are now on the 
 GWT YouTube channel, enjoy!

 https://www.youtube.com/playlist?list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE

 Bhaskar


-- 
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/efd9ec03-ace4-4394-8087-b884b0f754b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: GWT 2.8 js interopt compiler issue

[Brandon Donnelson]

Nevermind, memory had to be increased. 

On Thursday, June 11, 2015 at 8:35:30 AM UTC-7, Brandon Donnelson wrote:

 Would GWT 2.8, Java 1.8 (-sourceLevel 1.8) be able to compile this?

 @JsType(prototype=Window)

 public interface Window {

   static Window window() {

 // returns $wnd;

 return Util.getWindow();

   }


   void alert(String msg);

 }


 Window.window().alert(Does this work?);



 Maybe it's premature to ask this, but the compiler chokes on this with an 
 out of memory error.




 For Reference:

 public class Util {

   public static native Window getWindow() /*-{

  return $wnd;

   }-*/;

 }


-- 
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/99a84822-d845-4bb0-8675-8176b4aa4d33%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] GWT 2.8 js interopt compiler issue

[Brandon Donnelson]

Would GWT 2.8, Java 1.8 (-sourceLevel 1.8) be able to compile this?

@JsType(prototype=Window)

public interface Window {

  static Window window() {

// returns $wnd;

return Util.getWindow();

  }


  void alert(String msg);

}


Window.window().alert(Does this work?);



Maybe it's premature to ask this, but the compiler chokes on this with an 
out of memory error.




For Reference:

public class Util {

  public static native Window getWindow() /*-{

 return $wnd;

  }-*/;

}

-- 
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/8f6046e5-5fe7-4752-8b68-bee339638e5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.7 with Designer

[Brandon Donnelson]

I think it would be better to fix the Designer. 

https://github.com/gwt-eclipse-plugin/gwt-eclipse-plugin/issues/56
https://github.com/gwt-eclipse-plugin/gwt-designer

On Saturday, May 23, 2015 at 10:33:10 AM UTC-7, Lenny Grover wrote:

 Is there any possibility of getting this merged into an official 2.7.1 
 release (like the earlier 2.6.1 release) and into the upcoming 2.8 release? 
  It would be great if we could get GWT Designer support back into the 
 official builds (2.7.1, 2.8, +).

 Thank you very much for your work on this!

 On Monday, May 18, 2015 at 11:04:23 PM UTC-4, atx@gmail.com wrote:

 Merged a commit from 2.6.1, created a few methods overloads, and 
 implemented an interface on a class the designer uses. It was really not 
 too much. For the full details see the top of the README in the repo linked.



-- 
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: Have GWT 2.7.0 SuperDevMode reuse old compile-n files from last run

[Brandon Donnelson]

Eclipse uses the entrypoint, so this wouldn't have anything to do with 
Eclipse. 

On Sunday, May 17, 2015 at 5:01:33 AM UTC-7, salek@googlemail.com wrote:

 Hello,

 I'm using GWT 2.7.0 SuperDevMode and start the codeserver from Eclipse 
 Luna SR2 under Win 8.1, but as plain Java application without using the 
 Eclipse plugin.
 My log starts with these lines on startup all the time:

 Turning off precompile in incremental mode.
 Super Dev Mode starting up
workDir: C:\Users\myuser\workspace\myproj\codeserver
Public resources found in...
Translatable source found in...
 log4j:WARN No appenders could be found for logger 
 (org.eclipse.jetty.util.log).
 log4j:WARN Please initialize the log4j system properly.
Loading Java files in mymodule.
Persistent unit cache dir set to: 
 C:\Users\myuser\workspace\myproj\codeserver\mymodule\compile-1\gwt-unitCache
Looking for previously cached Compilation Units in 
 C:\Users\myuser\workspace\myproj\codeserver\mymodule\compile-1\gwt-unitCache
*Found 0 cached/archived units.  Used 0 / 4872 units from cache.*
Compiling...
   0% complete (ETR: ?)
   10% complete (ETR: 350 seconds)
   20% complete (ETR: 217 seconds)
   30% complete (ETR: 231 seconds)
   40% complete (ETR: 183 seconds)
   50% complete (ETR: 143 seconds)
   60% complete (ETR: 105 seconds)
   70% complete (ETR: 71 seconds)
   80% complete (ETR: 44 seconds)
   90% complete (ETR: 21 seconds)
   100% complete (ETR: 0 seconds)
   Compilation completed in 219,33 seconds
Added 4872 units to cache since last cleanup.


 Is it somehow possible to have the codeserver use the old data from 
 compile-1, compile-2, compile-3... instead of starting with a full 
 compile on startup every time?
 It seems there is no need for this (the incremental compiling after a 
 change works), so I think it should be possible.

 Could this be related to the way Eclipse ends the codeserver (terminates 
 it), so that it can't clean up for the next start?

 My startup parameters are as follows:
 -src src -workDir ${workspace_loc:myproj}/codeserver -port 1234 mymodule 
 -logLevel 
 TRACE -war C:\Users\myuser\workspace\myproj\war -incremental -precompile 
 -workDir 
 C:\Users\myuser\workspace\myproj\codeserver


 Thank you  Best regards
 Salek


-- 
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 2.7 with Designer

[Brandon Donnelson]

What did you have to do to workaround the issue?


On Wednesday, May 13, 2015 at 12:52:15 PM UTC-7, atx@gmail.com wrote:

 https://github.com/bently0602/GWT-2.7

 Here's some patches to support using the eclipse designer with GWT 2.7. It 
 is very hackish so it may not work in every use case or some random bugs 
 may come up. If you want to grab the SDK pre-built see the file 
 gwt-0.0.0.zip from the link.


-- 
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: Trying SDM in gwt 2.5.1 - no option to compile

[Brandon Donnelson]

There are so many issues with SDM in 2.5.x that I recommend upgrading to 
GWT 2.7. It's so much faster, source maps work better and such. Although I 
suspect you've heard that but have some app upgrade constraints. 

On Friday, May 15, 2015 at 4:21:46 PM UTC-7, MG12 wrote:

 I needed to add:

 add-linker name=xsiframe/
 set-configuration-property name=devModeRedirectEnabled value=true/
 set-property name=compiler.useSourceMaps value=true/

 to my gwt.xml



 On Saturday, May 16, 2015 at 1:08:10 AM UTC+2, MG12 wrote:

 Hi

 I'm trying to get setup with SDM. 

 When I view my app, and click on the 'Dev Mode On' book mark, I get the 
 following modal popup:



 https://lh3.googleusercontent.com/-2FOoMn-xi7Y/VVZ7-PAGCpI/Ai8/Jx6h1xB08aI/s1600/Selection_252.png












 Notice there is not option / button to actually choose the module.

 I have checked the html for this popup, and there is also no button - so 
 its not that there is any css hiding elements.

 What would cause this? How can I fix this?

 Thanks



-- 
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 Meetup 2015

[Brandon Donnelson]

Good idea. Is there a Spreadsheet started for talks and sessions? I think
something was floating around last year.

Have a good day,
Brandon Donnelson
+Follow Me https://plus.google.com/u/0/111739836936169749229/posts

On Fri, May 8, 2015 at 4:05 AM, Julien Dramaix julien.dram...@gmail.com
wrote:

 We could also discuss about the website. Several things need to be fixed
 and we could discuss how to reorganize content of the website (old articles
 should be removed for instance)

 On Thu, May 7, 2015 at 3:04 PM Brandon Donnelson branflake2...@gmail.com
 wrote:

 Sounds good, I can whip something up. I'll should have some new docs,
 videos and plugin preview ready to go too.

 Have a good day,
 Brandon Donnelson
 +Follow Me https://plus.google.com/u/0/111739836936169749229/posts

 On Thu, May 7, 2015 at 5:05 AM, Julien Dramaix julien.dram...@gmail.com
 wrote:

 It would be nice to have a status about the Eclipse plugin indeed.  IIRC,
 sessions are recorded so people will be able to watch your session
 afterwards.

 On Thu, May 7, 2015 at 7:34 AM Brandon Donnelson 
 branflake2...@gmail.com wrote:

 If folks are interested I could talk about the Eclipse plugin...
 thoughts?

 --
 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/5b30bfc8-bd86-40b0-8910-b5cd8a72fa3d%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/5b30bfc8-bd86-40b0-8910-b5cd8a72fa3d%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 a topic in the
 Google Groups GWT Contributors group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/google-web-toolkit-contributors/CKG8rWCN5Ok/unsubscribe
 .
 To unsubscribe from this group and all its topics, 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%3D7w8C1y498Da1rWgWstxkRed-Nz0dZn2wFsAu0FNHwxMQ%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D7w8C1y498Da1rWgWstxkRed-Nz0dZn2wFsAu0FNHwxMQ%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/CAPnsdHQNSfHyno0AERchcGn7HGSGb%3DbwVq8DwT3X9jSJLo-ZGA%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAPnsdHQNSfHyno0AERchcGn7HGSGb%3DbwVq8DwT3X9jSJLo-ZGA%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 a topic in the
 Google Groups GWT Contributors group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/google-web-toolkit-contributors/CKG8rWCN5Ok/unsubscribe
 .
 To unsubscribe from this group and all its topics, 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%3D7sauD7RxfE4_YL6Mm4%3D0Jpxz-RM_8jRix30HjHCBGNoA%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D7sauD7RxfE4_YL6Mm4%3D0Jpxz-RM_8jRix30HjHCBGNoA%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/CAPnsdHT2Wd55S0iRCgEuMJAZQm4uqU2yDhWjF7kvjhriBjsbmA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.