Re: source maps unreliable in 2.7.0

[jaga]

On stable Chrome versions I couldn't inspect the variable values. How do you do 
it? When I attempt to evaluate a variable it just gives an error. Unfortunately 
Canary is the only way I had of viewing the values at runtime which is a good 
enough reason to use it. I don't know how to use conditional JavaScript 
breakpoints.  Perhaps some documentation would help? 

-- 
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: source maps unreliable in 2.7.0

[Jens]

I am not aware of any way to tell Chrome to try requesting source maps 
again beside reloading the page. Honestly I would never use Chrome Canary 
for development since you never know if Chrome misbehaves or not.

I am fine with Chrome 39 and Chrome 40 beta. Never had a problem with 
source maps not being downloaded.

Also I don't really had a problem with debugging. You can see the current 
scopes variable values in Chrome, set watch expressions and conditional 
breakpoints. This also works within IntelliJ (and probably in Eclipse using 
SDBG), although you always must keep in mind that you are debugging 
JavaScript. So conditional breakpoints need JavaScript expressions and 
variable names are JavaScript variable names since they are not mapped 
using source maps (the source map spec does not define this yet).

-- J.

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

Re: Source Maps suddenly don't show java source

[Richard Wallis]

Got sourcemaps working on Chromium.  Still doesn't work on Chrome but it
solves the problem.

On Wed, Dec 10, 2014 at 1:35 PM, Richard Wallis  wrote:

> Reverting to 2.6.1 and using the old Dev Mode On bookmarklet works.
>
> Anyone have an idea of what I'm doing wrong?
>
> On Wed, Dec 10, 2014 at 12:07 PM, Richard Wallis 
> wrote:
>
>> @Jens I tracked down the sourcemap.json file and I can manually add it in
>> Chrome Source tab and then source maps will work until the recompile causes
>> the hash to change.
>>
>> Any idea what could be causing Chrome not to autoload the maps?
>>
>> On Wed, Dec 10, 2014 at 11:31 AM, Richard Wallis 
>> wrote:
>>
>>> Just an update.  Problem occurs with Chromium too.
>>>
>>> On Wed, Dec 10, 2014 at 11:15 AM, Richard Wallis 
>>> wrote:
>>>
 Thanks Jens, I've checked multiple times that Source Maps is enabled.

 The problem occurs in multiple unrelated gwt projects.  It occurs on
 chrome dev and chrome stable channel and it occurs after deleting Chrome's
 UserData dir so I'm using a completely clean version of Chrome.

 I'll try any ideas no matter how stupid, this has completely halted all
 my projects.

 On Wed, Dec 10, 2014 at 11:03 AM, Jens 
 wrote:

> If the CodeServer does not show the log output:
>
> GET /sourcemaps/app/4EA51AEEB40A4AB0358CAE52B6668036_sourcemap.json
>sent source map for module 'app' in 257 ms
>
> Then Chrome probably did not ask for source maps. Maybe you
> accidentally disabled JS source map support in Chrome Dev Tool settings.
>
> -- J.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google Web Toolkit" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit/dE8b875dXEU/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-web-toolkit@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>


>>>
>>
>

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

Re: Source Maps suddenly don't show java source

[Richard Wallis]

Reverting to 2.6.1 and using the old Dev Mode On bookmarklet works.

Anyone have an idea of what I'm doing wrong?

On Wed, Dec 10, 2014 at 12:07 PM, Richard Wallis  wrote:

> @Jens I tracked down the sourcemap.json file and I can manually add it in
> Chrome Source tab and then source maps will work until the recompile causes
> the hash to change.
>
> Any idea what could be causing Chrome not to autoload the maps?
>
> On Wed, Dec 10, 2014 at 11:31 AM, Richard Wallis 
> wrote:
>
>> Just an update.  Problem occurs with Chromium too.
>>
>> On Wed, Dec 10, 2014 at 11:15 AM, Richard Wallis 
>> wrote:
>>
>>> Thanks Jens, I've checked multiple times that Source Maps is enabled.
>>>
>>> The problem occurs in multiple unrelated gwt projects.  It occurs on
>>> chrome dev and chrome stable channel and it occurs after deleting Chrome's
>>> UserData dir so I'm using a completely clean version of Chrome.
>>>
>>> I'll try any ideas no matter how stupid, this has completely halted all
>>> my projects.
>>>
>>> On Wed, Dec 10, 2014 at 11:03 AM, Jens  wrote:
>>>
 If the CodeServer does not show the log output:

 GET /sourcemaps/app/4EA51AEEB40A4AB0358CAE52B6668036_sourcemap.json
sent source map for module 'app' in 257 ms

 Then Chrome probably did not ask for source maps. Maybe you
 accidentally disabled JS source map support in Chrome Dev Tool settings.

 -- J.

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

>>>
>>>
>>
>

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

Re: Source Maps suddenly don't show java source

[Richard Wallis]

@Jens I tracked down the sourcemap.json file and I can manually add it in
Chrome Source tab and then source maps will work until the recompile causes
the hash to change.

Any idea what could be causing Chrome not to autoload the maps?

On Wed, Dec 10, 2014 at 11:31 AM, Richard Wallis  wrote:

> Just an update.  Problem occurs with Chromium too.
>
> On Wed, Dec 10, 2014 at 11:15 AM, Richard Wallis 
> wrote:
>
>> Thanks Jens, I've checked multiple times that Source Maps is enabled.
>>
>> The problem occurs in multiple unrelated gwt projects.  It occurs on
>> chrome dev and chrome stable channel and it occurs after deleting Chrome's
>> UserData dir so I'm using a completely clean version of Chrome.
>>
>> I'll try any ideas no matter how stupid, this has completely halted all
>> my projects.
>>
>> On Wed, Dec 10, 2014 at 11:03 AM, Jens  wrote:
>>
>>> If the CodeServer does not show the log output:
>>>
>>> GET /sourcemaps/app/4EA51AEEB40A4AB0358CAE52B6668036_sourcemap.json
>>>sent source map for module 'app' in 257 ms
>>>
>>> Then Chrome probably did not ask for source maps. Maybe you accidentally
>>> disabled JS source map support in Chrome Dev Tool settings.
>>>
>>> -- J.
>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Google Web Toolkit" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/google-web-toolkit/dE8b875dXEU/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to
>>> google-web-toolkit+unsubscr...@googlegroups.com.
>>> To post to this group, send email to google-web-toolkit@googlegroups.com
>>> .
>>> Visit this group at http://groups.google.com/group/google-web-toolkit.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>

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

Re: Source Maps suddenly don't show java source

[Richard Wallis]

Just an update.  Problem occurs with Chromium too.

On Wed, Dec 10, 2014 at 11:15 AM, Richard Wallis  wrote:

> Thanks Jens, I've checked multiple times that Source Maps is enabled.
>
> The problem occurs in multiple unrelated gwt projects.  It occurs on
> chrome dev and chrome stable channel and it occurs after deleting Chrome's
> UserData dir so I'm using a completely clean version of Chrome.
>
> I'll try any ideas no matter how stupid, this has completely halted all my
> projects.
>
> On Wed, Dec 10, 2014 at 11:03 AM, Jens  wrote:
>
>> If the CodeServer does not show the log output:
>>
>> GET /sourcemaps/app/4EA51AEEB40A4AB0358CAE52B6668036_sourcemap.json
>>sent source map for module 'app' in 257 ms
>>
>> Then Chrome probably did not ask for source maps. Maybe you accidentally
>> disabled JS source map support in Chrome Dev Tool settings.
>>
>> -- J.
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Google Web Toolkit" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/google-web-toolkit/dE8b875dXEU/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> google-web-toolkit+unsubscr...@googlegroups.com.
>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>> Visit this group at http://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

Re: Source Maps suddenly don't show java source

[Richard Wallis]

Thanks Jens, I've checked multiple times that Source Maps is enabled.

The problem occurs in multiple unrelated gwt projects.  It occurs on chrome
dev and chrome stable channel and it occurs after deleting Chrome's
UserData dir so I'm using a completely clean version of Chrome.

I'll try any ideas no matter how stupid, this has completely halted all my
projects.

On Wed, Dec 10, 2014 at 11:03 AM, Jens  wrote:

> If the CodeServer does not show the log output:
>
> GET /sourcemaps/app/4EA51AEEB40A4AB0358CAE52B6668036_sourcemap.json
>sent source map for module 'app' in 257 ms
>
> Then Chrome probably did not ask for source maps. Maybe you accidentally
> disabled JS source map support in Chrome Dev Tool settings.
>
> -- J.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google Web Toolkit" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit/dE8b875dXEU/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Source Maps suddenly don't show java source

[Jens]

If the CodeServer does not show the log output:

GET /sourcemaps/app/4EA51AEEB40A4AB0358CAE52B6668036_sourcemap.json
   sent source map for module 'app' in 257 ms

Then Chrome probably did not ask for source maps. Maybe you accidentally 
disabled JS source map support in Chrome Dev Tool settings.

-- J.

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

Re: Source maps

[Juan Pablo Gardella]

:) Good news. Alan will be happy

2012/7/31 Joseph Lust 

> FYI, Source Map support is now in Mozilla Firefox nightly builds! Soon
> Alan's life will be much easier. Read more details 
> here
> .
>
>
> Sincerely,
> Joseph
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-web-toolkit/-/dE1u0iD0_LsJ.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Source maps

[Joseph Lust]

FYI, Source Map support is now in Mozilla Firefox nightly builds! Soon 
Alan's life will be much easier. Read more details 
here
.


Sincerely,
Joseph

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/dE1u0iD0_LsJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Source maps

[Thomas Broyer]

On Monday, April 2, 2012 10:17:15 AM UTC+2, Honza Rames wrote:
>
> Thanks cool, this way it works just fine, I also had to symlink my java 
> sources so the browser could access them, you can do this by creating a 
> symlink to you com (org or whatever package you use as base) in you 
> war/ folder (where the cache.htmls are generated and where 
> you copy source maps to). It would probably be a lot better to have a 
> servlet that can handle fetching the sources and also a modified linker 
> that adds the sourceMappingURL to the generated JS (I guess this gets 
> more complicated when code splitting is in play).
>
>
According to 
http://code.google.com/p/google-web-toolkit/source/detail?r=10760 only 
the xsiframe linker () will output the //@ 
sourceUrl=…
It's also only used for stack-trace deobfuscation (as is said on the wiki 
page), which is why it doesn't Just Work™ with Chrome's Developer Tools' 
support for Source Maps (no //@ sourceMappingURL=…, and the generated 
artifacts are not publicly accessible)
It also won't work if you use the experimental Closure Compiler backend.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/98YPPJoosJQJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Source maps

[Honza Rameš]

Thanks cool, this way it works just fine, I also had to symlink my java
sources so the browser could access them, you can do this by creating a
symlink to you com (org or whatever package you use as base) in you
war/ folder (where the cache.htmls are generated and where
you copy source maps to). It would probably be a lot better to have a
servlet that can handle fetching the sources and also a modified linker
that adds the sourceMappingURL to the generated JS (I guess this gets more
complicated when code splitting is in play).

Honza

On Mon, Apr 2, 2012 at 09:27, Dan Cojocar  wrote:

> Yes, some bits are still missing, but using trunk and following the
> instructions from here:
> http://code.google.com/p/google-web-toolkit/wiki/SourceMaps (with few
> additional steps, mentioned in the comments) I was able to debug the Mail
> application, using the java sources in Development tools.
>
> On Mon, Apr 2, 2012 at 9:45 AM, Honza Rameš  wrote:
>
>> Yep, I'm using trunk but I'm not sure that the source map support is
>> fully functional even in trunk though it gets generated. I tried both
>> canary and dev channels of Chrome (I think even Googlers won't use anything
>> special since canary is almost daily build but we cannot be sure ;-) )
>>
>> Honza
>>
>>
>> On Sun, Apr 1, 2012 at 18:34, Gal Dolber  wrote:
>>
>>> oh, my mistake, it seems SourceMap is there.. are you using trunk?
>>>
>>>
>>> On Sun, Apr 1, 2012 at 12:31 PM, Gal Dolber wrote:
>>>
 got exited for a minute... its not there yet, I'm checking out trunk
 everyday hoping to see SuperDraftMode and SourceMap commited


 On Sun, Apr 1, 2012 at 7:20 AM, Andrea Boscolo wrote:

> Are you sure the whole machinery is already available in the public
> (trunk) repo? I thought it's not.
>
> https://plus.google.com/u/1/110412141990454266397/posts/Nvr6Se6eAPh
>
>
> On Sunday, April 1, 2012 12:16:05 PM UTC+2, Honza Rames wrote:
>>
>> Hi everyone,
>> I tried to compile my GWT app with source maps support (as explained
>> here http://stackoverflow.com/**questions/9804492/how-to-try-**
>> sourcemaps-with-gwt)
>> and it failed at first (some json stuff was missing) so I added it to my
>> project's class path then it compiled OK and I can see the source maps
>> generated in WEB-INF/deploy//**symbolMaps. I should also
>> note that I'm using custom build of GWT from trunk. I enabled source maps
>> support in Chrome's Developer tools setting panel but I the source maps
>> doesn't seem to work. I'm launching the app through jetty but not in dev
>> mode (obviously ;-) ) I compiled the project in obfuscated mode as 
>> standard
>> compile (no draft or anything like that). Do I have to use another 
>> version
>> of Chrome? Does anyone tried this as well and succeeded?
>>
>> Honza
>>
>  --
> You received this message because you are subscribed to the Google
> Groups "Google Web Toolkit" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-web-toolkit/-/hcGUk2-d124J.
>
> To post to this group, send email to
> google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>



 --
 Guit: Elegant, beautiful, modular and *production ready* gwt
 applications.

 http://code.google.com/p/guit/





>>>
>>>
>>> --
>>> Guit: Elegant, beautiful, modular and *production ready* gwt
>>> applications.
>>>
>>> http://code.google.com/p/guit/
>>>
>>>
>>>
>>>
>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "Google Web Toolkit" group.
>>> To post to this group, send email to google-web-toolkit@googlegroups.com
>>> .
>>> To unsubscribe from this group, send email to
>>> google-web-toolkit+unsubscr...@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/google-web-toolkit?hl=en.
>>>
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Google Web Toolkit" group.
>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-web-toolkit+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-web-toolkit?hl=en.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://grou

Re: Source maps

[Dan Cojocar]

Yes, some bits are still missing, but using trunk and following the
instructions from here:
http://code.google.com/p/google-web-toolkit/wiki/SourceMaps (with few
additional steps, mentioned in the comments) I was able to debug the Mail
application, using the java sources in Development tools.

On Mon, Apr 2, 2012 at 9:45 AM, Honza Rameš  wrote:

> Yep, I'm using trunk but I'm not sure that the source map support is fully
> functional even in trunk though it gets generated. I tried both canary and
> dev channels of Chrome (I think even Googlers won't use anything special
> since canary is almost daily build but we cannot be sure ;-) )
>
> Honza
>
>
> On Sun, Apr 1, 2012 at 18:34, Gal Dolber  wrote:
>
>> oh, my mistake, it seems SourceMap is there.. are you using trunk?
>>
>>
>> On Sun, Apr 1, 2012 at 12:31 PM, Gal Dolber  wrote:
>>
>>> got exited for a minute... its not there yet, I'm checking out trunk
>>> everyday hoping to see SuperDraftMode and SourceMap commited
>>>
>>>
>>> On Sun, Apr 1, 2012 at 7:20 AM, Andrea Boscolo wrote:
>>>
 Are you sure the whole machinery is already available in the public
 (trunk) repo? I thought it's not.

 https://plus.google.com/u/1/110412141990454266397/posts/Nvr6Se6eAPh


 On Sunday, April 1, 2012 12:16:05 PM UTC+2, Honza Rames wrote:
>
> Hi everyone,
> I tried to compile my GWT app with source maps support (as explained
> here http://stackoverflow.com/**questions/9804492/how-to-try-**
> sourcemaps-with-gwt)
> and it failed at first (some json stuff was missing) so I added it to my
> project's class path then it compiled OK and I can see the source maps
> generated in WEB-INF/deploy//**symbolMaps. I should also
> note that I'm using custom build of GWT from trunk. I enabled source maps
> support in Chrome's Developer tools setting panel but I the source maps
> doesn't seem to work. I'm launching the app through jetty but not in dev
> mode (obviously ;-) ) I compiled the project in obfuscated mode as 
> standard
> compile (no draft or anything like that). Do I have to use another version
> of Chrome? Does anyone tried this as well and succeeded?
>
> Honza
>
  --
 You received this message because you are subscribed to the Google
 Groups "Google Web Toolkit" group.
 To view this discussion on the web visit
 https://groups.google.com/d/msg/google-web-toolkit/-/hcGUk2-d124J.

 To post to this group, send email to
 google-web-toolkit@googlegroups.com.
 To unsubscribe from this group, send email to
 google-web-toolkit+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/google-web-toolkit?hl=en.

>>>
>>>
>>>
>>> --
>>> Guit: Elegant, beautiful, modular and *production ready* gwt
>>> applications.
>>>
>>> http://code.google.com/p/guit/
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Guit: Elegant, beautiful, modular and *production ready* gwt applications.
>>
>> http://code.google.com/p/guit/
>>
>>
>>
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Google Web Toolkit" group.
>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-web-toolkit+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-web-toolkit?hl=en.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Source maps

[Honza Rameš]

Yep, I'm using trunk but I'm not sure that the source map support is fully
functional even in trunk though it gets generated. I tried both canary and
dev channels of Chrome (I think even Googlers won't use anything special
since canary is almost daily build but we cannot be sure ;-) )

Honza

On Sun, Apr 1, 2012 at 18:34, Gal Dolber  wrote:

> oh, my mistake, it seems SourceMap is there.. are you using trunk?
>
>
> On Sun, Apr 1, 2012 at 12:31 PM, Gal Dolber  wrote:
>
>> got exited for a minute... its not there yet, I'm checking out trunk
>> everyday hoping to see SuperDraftMode and SourceMap commited
>>
>>
>> On Sun, Apr 1, 2012 at 7:20 AM, Andrea Boscolo wrote:
>>
>>> Are you sure the whole machinery is already available in the public
>>> (trunk) repo? I thought it's not.
>>>
>>> https://plus.google.com/u/1/110412141990454266397/posts/Nvr6Se6eAPh
>>>
>>>
>>> On Sunday, April 1, 2012 12:16:05 PM UTC+2, Honza Rames wrote:

 Hi everyone,
 I tried to compile my GWT app with source maps support (as explained
 here http://stackoverflow.com/**questions/9804492/how-to-try-**
 sourcemaps-with-gwt)
 and it failed at first (some json stuff was missing) so I added it to my
 project's class path then it compiled OK and I can see the source maps
 generated in WEB-INF/deploy//**symbolMaps. I should also note
 that I'm using custom build of GWT from trunk. I enabled source maps
 support in Chrome's Developer tools setting panel but I the source maps
 doesn't seem to work. I'm launching the app through jetty but not in dev
 mode (obviously ;-) ) I compiled the project in obfuscated mode as standard
 compile (no draft or anything like that). Do I have to use another version
 of Chrome? Does anyone tried this as well and succeeded?

 Honza

>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "Google Web Toolkit" group.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msg/google-web-toolkit/-/hcGUk2-d124J.
>>>
>>> To post to this group, send email to google-web-toolkit@googlegroups.com
>>> .
>>> To unsubscribe from this group, send email to
>>> google-web-toolkit+unsubscr...@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/google-web-toolkit?hl=en.
>>>
>>
>>
>>
>> --
>> Guit: Elegant, beautiful, modular and *production ready* gwt applications.
>>
>> http://code.google.com/p/guit/
>>
>>
>>
>>
>>
>
>
> --
> Guit: Elegant, beautiful, modular and *production ready* gwt applications.
>
> http://code.google.com/p/guit/
>
>
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Source maps

[Gal Dolber]

oh, my mistake, it seems SourceMap is there.. are you using trunk?

On Sun, Apr 1, 2012 at 12:31 PM, Gal Dolber  wrote:

> got exited for a minute... its not there yet, I'm checking out trunk
> everyday hoping to see SuperDraftMode and SourceMap commited
>
>
> On Sun, Apr 1, 2012 at 7:20 AM, Andrea Boscolo wrote:
>
>> Are you sure the whole machinery is already available in the public
>> (trunk) repo? I thought it's not.
>>
>> https://plus.google.com/u/1/110412141990454266397/posts/Nvr6Se6eAPh
>>
>>
>> On Sunday, April 1, 2012 12:16:05 PM UTC+2, Honza Rames wrote:
>>>
>>> Hi everyone,
>>> I tried to compile my GWT app with source maps support (as explained
>>> here http://stackoverflow.com/**questions/9804492/how-to-try-**
>>> sourcemaps-with-gwt)
>>> and it failed at first (some json stuff was missing) so I added it to my
>>> project's class path then it compiled OK and I can see the source maps
>>> generated in WEB-INF/deploy//**symbolMaps. I should also note
>>> that I'm using custom build of GWT from trunk. I enabled source maps
>>> support in Chrome's Developer tools setting panel but I the source maps
>>> doesn't seem to work. I'm launching the app through jetty but not in dev
>>> mode (obviously ;-) ) I compiled the project in obfuscated mode as standard
>>> compile (no draft or anything like that). Do I have to use another version
>>> of Chrome? Does anyone tried this as well and succeeded?
>>>
>>> Honza
>>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Google Web Toolkit" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/google-web-toolkit/-/hcGUk2-d124J.
>>
>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-web-toolkit+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-web-toolkit?hl=en.
>>
>
>
>
> --
> Guit: Elegant, beautiful, modular and *production ready* gwt applications.
>
> http://code.google.com/p/guit/
>
>
>
>
>


-- 
Guit: Elegant, beautiful, modular and *production ready* gwt applications.

http://code.google.com/p/guit/

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Source maps

[Gal Dolber]

got exited for a minute... its not there yet, I'm checking out trunk
everyday hoping to see SuperDraftMode and SourceMap commited

On Sun, Apr 1, 2012 at 7:20 AM, Andrea Boscolo  wrote:

> Are you sure the whole machinery is already available in the public
> (trunk) repo? I thought it's not.
>
> https://plus.google.com/u/1/110412141990454266397/posts/Nvr6Se6eAPh
>
>
> On Sunday, April 1, 2012 12:16:05 PM UTC+2, Honza Rames wrote:
>>
>> Hi everyone,
>> I tried to compile my GWT app with source maps support (as explained here
>> http://stackoverflow.com/**questions/9804492/how-to-try-**
>> sourcemaps-with-gwt)
>> and it failed at first (some json stuff was missing) so I added it to my
>> project's class path then it compiled OK and I can see the source maps
>> generated in WEB-INF/deploy//**symbolMaps. I should also note
>> that I'm using custom build of GWT from trunk. I enabled source maps
>> support in Chrome's Developer tools setting panel but I the source maps
>> doesn't seem to work. I'm launching the app through jetty but not in dev
>> mode (obviously ;-) ) I compiled the project in obfuscated mode as standard
>> compile (no draft or anything like that). Do I have to use another version
>> of Chrome? Does anyone tried this as well and succeeded?
>>
>> Honza
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-web-toolkit/-/hcGUk2-d124J.
>
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>



-- 
Guit: Elegant, beautiful, modular and *production ready* gwt applications.

http://code.google.com/p/guit/

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Source maps

[Andrea Boscolo]

Are you sure the whole machinery is already available in the public (trunk) 
repo? I thought it's not.

https://plus.google.com/u/1/110412141990454266397/posts/Nvr6Se6eAPh

On Sunday, April 1, 2012 12:16:05 PM UTC+2, Honza Rames wrote:
>
> Hi everyone,
> I tried to compile my GWT app with source maps support (as explained here 
> http://stackoverflow.com/questions/9804492/how-to-try-sourcemaps-with-gwt) 
> and it failed at first (some json stuff was missing) so I added it to my 
> project's class path then it compiled OK and I can see the source maps 
> generated in WEB-INF/deploy//symbolMaps. I should also note 
> that I'm using custom build of GWT from trunk. I enabled source maps 
> support in Chrome's Developer tools setting panel but I the source maps 
> doesn't seem to work. I'm launching the app through jetty but not in dev 
> mode (obviously ;-) ) I compiled the project in obfuscated mode as standard 
> compile (no draft or anything like that). Do I have to use another version 
> of Chrome? Does anyone tried this as well and succeeded?
>
> Honza
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/hcGUk2-d124J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.