Re: Upgrading 1.5 application: troubles with click event on Hyperlink and Anchor
The problem was that I had replaced
RootPanel.get("linksPanel").add(linksPanelWidget);
with
Document.get().getElementById("linksPanel").appendChild
(linksPanelWidget.getElement());
because I was getting the error "A widget that has an existing parent
widget may not be added to the
detach list"
and this caused the click event to not reach my handler.
Putting back the RootPanel(...) code fixed it, and the 2.0 code is
after all correct:
Anchor loginLnk = new Anchor(msg.login());
loginLnk.addClickHandler(new ClickHandler(){
@Override
public void onClick(ClickEvent ev) {
login();
}
});
On Dec 31, 11:50 am, hbatista wrote:
> I'm trying to upgrade a GWT 1.5 application into 2.0, and having
> problems getting hyperlink/anchor clicks to work as before.
>
> My 1.5 code is very simple, I'm creating a hyperlink and adding a
> click listener to it:
>
> Hyperlink loginLnk = new Hyperlink(msg.login(), "");
> loginLnk.addClickListener(new ClickListener(){
> public void onClick(Widget sender) {
> login();
> }
>
> });
>
> Now, in 2.0, Hyperlink.addClickHandler is deprecated (and nothing
> happens when clicking it).
> If I replace it with an Anchor, I'm redirected to onModuleLoad when
> clicking it, and my handler doesn't run.
>
> What is the correct way to implement this behavior in GWT 2.0 ?
--
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.
Upgrading 1.5 application: troubles with click event on Hyperlink and Anchor
I'm trying to upgrade a GWT 1.5 application into 2.0, and having
problems getting hyperlink/anchor clicks to work as before.
My 1.5 code is very simple, I'm creating a hyperlink and adding a
click listener to it:
Hyperlink loginLnk = new Hyperlink(msg.login(), "");
loginLnk.addClickListener(new ClickListener(){
public void onClick(Widget sender) {
login();
}
});
Now, in 2.0, Hyperlink.addClickHandler is deprecated (and nothing
happens when clicking it).
If I replace it with an Anchor, I'm redirected to onModuleLoad when
clicking it, and my handler doesn't run.
What is the correct way to implement this behavior in GWT 2.0 ?
--
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.
Server side includes with built-in Tomcat?
Hi, I want to have server side includes in my GWT main page. On an external Tomcat server I had no problem, but I can't make it work with the built in server. I added the SSI servlet configuration to the ROOT/WEB-INF/web.xml file and I think the servlet is starting correctly, but the SSI directives aren't being processed. Any help is appreciated. Thanks --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
Not to resurrect the thread, but I feel I need to add some input to this, as I've been using Gwt-Ext for over a year now. I've been using it in a big and complex application, and the results have been great. Now, about some points people have raised: -Slowness: if you design your application properly and use the right widgets for each job, you'll have no problems. Our application runs like a charm, and it deals with BIG datasets. But yes, you do need to code thinking about performance, as is the case with ANY other application if you deal with a lot of data. -Bugs: I've come across a couple, but nothing serious, and you do have the source, so you can FIX them (I've done it when needed). The detractors please tell me of a piece of software that doesn't have a bug... Our app has always been completely stable, no problems there, so I don't know what some people here are talking about... -Maintainability/extensibility: you have the source, so you can adapt and extend whatever widget you want (done that too). If you think you can develop the same kind of functionality with just GWT / CSS to match one of these libraries in a decent amount of time, you are just insane, or just are so inexperienced you cannot understand how much work you have ahead of you. It saved us a huge (I mean HUGE) amount of time, and I recommend it. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Severe performance problem after upgrading to GWT 1.5.2 (final)
In my case I made some mistake while profiling my code... turns ot that for some reason the database access got really slow. I switched the database drivers (from jtds to the microsoft jdbc driver for sql server) and everything went back to normal. On Sep 30, 8:20 pm, Manuel <[EMAIL PROTECTED]> wrote: > Has anyone figured what is going.. I am experiencing same problems.. > everything seems slower. > > On Sep 18, 4:59 am, hbatista <[EMAIL PROTECTED]> wrote: > > > > > Thanks for the suggestion, but changing data types didn't help. > > I did not profile my code, but the observed behavior is: > > 1. RPC call is made > > 2. server side method runs and returns (quickly!) > > 3. ... huge delay with no CPU activity ... > > 4. finally client side onSuccess() RPC callback runs > > > What could be happening on step 3 ? > > > I took a quick look at the serializer source code, but it's too > > different from 1.4.60 to compare side by side. > > > On Sep 18, 2:06 am, Tim <[EMAIL PROTECTED]> wrote: > > > > not sure, but maybe there are some datatype penalty issues (long vs > > > double etc). Did you profile your server side code? > > > > On Sep 17, 10:28 am, hbatista <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > I've just upgraded one of my projects from 1.4.60 to1.5.2, and > > > > everything went very smoothly, but... > > > > when my application tries to fetch a large number of objects from the > > > > server (via RPC, returns HashMap, about 6000 entries) it > > > > takes a very very long time! > > > > > Before the upgrade this was very fast (at least in Firefox and Chrome, > > > > not in IE). > > > > > Strangely, while waiting for the RPC call to return there is NO cpu > > > > activity... > > > > > For me this seems related to some deep changes in the serialization > > > > code (taking a guess here), before the upgrade trying to fetch so many > > > > records from the server would crash IE with 'JavaScript SyntaxError > > > > exception: Out of memory', while now it works (good!) but is veryslow > > > > in all browsers (bad!). > > > > > Can someone help me debug this problem?- Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Severe performance problem after upgrading to GWT 1.5.2 (final)
Thanks for the suggestion, but changing data types didn't help. I did not profile my code, but the observed behavior is: 1. RPC call is made 2. server side method runs and returns (quickly!) 3. ... huge delay with no CPU activity ... 4. finally client side onSuccess() RPC callback runs What could be happening on step 3 ? I took a quick look at the serializer source code, but it's too different from 1.4.60 to compare side by side. On Sep 18, 2:06 am, Tim <[EMAIL PROTECTED]> wrote: > not sure, but maybe there are some datatype penalty issues (long vs > double etc). Did you profile your server side code? > > On Sep 17, 10:28 am, hbatista <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > I've just upgraded one of my projects from 1.4.60 to 1.5.2, and > > everything went very smoothly, but... > > when my application tries to fetch a large number of objects from the > > server (via RPC, returns HashMap, about 6000 entries) it > > takes a very very long time! > > > Before the upgrade this was very fast (at least in Firefox and Chrome, > > not in IE). > > > Strangely, while waiting for the RPC call to return there is NO cpu > > activity... > > > For me this seems related to some deep changes in the serialization > > code (taking a guess here), before the upgrade trying to fetch so many > > records from the server would crash IE with 'JavaScript SyntaxError > > exception: Out of memory', while now it works (good!) but is very slow > > in all browsers (bad!). > > > Can someone help me debug this problem?- Hide quoted text - > > - Show quoted text - --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Severe performance problem after upgrading to GWT 1.5.2 (final)
Hi, I've just upgraded one of my projects from 1.4.60 to 1.5.2, and everything went very smoothly, but... when my application tries to fetch a large number of objects from the server (via RPC, returns HashMap, about 6000 entries) it takes a very very long time! Before the upgrade this was very fast (at least in Firefox and Chrome, not in IE). Strangely, while waiting for the RPC call to return there is NO cpu activity... For me this seems related to some deep changes in the serialization code (taking a guess here), before the upgrade trying to fetch so many records from the server would crash IE with 'JavaScript SyntaxError exception: Out of memory', while now it works (good!) but is very slow in all browsers (bad!). Can someone help me debug this problem? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
