Thursday, July 3, 2014

Re: JSNI function and DevMode

I've been able to get largely past this issue. It looks like the menus aren't working because of an issue with how the Controllers are loaded in DevMode (still researching). The JS method gets exported and is properly firing the selected page, but that event is getting lost further along.

The part that was throwing me off is that in DevMode, when I have the JS function defined as in the first post, clicking on a menu and firing this function causes the page to clear and "null" to be displayed. If I remove the $entry(); wrapping, the method still fires, but doesn't cause DevMode to clear the page and display "null".

Thanks for everyone's suggestions.

On Thursday, July 3, 2014 12:19:31 PM UTC-4, jonl wrote:

After reading the other replies and looking at this, I would suspect it to be a race condition in DevMode. Where the problem lies in when the exportMenuClickedMethod() is called.

This is where the method being static or not comes into play. By it not being static, it can't be called until an instance of the class is created, which in DevMode may different than in compiled mode because you have the back and forth of the browser and Eclipse here.

So, I would make the method static, and call it in a static initialize block for the class in which it is declared. That way it will be exported more consistently in DevMode and compiled mode.

On Wednesday, July 2, 2014 10:33:33 AM UTC-7, gktcs wrote:
I was trying to "anonymize" what was actually being done when pasting in here and somehow ended up with an extra single quote. I've verified that the application is correct and just using 'PAGE'.

As for the export function not being static...probably just an oversight. I wouldn't think it matters either, but I'll make the change and see if that makes any difference.

On Wednesday, July 2, 2014 11:59:47 AM UTC-4, Patrick Tucker wrote:
You have 2 single quotes after PAGE??
Also, not that it should matter here, but why isn't your export function static?

--
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+unsubscribe@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.

Prautobeans - proto and autobeans maven plugin

at the recent gwt meetup at the google plex quite a bit of discussion around where RPC is going took place in the sidebars.

in my own projects, working on a database backend, I accidentally got sidetracked building a websocket wire protocol based loosely on staying freindly to autbobeans but defining my interfaces in proto IDL. the result is finally able to stand up, if a bit wobbly:

Prautobeans! https://github.com/jnorthrup/prautobeans

at the meetup we saw some action items on bringing ByteBuffers with typedarray support into gwt v.next and doing proof of concept on a project similar in spirit: https://github.com/niloc132/drunken-wallhack (aka gwt3beans)

news that gwt 2.7 is lacking in jdk 8 support is dissapointing, it might mean i have to port the code from jdk8 to jdk7 to support in-gwt bytebuffers, but otherwise this stands to be a reasonably symetrical codebase for rpc and defining websocket messages going forward.

please fork this and don't hesitate to look me up if rpc is giving you grief and you are looking for help or collaboration in getting websocket solutions into a gwt solution!

protbeans project manifesto below

prautobeans

this project was written with the following goals in mind

enable an alternative autobeans marshalling and proxy codebase
1. on serverside
2. use a jdk8 baseline
3. soon gwt 2.7 client, with bytebuffers
marshal a binary encoding
1. that packs element sizes into bytes, or 32-bit ints when >254, and someday never, longs
2. that packs booleans into bits,
3. that packs nulls into bits (or adds one bit to non-null nullables)
4. that packs a DAG of proto defined objects
5. DirectByteBuffer compatibility for zero-copy IO, existing proto based generators rely on heap based byte[]
use maven to generate src/main/proto into the above autobeans and marshalling proxies
heap-averse and compact code, c-like, suitable for a c++ interop port in the near-term

Re: JSNI function and DevMode

After reading the other replies and looking at this, I would suspect it to be a race condition in DevMode. Where the problem lies in when the exportMenuClickedMethod() is called.

This is where the method being static or not comes into play. By it not being static, it can't be called until an instance of the class is created, which in DevMode may different than in compiled mode because you have the back and forth of the browser and Eclipse here.

So, I would make the method static, and call it in a static initialize block for the class in which it is declared. That way it will be exported more consistently in DevMode and compiled mode.

On Wednesday, July 2, 2014 10:33:33 AM UTC-7, gktcs wrote:

I was trying to "anonymize" what was actually being done when pasting in here and somehow ended up with an extra single quote. I've verified that the application is correct and just using 'PAGE'.

As for the export function not being static...probably just an oversight. I wouldn't think it matters either, but I'll make the change and see if that makes any difference.

On Wednesday, July 2, 2014 11:59:47 AM UTC-4, Patrick Tucker wrote:
You have 2 single quotes after PAGE??
Also, not that it should matter here, but why isn't your export function static?

Re: GWT Developer Plugin

On Thursday, July 3, 2014 4:51:59 PM UTC+2, Jens wrote:

On Windows you can:

- Use IE with classic DevMode browser plugin
- Use FireFox 26 or FireFox 24 ESR with classic DevMode browser plugin
- Use an older Chrome (I think up to Chrome 33) with classic DevMode browser plugin

- Use any browser with SuperDevMode which does not require a browser plugin.

SuperDevMode uses a code server that can compile your app to JavaScript relatively fast. With a bookmarklet in your browser you can trigger recompiles to pick up code changes. SuperDevMode does not provide the same experience than classic DevMode.

http://www.gwtproject.org/articles/superdevmode.html (article is a bit outdated)

Step-by-step howto for setting up and using SuperDevMode: https://stackoverflow.com/a/18333050/116472

Re: GWT Developer Plugin

On Windows you can:

- Use IE with classic DevMode browser plugin

- Use FireFox 26 or FireFox 24 ESR with classic DevMode browser plugin

- Use an older Chrome (I think up to Chrome 33) with classic DevMode browser plugin

- Use any browser with SuperDevMode which does not require a browser plugin.

SuperDevMode uses a code server that can compile your app to JavaScript relatively fast. With a bookmarklet in your browser you can trigger recompiles to pick up code changes. SuperDevMode does not provide the same experience than classic DevMode.

http://www.gwtproject.org/articles/superdevmode.html (article is a bit outdated)

-- J.

Re: GWT Developer Plugin

What do you mean, can please be more accurate?

SuperDevMode is another plugin with the same functionality?

AFAIK what is that and where i can find it?

thanks really a lot

2014-07-03 15:18 GMT+02:00 manstis <michael.anstis@gmail.com>:

Or use SuperDevMode

Support for DevMode browser plugins is, AFAIK, coming to an end...

On Wednesday, 2 July 2014 16:18:37 UTC+1, Francesco Viscomi wrote:
Hi all

i need to use GWT Developer Plugin and I have windows 8 at 64bit

either chrome and firefox i'm not able to use the plugin;

when i try to download it i get:

(firefox)
Sorry, the GWT Developer Plugin only supports Firefox 3.0 - 26.0.
Perhaps download Firefox 24?

(chrome)
start to download but a pop up inform me that the installation has been disabled because it is necessary plugin NPAPI;

how i can resolve this issue? thanks a lot

Francesco

--
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/t1N2wpHjD54/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@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.

--
Ing. Viscomi Francesco

Re: GWT Developer Plugin

Or use SuperDevMode

Support for DevMode browser plugins is, AFAIK, coming to an end...

On Wednesday, 2 July 2014 16:18:37 UTC+1, Francesco Viscomi wrote:

Hi all

i need to use GWT Developer Plugin and I have windows 8 at 64bit

either chrome and firefox i'm not able to use the plugin;

when i try to download it i get:

(firefox)
Sorry, the GWT Developer Plugin only supports Firefox 3.0 - 26.0.
Perhaps download Firefox 24?

(chrome)
start to download but a pop up inform me that the installation has been disabled because it is necessary plugin NPAPI;

how i can resolve this issue? thanks a lot
Francesco