On Wednesday, May 21, 2014 9:07:41 PM UTC+2, Sergey Shpikin wrote:
>
> Super dev mode is obviously *worse* than the classic dev mode.
>

Yes… and no.
 

> You can't debug your app transparently, both client and server in Eclipse, 
> trace it, watch the vars etc.
>

Have you tried SDBG? (I haven't)
http://sdbg.github.io/
Currently a bit limited (but also limited by SourceMaps and browsers 
(Chrome)) but at least you can set breakpoints from Eclipse to trace the 
execution of your code.
 

> Basically, super dev mode is a fast crutch which doesn't help to debug at 
> all. I can just dump vars using console.log as well. It's inferior and 
> shouldn't be called super.
>

You're missing the fact that it works in virtually every browser that GWT 
runs in, and that includes mobile browsers!
 

> I don't know how to develop on GWT further since devs abandoned it as it 
> seems.
>

What makes you say that?!
Have you looked at the pending reviews and commit log?

Now they suggest debugging the raw JS code with workarounds like sourcemaps.
>

Like everyone else using a language compiled to JS BTW (except Dart because 
they have the resources to build and maintain a fork of Chromium with the 
Dart engine embedded).
 

> The whole point of GWT is that developer shouldn't know JS to create apps,
>

That's a wrong assumption.
The whole point of GWT is that you can a) reuse well-tried tools, b) 
benefit from static-typing and c) reuse your code in other environments 
(server-side Java, Android app, iOS app through J2ObjC).
Nowhere in http://www.gwtproject.org/overview.html 
or http://www.gwtproject.org/makinggwtbetter.html does it say you don't 
have to know JS. It says you don't have to be an expert, but that doesn't 
mean you don't have to know it.
 

> all those tools were not perfect but they did their job. Now it all have 
> been cancelled and not replaced (SDM isn't a replacement, it's highly 
> experimental as they state). This NIH (NPAPI ⇒ PPAPI) reminds me of 
> Microsoft. Ok, I understand that there are security reasons but at least 
> don't abandon your own software!
>

Tell that to the Chrome team, not GWT. Developers inside Google also suffer 
from that decision.
Also, please keep in mind that GWT is not a Google project (not anymore, 
for nearly 2 years now). Google chairs at the Steering Committee and still 
contributes 90% of the code, but they're on par with JBoss, Vaadin, Sencha, 
ArcBees, etc.

…but also remember that Apple were the first to break DevMode in Safari 
5.1, then Mozilla in Firefox last December; and that wasn't even about 
removing NPAPI support.
DevMode is and has always been brittle, but still was better than 
HostedMode, and now seems to be the time to replace it.
 

> I hope they'll port it to PPAPI
>

As said numerous times before: this is not possible.
 

> or make SDM working like the classic devmode, with variables inspection, 
> tracing, breakpoints
>

Ask browser vendors to make SourceMaps better. Some of this can be done by 
third-party tools (breakpoints already work in Eclipse with SDBG, and I 
think in IntelliJ IDEA too), but not everything.
 

> and all of it perfectly integrated with Eclipse. I'm really frustrated by 
> these fast groundbreaking changes.
>

Like all of us, but we have no power to drive/change browser vendors plans.
 

> BTW, at least Iceweasel in Debian doesn't support the plugin anymore, 
> tried several versions (24, 29, 30), the plugin isn't recognized just like 
> in Chrome, though it still can be configured. I guess my best choice would 
> be installing Chromium 34,  and developing on it. Fortunately, Debian 
> snapshot provides all older versions.
>

Some people had issues with Chrome 34, so maybe better try 33.
Or you can download Firefox 24 from Mozilla. 

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to