Upgrading from 1.4 to 2.0

[Andre Freller]

Hi All,

We are upgrading from 1.4 to 2.0 and I would like to share this experience
with you.
First of all, the site is flying! Congrats and thank you GWT Team.

The only problem we faced so far was a strange RPC behavior when the call
was
launched from a  NativePreviewHandler. Our site registered a EventPreview to
handle
keyboard events like Escs and Arrows even when there was no FocusWidget
selected.

In some situations, when the user sends a Escape to close a popup window,
the
Widget under that popup makes a RPC to redraw it self.

After changing from EventPreview to NativePreviewHandler the RPC begin to
fail with a
StatusCodeException. There was no server side error. I even wrote
a doUnexpectedFailure
method to see if there was an error that our app was not registering, but it
was never
call.

The solution was to encapsulate the RPC in a DeferredCommand. Now everything
is working
and faster then before.

Question. Even specifying one locale and one user.agent the gwt Compiler
compiles 2 permutation. Is this the minimum number of permutations
produced by the compiler? What else can be done to accelerate compiler
time during development?

Best regards,
Freller
-- 

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-tool...@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: Problem with GWT Widget Printing

[Andre Freller]

Hi Jay,
I was wondering if DOM.toString() works too on 1.4, I tested and it does
work.

I'll post a new version so it will work on 1.5 too.

Regards,
Freller


On Mon, Apr 6, 2009 at 14:42, jay  wrote:

>
> I'm not sure what you're asking... If you're asking if you can pass a
> DOM element to your "it" method and have it work, then in 1.5 the
> answer is no...the implicit toString() call won't do what it does in
> 1.4. Which is why in 1.5 you need to use the DOM.toString() method...
>
> (If you're asking something else, then I apologize for not answering
> it.)
>
> jay
>
> On Apr 5, 9:31 am, Freller  wrote:
> > The beauty of open source! I haven't migrated to 1.5 yet, so this
> > error is new to me.
> > We will jump directly to 1.6. The Print class boil down to :
> >
> > public static void it(String html) {
> > try {
> > buildFrame(html);
> > DeferredCommand.add(printFrameCommmand);
> > } catch (Throwable exc) {
> > Window.alert(exc.getMessage());
> > }
> > }
> >
> > public static void it(String style, String it) {
> > it(""+style+"\n"+it+" > html>");
> > }
> >
> > I did that so we could print both DOM elements and strings.
> > Perhaps I should treat DOM elements diferently adding them to the DOM
> > instead
> > of using the toString method? Anybody know if this will render faster
> > and/or more
> > correct prints?
> >
> > Jay, does this work for both 1.4 and 1.5 or it'll only work on 1.5?
> >
> > Regards,
> > Freller
> >
> > On Apr 3, 6:27 pm, jay  wrote:
> >
> >
> >
> > > It seems that prior to GWT 1.5, element.toString() did the right
> > > thing. When I moved to GWT 1.5.3, I had to switch to using
> > > "DOM.toString( elem );"
> >
> > > jay
> >
>

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Google App Engine & GWT

[Andre Freller]

Good news:  
http://code.google.com/appengine/docs/java/overview.html
...

The Google Plugin for
Eclipse
adds
new project wizards and debug configurations to your
Eclipse IDE
for App Engine projects. App Engine for Java makes it especially easy to
develop and deploy world-class web applications using Google Web
Toolkit (GWT).
The Eclipse plugin comes bundled with the App Engine and GWT SDKs.
...
I still don't know if it supports server side GWT code for proper GWT-RPC.


Bad news:  
http://code.google.com/appengine/docs/java/runtime.html
...
The Sandbox
...
Threads

A Java application cannot create a new java.lang.ThreadGroup nor a new
java.lang.Thread. These restrictions also apply to JRE classes that make use
of threads. For example, an application cannot create a new
java.util.concurrent.ThreadPoolExecutor, or a java.util.Timer. An
application *can* perform operations against the current thread, such as
Thread.currentThread().dumpStack().

...



Regards,

Freller

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

UiBinder & Code spliting

[Andre Freller]

Hi all,

I'm trying to adopt the UiBinder approach but it appears to me that it is
 interfering with code spliting. The only post I could find about this is
this one:

http://groups.google.com/group/google-web-toolkit/browse_frm/thread/cd3de21e9ea3ebcf/29cc98e4cb33d6dd?lnk=gst&q=runAsync+uibinder#29cc98e4cb33d6dd

Is it possible to use both techniques in one project? If so, any hint?

Regards,
Freller

-- 
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-tool...@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.