[gwt-contrib] Re: Focus/blur on a group of widgets?
On Sun, Sep 6, 2009 at 2:00 PM, Ed wrote: > I think it would be possible if you use a kind of delayed-pipeline > (pattern): holding on to an event till some condition is met before > forwarding itExample of the condition: till a maximum delay time > is reached and/or the focus of the previous blur event is received. > The advantage would be to receive the blur and focus event together in > one event as a kind of paired event. So you can immediately find out > which widget (if there is any) receives focus on a blur event... > The problem is that even objects on IE are weird -- you can't save them outside the context of the event handler they are passed to, and copying doesn't work. -- John A. Tamplin Software Engineer (GWT), Google --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: Comment on UsingOOPHM in google-web-toolkit
I am able to use Mac/OOPHM/Firefox3.5. Did you follow the directions (and discussions) on this page? http://code.google.com/p/google-web-toolkit/wiki/OophmForMacBasedGwtContributors On the other hand, I didn't use the provided link (Firefox) ... I built the plugin. Brett On Sep 6, 11:07 am, codesite-nore...@google.com wrote: > Comment by Dominik.J.Steiner: > > I'm on Mac Leopard and just build GWT from trunk, installed the above link > for FF 3.5 OOPHM plugin, ran my module in OOPHM and tried conecting to the > app withhttp://localhost:8080/MyApp.html?gwt.hosted=10.0.2.1:9997, but I > also get instantly the message "No GWT plugin found or hosted-mode > connection failed". Reading through the comments it seems that more people > are having that problem or am I missing something? > > For more > information:http://code.google.com/p/google-web-toolkit/wiki/UsingOOPHM --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: New API proposal: BatchedCommand
As a long time Java programmer (since v0.9!), I'd just like to throw in that I don't see any particular practical benefit to leveraging Runnable or Callable. Sure, they are just interfaces, and you could re-use them. But beyond that, especially with respect to Callable, almost nothing execution related from java.util.concurrent is applicable to thread-less JavaScript. Borrowing one interface from java.util.concurrent because it has the same signature, yet not implementing any of the java.util.concurrent features is more confusing to a Java programmer coming to GWT. So while I appreciate Eric's point of view, I don't share it. Jason's suggestion of re-using Executor and ExecutorService is also likely not practicable in GWT because of ExecutorService's blocking methods (invokeAll(), awaitTermination). Ray's last suggestion gets my vote. It looks substantially like the existing pattern and does not inject unnecessary new controller or scheduler classes. I'm of the "simplest thing that can possibly work" school of thought as of late. Brett Wooldridge --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: Focus/blur on a group of widgets?
I asked around on the net and got the idea that it's not possible at all. I think because these events are received from the underlying OS and simple forwarded, which makes sense I think it would be possible if you use a kind of delayed-pipeline (pattern): holding on to an event till some condition is met before forwarding itExample of the condition: till a maximum delay time is reached and/or the focus of the previous blur event is received. The advantage would be to receive the blur and focus event together in one event as a kind of paired event. So you can immediately find out which widget (if there is any) receives focus on a blur event... --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Comment on OophmForMacBasedGwtContributors in google-web-toolkit
Comment by jon.hanson: Thanks monika7, those steps appear to have worked for me. For more information: http://code.google.com/p/google-web-toolkit/wiki/OophmForMacBasedGwtContributors --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
