Re: [gwt-contrib] Re: CodeServer with Bookmarklets not working in GWT 2.7 (2nd request)

['Daniel Kurka' via GWT Contributors]

This is what recompile on reload is for, you can simply always load:

http://[sdmhost]:[sdmport]/recompile-requester/[module]

On Tue, Sep 13, 2016 at 5:53 PM JonL  wrote:

> I've had to do this when working on a sdm compiled application in a web
> wrapper on ios, instead of a proxy, I wrote a custom nocache.js that
> replaces the one generated by sdm and adds a url parameter to tell it the
> remote server to connect to where the codeserver is running, allowing me to
> debug the application running directly on the ipad correctly.
>
> Here is a gist of a sligtly modified version of the nocache.js replacing
> the module name with "module_name":
>
> https://gist.github.com/jonl-percsolutions-com/403ec9ba1bf50a6abcb0db852b171d0c
>
> So I just run my gwt-compile, replace the nocache.js and then create the
> war for deployment.   The when accessing the url, provide the url paramter "
> remote_server=http://ip:port;.
>
> Not sure if this will be what you need 100% but should work instead of
> setting up a proxy or clobbering the codeserver api.
>
>
> On Monday, September 12, 2016 at 12:24:54 PM UTC-7, Brandon Donnelson
> wrote:
>
> Proxying wasn't an option for developers because of the I.T. security
> protocols. Besides it feels a bit overcomplicated to have to set up a
> channel back to the code server. I think it would be easier to clobber the
> codeserver api with a workaround and setting the hosteName and hand that to
> the developers. I'm contemplating on forking the code server for GWT 2.7
> users to provide a workaround for the hostName through the program
> arguments.
>
> On Sat, Sep 10, 2016 at 1:43 AM Thomas Broyer  wrote:
>
> How about proxying through a local server that would intercept the
> nocache.js and route everything else to your external server? This is
> basically how webpack devserver and browserSync work in the JS land.
>
> --
> 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/13bfb1ba-f2fb-40cf-afda-c9902d016cb3%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> *Brandon Donnelson*
> GXT Support Engineer
>  
> 
> 
> 
> [image: SenchaCon 2016 Aria Resort, Las Vegas, November 7-9]
> 
> *Join me at SenchaCon 2016!*
>
> --
> 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/274f1c7b-8267-4164-8d11-ab3e64dd9721%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/CALLujio-C04RR1v%2BPbf0AA5QcQp8S4ts%3DEbn7SkgT2ENheYc8Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: CodeServer with Bookmarklets not working in GWT 2.7 (2nd request)

[JonL]

I've had to do this when working on a sdm compiled application in a web 
wrapper on ios, instead of a proxy, I wrote a custom nocache.js that 
replaces the one generated by sdm and adds a url parameter to tell it the 
remote server to connect to where the codeserver is running, allowing me to 
debug the application running directly on the ipad correctly.

Here is a gist of a sligtly modified version of the nocache.js replacing 
the module name with "module_name":
https://gist.github.com/jonl-percsolutions-com/403ec9ba1bf50a6abcb0db852b171d0c

So I just run my gwt-compile, replace the nocache.js and then create the 
war for deployment.   The when accessing the url, provide the url paramter "
remote_server=http://ip:port;.

Not sure if this will be what you need 100% but should work instead of 
setting up a proxy or clobbering the codeserver api.

On Monday, September 12, 2016 at 12:24:54 PM UTC-7, Brandon Donnelson wrote:
>
> Proxying wasn't an option for developers because of the I.T. security 
> protocols. Besides it feels a bit overcomplicated to have to set up a 
> channel back to the code server. I think it would be easier to clobber the 
> codeserver api with a workaround and setting the hosteName and hand that to 
> the developers. I'm contemplating on forking the code server for GWT 2.7 
> users to provide a workaround for the hostName through the program 
> arguments.   
>
> On Sat, Sep 10, 2016 at 1:43 AM Thomas Broyer  > wrote:
>
>> How about proxying through a local server that would intercept the 
>> nocache.js and route everything else to your external server? This is 
>> basically how webpack devserver and browserSync work in the JS land.
>>
>> --
>> 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/13bfb1ba-f2fb-40cf-afda-c9902d016cb3%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> *Brandon Donnelson*
> GXT Support Engineer
>   
>  
>  
> 
> [image: SenchaCon 2016 Aria Resort, Las Vegas, November 7-9] 
> 
> *Join me at SenchaCon 2016!*
>

-- 
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/274f1c7b-8267-4164-8d11-ab3e64dd9721%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: CodeServer with Bookmarklets not working in GWT 2.7 (2nd request)

[Brandon Donnelson]

Proxying wasn't an option for developers because of the I.T. security
protocols. Besides it feels a bit overcomplicated to have to set up a
channel back to the code server. I think it would be easier to clobber the
codeserver api with a workaround and setting the hosteName and hand that to
the developers. I'm contemplating on forking the code server for GWT 2.7
users to provide a workaround for the hostName through the program
arguments.

On Sat, Sep 10, 2016 at 1:43 AM Thomas Broyer  wrote:

> How about proxying through a local server that would intercept the
> nocache.js and route everything else to your external server? This is
> basically how webpack devserver and browserSync work in the JS land.
>
> --
> 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/13bfb1ba-f2fb-40cf-afda-c9902d016cb3%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
*Brandon Donnelson*
GXT Support Engineer
 



[image: SenchaCon 2016 Aria Resort, Las Vegas, November 7-9]

*Join me at SenchaCon 2016!*

-- 
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/CAA_mbNO97_gUCZiAPKOAG%2BNRG3pD0AWyt8wLrjFhSdGwSdioEA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: CodeServer with Bookmarklets not working in GWT 2.7 (2nd request)

[Thomas Broyer]

How about proxying through a local server that would intercept the nocache.js 
and route everything else to your external server? This is basically how 
webpack devserver and browserSync work in the JS land.

-- 
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/13bfb1ba-f2fb-40cf-afda-c9902d016cb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: CodeServer with Bookmarklets not working in GWT 2.7 (2nd request)

[Brandon Donnelson]

I haven't dug in yet, just wanting to use it. That sounds promising. Using 
bookmarlets doesn't work when the module is embedded in another iframe. so 
the next issue I need to deal with is helping detect the module when it's 
not in the main body but in another iframe of the document. 

The other workaround is to implant the project.nocache.js js launching in 
the war and send it off to the external server. So this makes another 
problem I have hit a couple times. Where I change the var hostName = 
"127.0.0.1";  to a specific ip because I loaded the app with 
project.nocache.js. I like this hack but I'm wishing I could set that in 
the code server launcher arguments. 

Anyway it's all about using an external server. 

-- 
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/41735d5b-1848-44e6-be31-3a34d87ddec7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: CodeServer with Bookmarklets not working in GWT 2.7 (2nd request)

[Thomas Broyer]

Doesn't CodeServer accept -setProperty? You could use that to pinpoint the 
property values so you only have one permutation when only user.agent is given.

-- 
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/fe7f6b31-c172-4043-a56e-0b43d716c4a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: CodeServer with Bookmarklets not working in GWT 2.7 (2nd request)

[Brandon Donnelson]

Workaround, hit dev mode off then compile again. 

-- 
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/2f411e2b-688f-4028-b8f9-95f052952e57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.