Hi @SID, I recently switched over to GWT for my client side development from ASP.Net as well. In my case we're in the process of writing a full blown Enterprise Package which will be using GWT client side and .Net Server side. So, from my perspective it's actually been easier learning GWT than it's been going through all the different frameworks using ASP.Net and the cool thing is that you get away from the whole ASP.Net engine, which will in essence lessen the load and make you applications much more responsive. You're also breaking away from the page life cycle and trying to maintain multiple ASP.Net pages with some Ajax. With GWT your client side becomes a full blown client application running in the browser and from my side I would definitely recommend making the break away from ASP.Net.
It literally took my team around 2 weeks to get set up with the IDEs and to get to know GWT. My sell to the company I'm working for was quite simply that we should follow the leaders of the perspective platforms. I believe that Google is the leader when it comes to client side and that (personall choice) MS is the leader when it comes to server side. So, our design is a mix of GWT doing server calls through WCF services. We're also designing an offline capability for our solutions which will be making use of Google Gears and will soon start playing with a tool where we can use the same code to run in a "smart client" environment. At this stage the company is still looking at using Silverlight instead of GWT, but if it comes down to myself and my team, the choice will definitely be GWT. I don't believe in making your clients plugin specific and even the Gears implementation will be swicth based. I hope this helps, if you need more information about where to start just ask. We went through quite a nice learning curve and have learned a lot of lessens while doing so :) Enjoy and good luck with the decision... On Mon, Oct 6, 2008 at 2:51 PM, Thomas Broyer <[EMAIL PROTECTED]> wrote: > > > On 6 oct, 13:18, Lothar Kimmeringer <[EMAIL PROTECTED]> wrote: > > > > C and - better - C++ helps to learn Java, but there are some > > differences you have to learn, like the way parameters are > > passed to methods and the lack of "pointers". There should be > > a couple of tutorials out there helping to switch from C++ > > to Java. > > @SID: if you programmed ASP.NET in C#, you won't have any problem > learning Java, as C# is almost a superset of Java (Java has no > "properties", no "indexers", no "delegates", no "value types"). What > will change, of course, is the runtime (and associated classes): JRE > vs. CLR. > > But switching from ASP.NET to GWT+(some server-side runtime) also > means switching mind from a "full-AJAX" app vs. server-generated HTML > +JavaScript (no more "postbacks", even less UpdatePanel and its "async > postbacks"; everything is client-side with GWT and you basically > exchange only data with the server side of your app). > > Now, switching from ASP.NET to servlets is quite easy if you already > used HttpHandlers; and GWT-RPC is similar (in use) to ASP.NET AJAX's > page methods. > > > > I am also considering DRUPAL as another alternative. I have never used > > > PHP as well, but some one told me that it is easy to learn PHP than > > > JAVA. > > > > Again, why do you desperately look for frameworks based on > > a language that you don't know? > > And I don't understand how Drupal can even be compared to GWT+(some > server-side) or ASP.NET... > > > > > -- Kind Regards Jaco van Staden Cell: +27 (0)82 7712294 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
