Thanks for the suggestions everyone. Definitely some things to think about in them.
I probably should have explained that I am looking at things more from an architecture design view. I am not likely going to do very much coding on this myself, but I don't want to end up with the ball of mud that can be JavaScript, which is likely without GWT - probably an assumption but based on a lot of feedback from people with some experience in large JavaScript projects that have multiple developers involved. I realise that in principle pretty much any language could be used server side and GWT could still be used, but it seems initially at least that a lot of the benefit of a single language with a single IDE would be lost doing that. The other probable advantage to Java + GWT over say Django + GWT is that a developer with the skills to work on the back end could also work on the front end and vice versa. In my mind there is a fairly large difference between a Java expert and someone that "knows some Java" in the same way that there is a difference between a Django expert and someone that "knows some Django" in terms of efficiency of code as well as development and debugging time. Hence I am wary of getting someone to code the back end in Django as well as the front end in Java (GWT). It sounds like I am really arguing with myself :o) The question I suppose really comes down to how much simpler it would be keeping things all in Java v. splitting it between two languages? Regards, John --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
