<p>I would like to create a database backed interactive AJAX webapp which has a custom (specific kind of events, editing) calendaring system. This would involve quite a lot of JavaScript and AJAX, and I thought about Google Web Toolkit for the interface and Ruby on Rails for server side.</p>

<p>Is Google Web Toolkit reliable and good? What hidden risks might be if I choose Google Web Toolkit? Can one easily combine it with Ruby on Rails on server side? Or should I try to use directly a JavaScript library like jQuery?</p>

<p>I have no experience in web development except some HTML, but I am an experienced programmer (c++, java, c#), and I would like to use only free tools for this project.</p>

[{'answer_id': 30817, 'author': 'Stuart Grassie', 'author_id': 3181, 'author_profile': 'https://Stackoverflow.com/users/3181', 'pm_score': 1, 'selected': False, 'text': "<p>You can code everything in Java using GWT, and you can integrate existing 3rd party javascript libraries with it. It's very good. I've never used RoR much though, so can't say anything about that.</p>\n"}, {'answer_id': 30832, 'author': 'levand', 'author_id': 3044, 'author_profile': 'https://Stackoverflow.com/users/3044', 'pm_score': 1, 'selected': False, 'text': "<p>If you're experienced in Java but not in Javascript/CSS, then GWT is going to be a lifesaver (unless you want to learn them, of course). CSS has so many little fiddly details. It is not uncommon to spend half a day fixing a 2 pixel misalignment that only occurs in IE6.</p>\n\n<p>I am not sure about how easy it would be to use ROR for the back end... It is possible, I am sure, since GWT ajax communication is just servlets. But they provide some really nice functionality for passing Java objects back and forth which you won't be able to utilize if your server isn't also using Java.</p>\n"}, {'answer_id': 30882, 'author': 'John Channing', 'author_id': 3305, 'author_profile': 'https://Stackoverflow.com/users/3305', 'pm_score': 0, 'selected': False, 'text': '<p>You could also consider <a href="http://grails.org/" rel="nofollow noreferrer">Grails</a> ("Groovy on Rails") which gives you the benefits of a Rails framework and the use of the Java VM.</p>\n'}, {'answer_id': 31139, 'author': 'PJ.', 'author_id': 3230, 'author_profile': 'https://Stackoverflow.com/users/3230', 'pm_score': 5, 'selected': True, 'text': '<p>RoR is actually one of the things the GWT is made to work well with, as long as you\'re using REST properly.  It\'s in the Google Web Toolkit Applications book, and you can see a demo from the book using this kind of idea <a href="http://www.gwtapps.com/?page_id=33" rel="noreferrer">here</a>.  That\'s not to say that you won\'t have any problems, but I think the support is definitely out there for it.</p>\n\n<p>There\'s a neat project for making RoR/GWT easy that you can find <a href="http://code.google.com/p/gwt-on-rails/" rel="noreferrer">here</a> (MIT license).  I haven\'t had a chance to try it out yet, but it looks like a good amount of thought has been put into it.  One catch is that it looks like it hasn\'t been fully tested with 2.1 Rails yet, just 2.0, so you may run into a few (probably minor and fixable) errors.</p>\n'}, {'answer_id': 58319, 'author': 'rustyshelf', 'author_id': 6044, 'author_profile': 'https://Stackoverflow.com/users/6044', 'pm_score': 2, 'selected': False, 'text': "<p>If you know JAVA, and have somewhere you can host it (like a tomcat or glassfish container) I would recommend that much more than using Ruby for the back end. The main reason is that then you can share all of your objects, and use the built in RPC mechanism. I've done this for quite a lot of our projects and it's a huge timesaver, not to mention that the code is less error prone, because you don't convert your java objects to anything and then back again.</p>\n\n<p>I have linked my GWT with Rails before, using the to_json function in Rails and then reading the JSON in GWT. It's all supported, but it is far more annoying than just doing the back end in JAVA.</p>\n\n<p>Of course if you have cheap hosting, then Java containers are pretty much out of the question, in which case I would think Rails would be the next best thing.</p>\n"}, {'answer_id': 58332, 'author': 'Michael Neale', 'author_id': 699, 'author_profile': 'https://Stackoverflow.com/users/699', 'pm_score': 2, 'selected': False, 'text': '<p>GWT is very high quality with a great community. However you do need to know CSS if you want to adjust the look of things (you will) - CSS can do a lot of the layout, just like regular web if you want it to. Libraries like GWT-ext or ExtGWT can help a bit as they have stunning "out of the box" looks but for a price (extra size to your app). </p>\n'}, {'answer_id': 82407, 'author': 'Simon Collins', 'author_id': 12412, 'author_profile': 'https://Stackoverflow.com/users/12412', 'pm_score': 2, 'selected': False, 'text': '<p>If you are looking to integrate GWT with non-Java backends such as ROR, PHP etc., you should bear in mind that GWT 1.5 now supports JavaScript Overlay types. This feature lets you write classes that can be mapped over the top of native JavaScript objects to easily provide accessor methods for properties of those objects and other extended functionality.</p>\n\n<p>See this link for more details:\n<a href="http://googlewebtoolkit.blogspot.com/2008/08/getting-to-really-know-gwt-part-2.html" rel="nofollow noreferrer">JavaScript Overlay Types</a></p>\n\n<p>So you could return JSON encoded data from your backend via AJAX calls, parse it into a JavaScript Object and then access the data through your GWT Java code using the overlay classes you\'ve created. Or when you render your page you can render static config data as JavaScript Objects and read it in via this mechanism, rather than having to do an AJAX call to grab the data.</p>\n'}, {'answer_id': 91019, 'author': 'Confusion', 'author_id': 16784, 'author_profile': 'https://Stackoverflow.com/users/16784', 'pm_score': 1, 'selected': False, 'text': '<p>I wrote about some of <a href="http://confusion.tweakblogs.net/blog/1052/the-disadvantages-of-the-google-web-toolkit.html" rel="nofollow noreferrer">the disadvantages of GWT</a> recently. Mainly, the disadvantages are: long deployment cycle for changes to some parts of the application and a rather steep learning curve. As a seasoned Java programmer, the second should be less of a problem and if you use a seperate backend, the first is also mitigated (as a complete redeploy is primarily required when you change the \'server\' part of the application).</p>\n'}, {'answer_id': 113981, 'author': 'Ace', 'author_id': 18673, 'author_profile': 'https://Stackoverflow.com/users/18673', 'pm_score': 1, 'selected': False, 'text': "<p>GWT is a wonderful framework with lots of potential. Keep in mind that it's still quite new, though. There are some unresolved bugs that can really annoy you, and they usually require ugly workarounds to get past. The community is great but you'll probably end up with a few problems sooner or later that Google can't answer yet.</p>\n\n<p>But hey, I say go for it. The potential for GWT is awesome, and I bet it's future will be bright.</p>\n"}, {'answer_id': 272222, 'author': 'Community', 'author_id': -1, 'author_profile': 'https://Stackoverflow.com/users/-1', 'pm_score': 1, 'selected': False, 'text': "<p>You should definitely use GWT for a new project (it's pretty easy to use in an old project too).</p>\n\n<p>I my experience it's very fast to learn and use. The compiled javascript code is much better than anything you could ever write by hand and it works fast too.</p>\n\n<p>Another benefit is the ability to debug you're code (which is hell with javascript alone)</p>\n"}, {'answer_id': 2174790, 'author': 'Ercilla', 'author_id': 262341, 'author_profile': 'https://Stackoverflow.com/users/262341', 'pm_score': 1, 'selected': False, 'text': "<p>This blog has inputs from many experienced users of GWT and have some great discussion points. I personally have huge experience with varied UI Frameworks. I will add my two cents. Lets look at <strong><em>fundamental</em></strong> advantages and disadvantages of GWT</p>\n\n<p><strong>Fundamental Advantage</strong></p>\n\n<p>GWT takes the web layer programming to JAVA. So, the obvious advantages of Java start getting into play. It will provide Object Oriented programming. It will also provide great debugging and compile time checks. Since it generates HTML and Javascript, it will also have ability to hide some complexity within its generator.</p>\n\n<p><strong>Fundamental Disadvantage</strong></p>\n\n<p>The disadvantage starts from the same statement. GWT takes the web layer programming to JAVA. If you know JAVA, probably you will never look out for an alternative language to write your business logic. It's self sufficient and great. But when it comes to writing configurations for a JAVA application. We use property files, database, XML etc. We never store configurations in a JAVA class file. Think hard, why is that?</p>\n\n<p>This is because configuration is a static data. It often require hierarchy. It is supposed to be readable. It never requires compilation. It doesn't require knowledge of JAVA programming language. In short, it is a different ball game. Now the question is, how it relates to our discussion?</p>\n\n<p>Now, lets think about a web page. Do you think when we write a web page we write a business logic? Absolutely not. Web page is just a configuration. It is a configuration of hierarchical containers and fields. We need to write business logic for the data that will be captured from and displayed on the web page and not to create the web page itself. </p>\n\n<p>Previous paragraph makes a very very strong statement. This will explain why HTML and XML based web pages are still the most popular ones. XML is the best in business to write configurations. A framework must allow a clear separation of web page from business logic (the goal of MVC framework). By doing this a web designer will be able to apply his skills of visualization and artistry to create brilliant looking web pages just by configuring XMLs and without being bothered about the intricacies of a programming language. Developers will be able to use their best in business JAVA for writing business logic.</p>\n\n<p>Finally, lets talk about the repercussions in direct terms. GWT breaks this principal so it is bound to fail. The cost for developing GWT application will be very high because you will need multiskill programmers to write web pages. The required look and feel will be very hard to achieve. The turn around time of modifying the web page will be very high because of unnecessary compilation. And lastly, since you are writing web pages in JAVA it is very easy to corrupt it with business logic. Unknowingly you will introduce complexities that must be avoided.</p>\n"}, {'answer_id': 4892902, 'author': 'deborah64554', 'author_id': 545420, 'author_profile': 'https://Stackoverflow.com/users/545420', 'pm_score': 0, 'selected': False, 'text': "<p>Our team recently asked the same question, and we chose to go with GWT, especially since the designer plugin made working with GWT more accessible to non-java experts on the team.  Whoever makes this choice, just beware you DON'T use the GWT Designer plugin !!  It has not been updated (in at least a year, apparently) to create a GWT application that is compatible with IE8.  </p>\n\n<p>Our team had almost completed our application layouts, which were working perfectly in Chrome, FF and Safari.  Then they blew up in IE.  IE 7 would load partial pages (but not composite includes), and IE8 was not even able to load up the application.  It just hung.</p>\n\n<p>The designer plugin has buttons that allow the user to add CellTable widgets that are not IE compatible (CellTable, DeckPanel, Horizontal Panel, Vertical Panel, among others). These will cause intense pain when the layouts have to be re-done in java without assistance from the designer.</p>\n\n<p>Experienced GWT users love it, but the designer plugin will kill you.  </p>\n"}]
['https://Stackoverflow.com/questions/30811', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/2534/']