Re: [gwt-contrib] Website documentation question

[Nicolas Weeger]

Thanks for the information.


I'll use the same syntax then, to be coherent.


I've mostly written about linkers, for now, other patches are minor so it 
should be trivial to merge.



Kind regards


Nicolas


Le vendredi 5 décembre 2014 22:47:03, Julien Dramaix a écrit :
> I have a big patch (done by Jason Lemay from Arcbees by the way) that I
> have to push for review converting every files using markdown syntax.
> And indeed we use html syntax for the header:
> ## Related frameworks
> 
> I will push this change in a few weeks but if you want to propose a patch
> for anything else don't hesitate to do it. I have to rebase my patch
> anyway.
> 
> Julien
> 
> On Fri Dec 05 2014 at 10:32:37 PM Nicolas Weeger  wrote:
> > Hello.
> > 
> > 
> > I've been poking around the documentation (patches ready, waiting for
> > CLA- related tasks to be finished :)), and I got a question about the
> > format to use.
> > 
> > 
> > Right now, pages are mostly HTML, split in .md files, with a Markdown
> > processor
> > converting.
> > 
> > 
> > So I guess the goal is to migrate to Markdown (the Pegdown variant at
> > least),
> > at least step by step or for new documentation?
> > 
> > 
> > One downside, though, is that unless I'm mistaking, Markdown doesn't
> > offer any
> > option to set IDs on elements, like headers, or names on anchors.
> > 
> > 
> > So should headers/linkable items be still put in HTML? Or should we use a
> > workaround to insert a  in the header?
> > 
> > 
> > 
> > Kind regards
> > 
> > 
> > Nicolas
> > 
> > --
> > 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/ms
> > gid/google-web-toolkit-contributors/201412052030.16089.nicolas%40nekoko.f
> > r .
> > For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: This is a digitally signed message part.

Re: [gwt-contrib] Website documentation question

[Julien Dramaix]

I have a big patch (done by Jason Lemay from Arcbees by the way) that I
have to push for review converting every files using markdown syntax.
And indeed we use html syntax for the header:
## Related frameworks

I will push this change in a few weeks but if you want to propose a patch
for anything else don't hesitate to do it. I have to rebase my patch anyway.

Julien



On Fri Dec 05 2014 at 10:32:37 PM Nicolas Weeger  wrote:

> Hello.
>
>
> I've been poking around the documentation (patches ready, waiting for CLA-
> related tasks to be finished :)), and I got a question about the format to
> use.
>
>
> Right now, pages are mostly HTML, split in .md files, with a Markdown
> processor
> converting.
>
>
> So I guess the goal is to migrate to Markdown (the Pegdown variant at
> least),
> at least step by step or for new documentation?
>
>
> One downside, though, is that unless I'm mistaking, Markdown doesn't offer
> any
> option to set IDs on elements, like headers, or names on anchors.
>
>
> So should headers/linkable items be still put in HTML? Or should we use a
> workaround to insert a  in the header?
>
>
>
> Kind regards
>
>
> Nicolas
>
> --
> 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/ms
> gid/google-web-toolkit-contributors/201412052030.16089.nicolas%40nekoko.fr
> .
> 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/CABb_3%3D5BZstbFPO-wyo9c3Y_1AUtREb%2B0%2B8-UufK1R4BS3SnRA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Website documentation question

[Nicolas Weeger]

Hello.


I've been poking around the documentation (patches ready, waiting for CLA-
related tasks to be finished :)), and I got a question about the format to use.


Right now, pages are mostly HTML, split in .md files, with a Markdown processor 
converting.


So I guess the goal is to migrate to Markdown (the Pegdown variant at least), 
at least step by step or for new documentation?


One downside, though, is that unless I'm mistaking, Markdown doesn't offer any 
option to set IDs on elements, like headers, or names on anchors.


So should headers/linkable items be still put in HTML? Or should we use a 
workaround to insert a  in the header?



Kind regards


Nicolas

-- 
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/201412052030.16089.nicolas%40nekoko.fr.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: This is a digitally signed message part.

Re: [gwt-contrib] SuperDevMode sometimes puts member fields in __proto__ why is that ?

['Roberto Lublinerman' via GWT Contributors]

Yes,I meant (instance) final fields of primitive or string type initialized
at declaration.

Compile time constants are propagated by the compiler in draft and
optimized mode.



On Fri, Dec 5, 2014 at 8:49 AM, 'Ray Cromwell' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> Static final fields on the prototype? I'm pretty sure these are
> promoted to global in optimized mode. Perhaps you meant final
> non-static fields? (which we should have an optimization for promoting
> to static :) )
>
>
> On Fri, Dec 5, 2014 at 7:29 AM, 'Roberto Lublinerman' via GWT
> Contributors  wrote:
> > In draft compile Java compile time constants are emitted in the
> prototype.
> > This should be exactly static final fields of primitive or string type
> > assigned at declaration.
> >
> > This is the approach to compile time constants taken to implement Java
> > semantics.
> >
> > FWIW in optimized compiles other fields might be "upgraded" to compile
> time
> > constants.
> >
> > On Dec 5, 2014 2:18 AM, "stuckagain"  wrote:
> >>
> >> I've been trying out GWT 2.7 and SuperDevMode in combination with the
> SDBG
> >> eclipse plugin.
> >>
> >> In the Chrome debugger I noticed that some fields are sometimes
> available
> >> under 'this' but sometimes they are available only in 'this.__proto__'.
> >> It seems that if I have a boolean field that is set to false that it
> does
> >> not appear in 'this' but under 'this.__proto__' and that I can not see
> it at
> >> all in the SDBG plugin. I filed a bug report on SDBG, but I am trying to
> >> figure out how this works in GWT SuperDevMode.
> >>
> >> Another thing that takes getting used: list/map structures are not that
> >> easy to navigate anymore. I hope they found some way to make it easier
> to
> >> have some support to convert them to something readable in the debugger.
> >>
> >>
> >> --
> >> 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/d948f131-0da7-4e9a-998a-925e68a62ced%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/CAC7T7gnmswu4mF_7SRPnZjQYjvykkTvgnnthPDfuFy5gpGamcQ%40mail.gmail.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/CAPVRV7eTkVStPGXrtfiPk5kO8yr2gyjQCZY4xkAD5ufExWB_6g%40mail.gmail.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/CAC7T7gnaifVU5UEa7mU41UuRcEZvwp-NWv_6v5pHsq4Na%3D8uuQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] SuperDevMode sometimes puts member fields in __proto__ why is that ?

['Ray Cromwell' via GWT Contributors]

Static final fields on the prototype? I'm pretty sure these are
promoted to global in optimized mode. Perhaps you meant final
non-static fields? (which we should have an optimization for promoting
to static :) )


On Fri, Dec 5, 2014 at 7:29 AM, 'Roberto Lublinerman' via GWT
Contributors  wrote:
> In draft compile Java compile time constants are emitted in the prototype.
> This should be exactly static final fields of primitive or string type
> assigned at declaration.
>
> This is the approach to compile time constants taken to implement Java
> semantics.
>
> FWIW in optimized compiles other fields might be "upgraded" to compile time
> constants.
>
> On Dec 5, 2014 2:18 AM, "stuckagain"  wrote:
>>
>> I've been trying out GWT 2.7 and SuperDevMode in combination with the SDBG
>> eclipse plugin.
>>
>> In the Chrome debugger I noticed that some fields are sometimes available
>> under 'this' but sometimes they are available only in 'this.__proto__'.
>> It seems that if I have a boolean field that is set to false that it does
>> not appear in 'this' but under 'this.__proto__' and that I can not see it at
>> all in the SDBG plugin. I filed a bug report on SDBG, but I am trying to
>> figure out how this works in GWT SuperDevMode.
>>
>> Another thing that takes getting used: list/map structures are not that
>> easy to navigate anymore. I hope they found some way to make it easier to
>> have some support to convert them to something readable in the debugger.
>>
>>
>> --
>> 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/d948f131-0da7-4e9a-998a-925e68a62ced%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/CAC7T7gnmswu4mF_7SRPnZjQYjvykkTvgnnthPDfuFy5gpGamcQ%40mail.gmail.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/CAPVRV7eTkVStPGXrtfiPk5kO8yr2gyjQCZY4xkAD5ufExWB_6g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] SuperDevMode sometimes puts member fields in __proto__ why is that ?

['Roberto Lublinerman' via GWT Contributors]

In draft compile Java compile time constants are emitted in the prototype.
This should be exactly static final fields of primitive or string type
assigned at declaration.

This is the approach to compile time constants taken to implement Java
semantics.

FWIW in optimized compiles other fields might be "upgraded" to compile time
constants.
On Dec 5, 2014 2:18 AM, "stuckagain"  wrote:

> I've been trying out GWT 2.7 and SuperDevMode in combination with the SDBG
>  eclipse plugin.
>
> In the Chrome debugger I noticed that some fields are sometimes available
> under 'this' but sometimes they are available only in 'this.__proto__'.
> It seems that if I have a boolean field that is set to false that it does
> not appear in 'this' but under 'this.__proto__' and that I can not see it
> at all in the SDBG plugin. I filed a bug report on SDBG, but I am trying to
> figure out how this works in GWT SuperDevMode.
>
> Another thing that takes getting used: list/map structures are not that
> easy to navigate anymore. I hope they found some way to make it easier to
> have some support to convert them to something readable in the debugger.
>
>
>  --
> 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/d948f131-0da7-4e9a-998a-925e68a62ced%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/CAC7T7gnmswu4mF_7SRPnZjQYjvykkTvgnnthPDfuFy5gpGamcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] SuperDevMode sometimes puts member fields in __proto__ why is that ?

[stuckagain]

I've been trying out GWT 2.7 and SuperDevMode in combination with the SDBG 
 eclipse plugin.

In the Chrome debugger I noticed that some fields are sometimes available 
under 'this' but sometimes they are available only in 'this.__proto__'. 
It seems that if I have a boolean field that is set to false that it does 
not appear in 'this' but under 'this.__proto__' and that I can not see it 
at all in the SDBG plugin. I filed a bug report on SDBG, but I am trying to 
figure out how this works in GWT SuperDevMode.

Another thing that takes getting used: list/map structures are not that 
easy to navigate anymore. I hope they found some way to make it easier to 
have some support to convert them to something readable in the debugger.


-- 
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/d948f131-0da7-4e9a-998a-925e68a62ced%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot

[Rob Walker]

In fact - it does seem to work in both models, but only with the following:


   - I have to use the Dev Mod On bookmarklet to trigger a recompile. If I 
   just reload, it doesn't seem to detect and recompile on it's own. I have a 
   feeling running SDM directly did do a recompile on reload on one occasion, 
   but can't be sure.
   - I have to use a -noincremental command option. Without this I get the 
   too many permutations error still
   

-- 
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/4756a6b3-1c1a-4454-a1b9-7cbf7afc7ec2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot

[David]

Hi Rob,

I'm using Jboss Fuse which uses Felix and it works fine in SuperDevMode.
But did I read it right that you start the osgi container embedded with
superdevmode ? I would love to know how I can achieve that as well because
then I don't need to use the -noserver parameter anymore.

I am using the bookmarklets to force a compile and enforce superdevmode
with the remote server. That works just fine for me.

On Fri, Dec 5, 2014 at 10:42 AM, Rob Walker 
wrote:

> Sadly the -launcherDir won't work for us I don't think - we're running an
> embedded Felix/OSGi server which serves up our application from bundle
> JARS. So there is no dir we can point them at.
>
> As per thread below, I think I am making progress with Dev Mode launch
> though - at least it is actually launching now anyhow. Seemed to need quite
> a few command line mods from our original BAT file to launch Dev Mode
>
> On Friday, 5 December 2014 11:31:55 UTC+2, Thomas Broyer wrote:
>>
>>
>>
>> On Friday, December 5, 2014 10:00:59 AM UTC+1, Rob Walker wrote:
>>>
>>> I'm really not surprise people are hitting this issue. It's not clear
>>> (or wasn't to me) from the Release Notes that you no longer run Super Dev
>>> Mode from the standalone program in 2.7 as was done in 2.6, but that
>>> running via Dev Mode enables it.
>>>
>>
>> …or you can keep your launcher with CodeServer but add a -launcherDir
>> argument pointing to the folder your standalone server is serving.
>> CodeServer will then generate a .nocache.js in there that enables "compile
>> on load".
>>
>> And yes the docs need an update (and I wasn't even aware of the issue
>> with the bookmarklets; good to know, and I believe we should try to fix it
>> because it can be really handy)
>>
>  --
> 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/1d9b9b6e-07f1-4c35-96d6-bdc3aa471267%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/CABrJHW1bvqdnq2p%3D1X%3DrQw43S5%2BSH27USnFE3vM0fcr3M0RT-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot

[Rob Walker]

Nope - even though Dev Mode runs now and goes into Super Dev Mode, our 
application is not actually loading in SDM when we visit the web page. 

Our web serving and resources are bundled into JARs, so I suspect the idea 
of overwriting the .nocache.js is just flawed or not working for this mode. 
There is no .nocache.js existing in the file system which overwriting will 
change our application behaviour.

SDM does still work for us if run explicitly, but we have to add a 
-noincremental flag, which I think defeats any speed gains

On Friday, 5 December 2014 11:42:48 UTC+2, Rob Walker wrote:
>
> Sadly the -launcherDir won't work for us I don't think - we're running an 
> embedded Felix/OSGi server which serves up our application from bundle 
> JARS. So there is no dir we can point them at.
>
> As per thread below, I think I am making progress with Dev Mode launch 
> though - at least it is actually launching now anyhow. Seemed to need quite 
> a few command line mods from our original BAT file to launch Dev Mode
>
> On Friday, 5 December 2014 11:31:55 UTC+2, Thomas Broyer wrote:
>>
>>
>>
>> On Friday, December 5, 2014 10:00:59 AM UTC+1, Rob Walker wrote:
>>>
>>> I'm really not surprise people are hitting this issue. It's not clear 
>>> (or wasn't to me) from the Release Notes that you no longer run Super Dev 
>>> Mode from the standalone program in 2.7 as was done in 2.6, but that 
>>> running via Dev Mode enables it.
>>>
>>
>> …or you can keep your launcher with CodeServer but add a -launcherDir 
>> argument pointing to the folder your standalone server is serving. 
>> CodeServer will then generate a .nocache.js in there that enables "compile 
>> on load".
>>
>> And yes the docs need an update (and I wasn't even aware of the issue 
>> with the bookmarklets; good to know, and I believe we should try to fix it 
>> because it can be really handy)
>>
>

-- 
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/fd93475e-ac71-4455-824a-a46d87d5e3c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot

[Rob Walker]

Sadly the -launcherDir won't work for us I don't think - we're running an 
embedded Felix/OSGi server which serves up our application from bundle 
JARS. So there is no dir we can point them at.

As per thread below, I think I am making progress with Dev Mode launch 
though - at least it is actually launching now anyhow. Seemed to need quite 
a few command line mods from our original BAT file to launch Dev Mode

On Friday, 5 December 2014 11:31:55 UTC+2, Thomas Broyer wrote:
>
>
>
> On Friday, December 5, 2014 10:00:59 AM UTC+1, Rob Walker wrote:
>>
>> I'm really not surprise people are hitting this issue. It's not clear (or 
>> wasn't to me) from the Release Notes that you no longer run Super Dev Mode 
>> from the standalone program in 2.7 as was done in 2.6, but that running via 
>> Dev Mode enables it.
>>
>
> …or you can keep your launcher with CodeServer but add a -launcherDir 
> argument pointing to the folder your standalone server is serving. 
> CodeServer will then generate a .nocache.js in there that enables "compile 
> on load".
>
> And yes the docs need an update (and I wasn't even aware of the issue with 
> the bookmarklets; good to know, and I believe we should try to fix it 
> because it can be really handy)
>

-- 
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/1d9b9b6e-07f1-4c35-96d6-bdc3aa471267%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot

[Rob Walker]

OK, so after a bit of a battle, I can get Dev Mode to run under 2.7, which 
now of course launches Super Dev Mode

I needed to change some things though. Our original launch command looked 
like this:

ava -cp "*%TAS_HOME%/proj/webui/src/com/ascert/webui/vt*;
> *%TAS_HOME%/proj/tas/gwtapi/src/com/ascert/tas/gwtapi*;
> *%TAS_HOME%/proj/tas/gwtapi/src*;*%TAS_HOME%/proj/webui/src*;%TAS_HOME%/build/ext/gwt-user.jar;%TAS_HOME%/proj/webui/lib/gwt-servlet-deps.jar;%TAS_HOME%/build/ext/gwt-dev.jar;%TAS_HOME%/build/ext/validation-api-1.0.0.GA-sources.jar;%TAS_HOME%/build/ext/gwtext.jar;%TAS_HOME%/build/ext/gwtextux.jar;%TAS_HOME%/build/ext/highcharts.jar;%TAS_HOME%/build/ext/gxt.jar;%TAS_HOME%/build/ext/gxt-chart.jar;%TAS_HOME%/build/ext/gxt-legacy.jar"
>  
> com.google.gwt.dev.DevMode -noserver -startupUrl 
> http://localhost:8084/VtWebUi/VtWebUi.html* GwtApiTas VtWebUi *
>

I forget why, but we needed paths to both the GWT XML and the sources 
separately. SDM under 2.7 does not like this, instead we needed to fully 
qualify our GWT XML with package names, and remove the path entry to them. 
In fact one module wasn't even on our original command which Dev Modes did 
not complain about (presumably because it was in same source path as main 
module)

java -cp 
"*%TAS_HOME%/proj/tas/gwtapi/src*;*%TAS_HOME%/proj/webui/src*;%TAS_HOME%/build/ext/gwt-user.jar;%TAS_HOME%/proj/webui/lib/gwt-servlet-deps.jar;%TAS_HOME%/build/ext/gwt-dev.jar;%TAS_HOME%/build/ext/validation-api-1.0.0.GA-sources.jar;%TAS_HOME%/build/ext/gwtext.jar;%TAS_HOME%/build/ext/gwtextux.jar;%TAS_HOME%/build/ext/highcharts.jar;%TAS_HOME%/build/ext/gxt.jar;%TAS_HOME%/build/ext/gxt-chart.jar;%TAS_HOME%/build/ext/gxt-legacy.jar"
 
> com.google.gwt.dev.DevMode -nostartServer -logLevel TRACE -startupUrl 
> http://localhost:8084/VtWebUi/VtWebUi.html 
> *com.ascert.tas.gwtapi.GwtApiTas* *com.ascert.webui.core.GwtComponents* 
> *com.ascert.webui.vt.VtWebUi*
>

This removed the 600+ sources with errors, but we still hit an error with 
one of our sub-module missing an inhertis:

When we compile GWT normally, we don't see this error - presumably because 
that module is inherited by our main module.

Not sure yet if this is fully working, but it is at least launching into 
Super Dev Mode via the Dev Mode command line

-- 
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/94f3573f-4aaf-427c-9bdc-b1cd86198cd5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot

[Thomas Broyer]

On Friday, December 5, 2014 10:00:59 AM UTC+1, Rob Walker wrote:
>
> I'm really not surprise people are hitting this issue. It's not clear (or 
> wasn't to me) from the Release Notes that you no longer run Super Dev Mode 
> from the standalone program in 2.7 as was done in 2.6, but that running via 
> Dev Mode enables it.
>

…or you can keep your launcher with CodeServer but add a -launcherDir 
argument pointing to the folder your standalone server is serving. 
CodeServer will then generate a .nocache.js in there that enables "compile 
on load".

And yes the docs need an update (and I wasn't even aware of the issue with 
the bookmarklets; good to know, and I believe we should try to fix it 
because it can be really handy)

-- 
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/b4a63e66-0378-4e66-a7e1-219cf4d1a891%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot

[Rob Walker]

I'm really not surprise people are hitting this issue. It's not clear (or 
wasn't to me) from the Release Notes that you no longer run Super Dev Mode 
from the standalone program in 2.7 as was done in 2.6, but that running via 
Dev Mode enables it.

Reading the docs on Debugging, they do kind of explain this - but there are 
places where they reference what appears to be the original way of running 
Super Dev Mode using bookmarklets, As above, those of us using these are 
not finding they work.

Also, for us, we don't run the embedded Jetty so need to run standalone 
server. Falling back to our old Dev Mode launch script, it does try to 
launch Super Dev Mode but aborts with an error:



Super Dev Mode starting up
>workDir: C:\Temp\gwt-codeserver-8197845274977519094.tmp
>Loading Java files in GwtApiTas.
> *   Ignored 308 units with compilation errors in first pass.*
> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all 
> errors.
>Module setup completed in 4878 ms
>Loading Java files in VtWebUi.
> *   Ignored 310 units with compilation errors in first pass.*
> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all 
> errors.
>Resolving com.ascert.tas.gwtapi.client.driverlib.DriverlibService
>   Found type 'com.ascert.tas.gwtapi.client.driverlib.DriverlibService'
>  Resolving method getDriverDescriptor
> [WARN] Ignoring unresolvable annotation type 
> com.ascert.tas.gwtapi.c
> lient.security.VtasSecurityCheckMethod
>  Resolving method getPackagedEnvironments
> [WARN] Ignoring unresolvable annotation type 
> com.ascert.tas.gwtapi.c
> lient.security.VtasSecurityCheckMethod
>  Resolving method getRepositories
> [WARN] Ignoring unresolvable annotation type 
> com.ascert.tas.gwtapi.c
> lient.security.VtasSecurityCheckReturn
>  Resolving method refreshRepository
> [WARN] Ignoring unresolvable annotation type 
> com.ascert.tas.gwtapi.c
> lient.security.VtasSecurityCheckMethod
>  Resolving method deletePackages
> [WARN] Ignoring unresolvable annotation type 
> com.ascert.tas.gwtapi.c
> lient.security.VtasSecurityCheckMethod
>  Resolving method downloadPackages
> [WARN] Ignoring unresolvable annotation type 
> com.ascert.tas.gwtapi.c
> lient.security.VtasSecurityCheckMethod
>  Resolving method pinPackage
> [WARN] Ignoring unresolvable annotation type 
> com.ascert.tas.gwtapi.c
> lient.security.VtasSecurityCheckMethod
>  Resolving method unpinPackages
> [WARN] Ignoring unresolvable annotation type 
> com.ascert.tas.gwtapi.c
> lient.security.VtasSecurityCheckMethod
>Finding entry point classes
> *  [ERROR] Hint: Check the inheritance chain from your module; it may 
> not be*
> *inheriting a required module or a module may not be adding its source 
> path entri*
> *es properly*
>


We don't have 600 sources with errors, since it clean compiles and runs 
fine. So I'm guessing it has something to do with source paths, given the 
number of modules skipped with errors. But at this stage I'm still lost.

Overall this was not a well documented or explained transition! I am really 
not surprised the average users are battling with it


-- 
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/7141631c-513b-4a58-8d0f-39098bff646d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot

[Rob Walker]

OK - this is very confusing, I went back to the Release Notes to see if I 
missed a breaking change in this area, but the 2.7.0RC1 release notes still 
reference the bookmarklets:

*The Dev Mode On bookmarklet dialog shows whether Super Dev Mode is turned 
on for each module on the page.*

And they don't suggest a different approacH is needed - or maybe I'm just 
not seeing it in the Docs

-- Rob

On Friday, 5 December 2014 10:33:18 UTC+2, Rob Walker wrote:
>
> I see others note the Dev Mode On / Off cause this - what's the new 
> approach then to enter Super Dev Mode?
>
> On Thursday, 4 December 2014 16:49:56 UTC+2, Daniel Kurka wrote:
>>
>> I am really curious why this is not working for you in the first place.
>>
>> Since the code we added to SDM should always scope you down to one 
>> permutation. Are you still using bookmarklets? (These do not deal with this 
>> properly and should not be used anymore).
>>
>>
>>

-- 
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/93745440-779b-4877-b852-c689e6b1721a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot

[Rob Walker]

I see others note the Dev Mode On / Off cause this - what's the new 
approach then to enter Super Dev Mode?

On Thursday, 4 December 2014 16:49:56 UTC+2, Daniel Kurka wrote:
>
> I am really curious why this is not working for you in the first place.
>
> Since the code we added to SDM should always scope you down to one 
> permutation. Are you still using bookmarklets? (These do not deal with this 
> properly and should not be used anymore).
>
> On Thu, Dec 4, 2014 at 3:43 PM, Rob Walker  > wrote:
>
>> OK - I know I'm being exceptionally dumb here, but won't that also limit 
>> a production build to that 1 permutation?
>>
>>
>> On Thursday, 4 December 2014 16:06:23 UTC+2, Robert Hoffmann wrote:
>>>
>>>  The mappings file only reports what was going on in the compile phase, 
>>> so modifying it has no effect.
>>>
>>> You have to set specific values for your properties in the module.xml 
>>> files:
>>> e.g. 
>>> >>
>>> 
>>> <<
>>>
>>> SDM picks this change up I believe without restart. However to see the 
>>> change in the mappings file too, you have to clean and recompile (i.e. 
>>> start your devserver).
>>>
>>>
>>>
>>> On 04/12/14 15:02, Rob Walker wrote:
>>>  
>>>
>>> I'm seeing this file in the artefacts generated by the SDM compile in 
>>> the temp dir. Isn't editing this file only going to apply to the current 
>>> invocation though? 
>>>
>>> Presumably next time around it's going to get a different temp dir, and 
>>> this fill will get recreated again.
>>>
>>> Have to confess - I don't fully follow what this file does though, and 
>>> why we need to manually edit it
>>>
>>> On Thursday, 4 December 2014 15:54:48 UTC+2, Robert Hoffmann wrote: 

  @thomas

 thank you, that helped me to reduce the permutations to one.

 For the record, compilation-mappings.txt contained multiple cache.js 
 file entries, now it only contains one
 >>
 FC8BCE744D2BA8E0C463CE0D2F389DB7.cache.js

 Devmode:devmode.js
 <<
 ...and now sdm works.

 And it's fast :-) 

  
 On Thursday, December 4, 2014 10:15:36 AM UTC+1, Robert Hoffmann wrote: 
>
> Hi,  
>
>  Is there a way to see which properties cause the permutations?
> (I'm using GWT 2.7.0) 
>  

  When compiling your project, you should have 
 a compilation-mappings.txt file generated next to the *.nocache.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/c32c04e2-0ea0-45fc-9e54-c86098d48d85%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Google Germany GmbH
> *Dienerstr. 12*
> *80331 München*
>
> Registergericht und -nummer: Hamburg, HRB 86891
> Sitz der Gesellschaft: Hamburg
> Geschäftsführer: Graham Law, Katherine Stephens
>  

-- 
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/e6e9f8cc-f976-4af5-baa4-a906fb9cc9c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.