7 items tagged “gwt”
2010
Why don’t more people use Google Web Toolkit for web development as opposed to scripting alternatives like JavaScript?
I’m morally opposed to GWT, because I don’t believe in building sites or applications that are entirely dependent on JavaScript to function. As someone who took the time to learn JavaScript, I’m also not at all convinced that Java is a more productive language.
[... 68 words]2009
Official Google Webmaster Blog: A proposal for making AJAX crawlable. It’s horrible! The Google crawler would map url#!state to url?_escaped_fragment_=state, then expect your site to provide rendered HTML that reflects that state (they even go as far as to suggest running a headless browser within your web server to do this). Just stick to progressive enhancement instead, it’s far less hideous. It looks like the proposal may have originated with the GWT team. # 8th October 2009, 5:52 pm
2008
Doctype: /trunk/goog. Google’s newly released JavaScript library (pure JavaScript, so more along the lines of YUI and jQuery than GWT). I haven’t found the documentation for it yet, but the code is extremely well commented. UPDATE: The documentation is spread throughout Doctype. # 14th May 2008, 9:12 pm
2007
Google Web Toolkit: Towards a better web. Good overview of why GWT exists, but I take exception to the title: requiring JavaScript to even display something does not make the web “better”. # 29th August 2007, 8:21 pm
The website to web application gradient. Jeremy snapped this cunning illustration at my JavaScript Libraries panel at the Web 2.0 Expo. # 20th April 2007, 12:30 am
2006
Making GWT Better. Explains the philosophy behind GWT. It’s all about the tools! # 12th December 2006, 5:53 pm
GWT 1.3 Release Candidate is 100% Open Source. At least you can see how the code generator works now. # 12th December 2006, 5:50 pm