I'm going to have to say no on this. If you're a PHP programmer with little to no Java experience since version 1.4, I would say you are going to burn yourself. GWT programming requires some fundamental knowledge of Java. You can take a look at those of us trying to digest the Google IO Best Practices, and all the sample apps that have sprung up trying to exemplify MVP, eventbus, IOC, command pattern RPC, etc. Lets not kid ourselves, this was not the Java we learned at the university, unless you really went in depth with GoF.
Those of us that either had prior knowledge of Java or have accepted the challenge of learning it can reap the rewards of using GWT. If you really want to learn Java, GWT is a good way to see quick results. (In this respect, PHP development is also gives a quick positive-feedback). But to architect an application will require a significant investment of your cycles. The payoff however, is huge. Depending on your personality, you may take this warning as a challenge or a snub. I hope you're successful at whichever path you take. On Wed, Jul 15, 2009 at 3:26 PM, Christian Goudreau < [email protected]> wrote: > I'm using PHP and GWT for my projects, i've done a lot of work around and > here's my though : > > Not enough documentation around the PHP and GWT projet. I had no enough > time to go around the libraries and learn everything from the code and the > exemples. I really hope this project will eventually become bigger and > integrated within the eclipse plugin since we can use native RPC calls with > php ! > > In the meanwhile, I'm using JSON object and XML to communicate between my > server and GWT. Since I don't have realy have big objects, it's fast and > reliable. But not as fast as native RPC calls. > > It is possible to use another server than the tomcat server from eclipse > for debugging. But you still need two project. > > Christian > > > On Wed, Jul 15, 2009 at 10:00 AM, ET <[email protected]> wrote: > >> >> I recommand using GWT... hands down. Not having to write javascript >> directly is a thing of beauty. Why worry about all of the cross- >> browser inconsistencies when GWT has taken care of that for you? ;-) >> >> On Jul 14, 11:39 am, Dalla <[email protected]> wrote: >> > Well, I can give you my thoughts on this :-) >> > >> > I tried using Dojo some time ago, and thought it had some really neat >> > features. >> > Though I didn´t like all having to write java script from scratch... >> > >> > Later I stumbled upon GWT, and I really liked it. >> > Maybe it´s not so strange that I liked it since I was a java web >> > developer using Struts 2 and JSP already, >> > but I love being able to develop AJAX applications from pure java >> > code, being able to use all the benefits of eclipse, >> > debugging, and so on. >> > >> > I´m not sure you´d have to create separate projects for PHP and GWT if >> > you don´t want to, >> > but maybe it would be a good idea for other reasons. >> > >> > I would start with GWT if I was you, but like I said, I was a java >> > developer before, >> > and also you´re asking your question on a GWT forum, so what´s to >> > expect? :-) >> > >> > --Dallahttp://date-time.appspot.com/ >> > >> > On 14 Juli, 13:20, pappfer <[email protected]> wrote: >> > >> > > For some reason I couldn't send this reply to my old thread: >> http://groups.google.com/group/Google-Web-Toolkit/browse_thread/threa... >> > > So I started this with the same title. >> > >> > > Thank you for your replies! >> > > I decided to stick with Dojo if I use some animation. >> > >> > > But now I want to build up a completely new website and a question got >> > > in my head again. My goal is to build up a mobile stuff download page >> > > where users could upload their stuffs (wallpaper, screensaver, themes, >> > > etc.) and others could download it. >> > > The features where I'd like to use AJAX technology are: >> > > - Upload multiple files without reloading the page - also with >> > > progressbar >> > > - Browse between wallpapers, screensavers, etc. without reloading the >> > > page >> > > - Rate wallpapers, etc. without reloading the page (like you do it >> > > here in GWT forums) >> > >> > > Now I'm thinking of either learning AJAX basics (I mean the XHR object >> > > and so) or building the complete webpage with GWT. I don't feel >> > > comfortable using some other stuffs like EXT-GWT or so because it >> > > might lack of support in the future and also new versions coming out >> > > later I think. >> > >> > > In my point of view pros for learning AJAX basics are: >> > > - could get to see more into AJAX >> > > - could make the site much more SEO friendly I guess >> > > - I wouldn't have to make separate projects in my Eclipse: one for PHP >> > > and one for Java so it'd be more comfortable >> > >> > > Pros for using GWT are: >> > > - could get more into Java >> > > - could possibly make more powerful web applications >> > > - AFAIK it deals good with browsers back button, and browser >> > > compatibility is good too which I'm not sure I could solve the other >> > > way >> > >> > > I'm also not sure why GWT uses it's on widgets while we have checkbox, >> > > labels, etc in HTML, too. >> > > What do you suggest me to use? >> > >> > > I'm happy to learn both Ajax basics and GWT too. >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
