Thanks Jens for clarifying that.
/Adrian
Den onsdagen den 26:e november 2014 kl. 17:09:06 UTC+1 skrev Jens:
I just got started with SDM but it seems like one cannot inspect variables
in the java source maps, maybe I missunderstood the whole thing. It's nice
that you can see the java source
I just got started with SDM but it seems like one cannot inspect variables
in the java source maps, maybe I missunderstood the whole thing. It's nice
that you can see the java source and step debug, but I really need to be
able to inspect variables.
For instance I somewhere read that you're
I just got started with SDM but it seems like one cannot inspect variables
in the java source maps, maybe I missunderstood the whole thing. It's nice
that you can see the java source and step debug, but I really need to be
able to inspect variables.
For instance I somewhere read that
Is there any option to debug JS running a browser with sourcemaps in
IntelliJ?
On Friday, February 14, 2014 12:19:46 AM UTC+1, Colin Alworth wrote:
There is a prototype project enabling Eclipse to debug the JS running in
the browser with sourcemaps - check it out at
Yes, there is. Create a running configuration for JavaScript, start the
configuration, install the IntelliJ-Plugin for Chrome... end it works ...
Really nice.
It seems, that FireFox won't work. I opened a ticket at IntelliJ. Hope theq
will fix it soon.
--
You received this message because
There is a prototype project enabling Eclipse to debug the JS running in
the browser with sourcemaps - check it out at http://github.com/sdbg/sdbg.
On Thursday, November 15, 2012 8:46:26 AM UTC-8, Clint Gilbert wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If I could hook Eclipse
The SuperDevMode seem do a full compile as is com.google.gwt.dev.Compiler
with PRETTY style plus sourcemaps generation. It even take longer time than
a normal GWT compiler compilation. Moreover, the unitCache is not always
pickup correctly make the compilation even longer.
On Wednesday,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/14/2012 08:33 PM, Oliver Krylow wrote:
Also the promise of gwt is NOT to abstract the browser or web
technologies and semantics away from you, but rather to bring good
and structured workflow and tooling to web development .
Well, sort of.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If I could hook Eclipse up to Firefox or Chrome and step through code,
that would make SDM much more workable. Is that currently possible?
If so, is it possible to inspect the internal state of an object
defined in Java, compiled to JS, and running
One tip in the chrome dev tools to find a source file is to select the
sources window and just start typing the name of the file. This will take
you to the files that match as you type.
On Wednesday, November 14, 2012 3:24:35 AM UTC-5, Stefan Röck wrote:
In a larger GWT multi project app and
On Thursday, November 15, 2012 5:55:44 PM UTC+1, Paul Stockley wrote:
One tip in the chrome dev tools to find a source file is to select the
sources window and just start typing the name of the file. This will take
you to the files that match as you type.
Or Ctrl+O.
--
You received
In a larger GWT multi project app and it took me several hours to get the
new SuperDevMode running (I found this
videohttp://jeff-davis.blogspot.de/2012/07/setting-up-gwt-25s-superdevmode.htmlvery
helpful).
Now, I'm a bit disappointed about the coolest new feature of 2.5 and I
wonder if I have
I'm facing the same problems as you. But I'm using GIN and GWT-RPC
On Wednesday, November 14, 2012 8:24:35 AM UTC, StefanR wrote:
In a larger GWT multi project app and it took me several hours to get the
new SuperDevMode running (I found this
I understand you pain. Our application is around 150k LOC of client code,
we are using only GWT-RPC, we have big problems with
development productivity and unfortunately SuperDevMode did not bring
anything useful for us.
On Wednesday, November 14, 2012 9:24:35 AM UTC+1, StefanR wrote:
In a
Our project is about 35,000 lines of client and server code. We don't use
RPC or request factory because we have our own RPC mechanism. We do have
quite a lot of UI binder files. Super dev mode recompiles take between 6 to
8 seconds. So it sounds like the generators are your problem. For some
Also facing the same issue.
On Wednesday, November 14, 2012 10:24:35 AM UTC+2, StefanR wrote:
In a larger GWT multi project app and it took me several hours to get the
new SuperDevMode running (I found this
videohttp://jeff-davis.blogspot.de/2012/07/setting-up-gwt-25s-superdevmode.htmlvery
I have about 250kloc, lots of RPC and no generators or UI binder.
With decent hardware, a recompile is about 7-8 seconds. With a 3-4 year old
computer, it was taking about 20 seconds.
Paul
On 14/11/12 14:34, Paul Stockley wrote:
Our project is about 35,000 lines of client and server code. We
It's to sad that if i want to change a small line of code, like css on
uibinder i need to recompile all the project.
Plus JSR 303 Validation annotations aren't compiled in superdev mode i will
put a issue
El miércoles, 14 de noviembre de 2012 02:24:35 UTC-6, StefanR escribió:
In a larger GWT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/14/2012 09:47 AM, Andrew Mackenzie wrote:
IMHO, SuperDev is not the fix for this, and GWT is exploring a
path (Source maps, browser debug, etc) that breaks one of the best
and distinguishing points of GWT.
Agreed. The inability to debug
I am really enjoying SuperDevMode. My desire is to program to the browser,
not to a high-level GWT api. I've build an MVP framework on top of lower
level browser api's, so no UI Binder, no request factory, no GWT widgets.
Compiles are fast. Debugging in Chrome works well. There are some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm glad SDM works for you; the ability to see HTML or CSS changes
quickly is definitely a pro.
But losing the IDE debugger is a big con. No browser debugger that
I'm aware of matches the functionality of Eclipse or IntelliJ. Losing
the ability to
In my opinion, Super Dev Mode is an awesome addition to Dev Mode.
It fits in my workflow:
- For super-fast changes in client-side code (to fine-tune styling etc.), I
use Dev Mode, with a Debugger attached, and a simple button on the page
that rebuilds just the widget I am tuning. Nothing beats
We are also enjoying super death mode as it allows debugging mobile
applications directly on the device . This is a huge time saver and while I
agree that having the debugger not integrated is inconsistent for java devs
but really, after spending 5 minutes with the chrome debugger you will find
On Thursday, November 15, 2012 2:34:12 AM UTC+1, Oliver Krylow wrote:
We are also enjoying super death mode as it allows debugging mobile
applications directly on the device . This is a huge time saver and while I
agree that having the debugger not integrated is inconsistent for java devs
On Thursday, November 15, 2012 1:14:56 AM UTC+1, Chris Lercher wrote:
The only problem I see is, that Super Dev Mode has been officially
described as a replacement for Dev Mode. I don't know, if that's such a
good idea.
With browsers all adding remote debugging support (except IE maybe)
On Thursday, November 15, 2012 2:53:37 AM UTC+1, Thomas Broyer wrote:
SourceMaps could then be used by your IDE so you could put breakpoints in
your editor window.
I can see the potential - it could be big. I do have a few doubts though:
1. Would this also allow me to inspect the internal
26 matches
Mail list logo
