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

[Namline]

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

Google Plugin for Eclipse Mars

[Jim Douglas]

This was working a week or two ago; now it's reporting:

Unable to read repository at https://dl.google.com/eclipse/plugin/4.5.

Unable to read repository at https://dl.google.com/eclipse/plugin/4.5.

No repository found at https://dl.google.com/eclipse/plugin/core/4.5.

https://developers.google.com/eclipse/docs/install-eclipse-4.5

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

Latest version of Elemental2?

[Bruno Salmon]

hi,

I would like to know if the last version of Elemental2 is still 16-06-30 or 
if there is a more recent release.

I'm asking because I'm getting the following compilation error with 
16-06-30 while trying to use the SVG API:

[INFO]Errors in elemental2/SVGSVGElement.java
[INFO]   [ERROR] Line 222: JsProperty setter 'void 
SVGSVGElement.setStyle(Object)' and getter 'String[] 
SVGSVGElement.getStyleAsStringArray()' cannot have inconsistent types.
[INFO]   [ERROR] Line 225: JsProperty setter 'void 
SVGSVGElement.setStyle(Object)' and getter 'CSSStyleDeclaration 
SVGSVGElement.getStyleAsCSSStyleDeclaration()' cannot have inconsistent 
types.
[INFO]Errors in elemental2/SVGStylable.java
[INFO]   [ERROR] Line 46: JsProperty setter 'void 
SVGStylable.setStyle(Object)' and getter 'String[] 
SVGStylable.getStyleAsStringArray()' cannot have inconsistent types.
[INFO]   [ERROR] Line 49: JsProperty setter 'void 
SVGStylable.setStyle(Object)' and getter 'CSSStyleDeclaration 
SVGStylable.getStyleAsCSSStyleDeclaration()' cannot have inconsistent types.

Thanks

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

[Thomas Broyer]

Maybe try out the new GWT Eclipse Plugin, which (AFAICT) bundles everything 
together: 
http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/debugging/Debugging.html

On Monday, October 17, 2016 at 12:48:38 AM UTC+2, Namline wrote:
>
> Jens,
>
> Actually, I took your advice and managed to set break points in Chrome's 
> Developer tool (in Source tab, under sourcemap folder where the Java 
> classes are) and debug from there (not that anything made sense with all 
> the generated JavaScripts).
>
> I also tried SDBG which more or less does the same thing but in the 
> Eclipse as a plugin. I just followed the video on SDBG site 
> and got it to work. What was confusing about it 
> was to run debugging in SuperDevMode first, then rerun the Eclipse Debug 
> As, but this time Launch Chrome from Debug Configuration. It actually 
> spawns two (2) debugging sessions from the looks of it: one for Web 
> Application (code server) and the other for Launch Chrome. Thanks for the 
> recommendation.
>
>
> On Sunday, October 16, 2016 at 3:46:59 PM UTC-4, Jens wrote:
>>
>> SuperDevMode compiles your Java source transparently to JavaScript, it 
>> never executes your Java source code directly in a JVM. So Java break 
>> points in your GWT app will never work.
>>
>> That means with SuperDevMode you can only debug your code using the 
>> browser, as thats the one who actually executes the final JS code. You can 
>> either set break points in your browsers dev tools or install the Eclipse 
>> plugin "SDBG" which allows you to set break points in your IDE which are 
>> then synchronized to the browser.
>>
>> -- 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.