Group items tagged

My view of GWT is changing. When I wrote 5 GWT Anti-Patterns I saw it as the framework controlling my entire application. Now it's my glue. GWT is a wonderful foundation holding together the different parts of your application. It can grow and expand to new technologies and uses we haven't thought of yet, but it can also hold us back. You can get stuck in GWT and never find your way out. Each of these four anti-patterns addresses different ways to write code you wish you hadn't. The solutions are all about opening doors instead of closing them.

SmartGWT is easy to setup and I simply can't understand why they don't add a few lines into their Getting Started page. Yesterday I found obsolete SmartGWT setup tutorial - but it still works with only one thing missing. As someone mentioned in comments there, you need to add following code into your HTML (before script with your GWT module): Besides this you only need one inherit in your GWT Module XML: And of course - add smartgwt.jar on your classpath for GWT compiler. That's it - now you know how to setup SmartGWT project. (Of course I omitted the coding part, but there is a Showcase with examples.) That's the missing Getting Started. A few lines instead of many links mostly for Eclipse users - with some links not even related to SmartGWT at all.

"The OFCGWT project provides a simple to use chart widget for GWT based on Open Flash Chart 2. The library includes the needed flash insertion, update and manipulation methods for the chart widget. It also includes a POJO model for the chart elements and components that assist in the generation of the JSON to provide the correct chart data for OFC 2.x API. The project has released a beta of version 2.x and a stable 1.3.x release - with over 12,000+ downloads !! Note: A beta of v2.0 (GWT 1.6 support) does contain breaking API for those coming from the 1.X version of OFCGWT - it contains new refactored events and a new chart factory, better attach/detach support, new charts features(new Horizontal Stack Bar Chart, enhanced animations based on OFC Ichor with DZ fixes and patches). "

"Google Web Toolkit (GWT) is a development toolkit for building and optimizing complex browser-based applications. GWT is used by many products at Google, including Google Wave and Google AdWords. It's open source, completely free, and used by thousands of developers around the world. "

""Coming from desktop application development, I have found the IT Mill Toolkit [Vaadin] to be a lot of help in the transition to web application development. With the toolkit, writing AJAX enabled web applications is as easy as writing Swing based GUI code. It hides so many frustrating details, and handles browser independence so I don't have to worry about it. Using the toolkit makes it quite easy for me to write sophisticated web applications." Bo Thorsen, Monty Program AB"

WebORB for PHP is a high-performing, multi-functional development and runtime environment that is FREE and Open Source and designed to effortlessly connect Flex, Flash, AJAX and Silverlight clients with PHP classes and data from relational databases via PHP backend. Some of the key benefits of using WebORB include ease of development, improved development workflow, reduced code base to write and manage, reduced development cost and faster time to market.

WebORB for PHP is a robust FREE and OPEN SOURCE multi-protocol development and runtime environment that is designed to effortlessly connect Flex, Flash, AJAX and Silverlight clients with PHP classes and data from relational databases via PHP backend. WebORB for PHP The goal of WebORB for PHP is to enable a new generation of web applications with enhanced UI capabilities, robust client-server communication, streamlined data synchronization, transaction services support and real-time messaging, all at a reasonable cost that delivers fast time to market.

Response to marbux comments.

# See also my comment on the same web page that explains why HTML 5 is NOT it for document exchange between web editing applications. . - comment by marbux # Response to marbux supporting the WebKit layout/document model. Marbux argues that HTML5 is not interoperable, and CSS2 near useless. HTML5 fails regarding the the interop web appplications need. I respond by arguing that the only way to look at web applications is to consider that the browser layout engine is the web application layout engine! Web applications are actually written to the browser layout/document model, OR, to take advantage of browser plug-in capabilities. The interoperability marbux seeks is tied directly to the browser layout engine. In this context, the web format is simply a reflection of that layout engine. If there's an interop problem, it comes from browser madness differentials. The good news is that there are all kinds of efforts to close the browser gap: including WHATWG - HTML5, CSS3, W3C DOM, JavaScript Libraries, Google GWT (Java to JavaScript), Yahoo GUI, and the my favorite; WebKit. The bad news is that the clock is ticking. Microsoft has pulled the trigger and the great migration of MSOffice client/server systems to the MS WebSTack-Mesh architecture has begun. Key to this transition are the WPF-.NET proprietary formats, protocols and interfaces such as XAML, Silverlight, LINQ, and Smart Tags. New business processes are being written, and old legacy desktop bound processes are being transitioned to this emerging platform. The fight for the Open Web is on, with Microsoft threatening to transtion their entire business desktop monopoly to a Web platform they own. The Web is going to be broken. There is no way of stopping Microsoft at this point. What we can do though is focus on Open Web solutions that are worthy alternatives to Microsoft's proprietary push. For me, this means the WebKit layout/document model supported by Apple, Adobe and Google. ~ge~

A CMS expert argues for HTML over XHTML, explaining his reasons for switching. Excellent read! He nails the basics. for similar reasons, we moved from ODF to ePUB and then to CDf and finally to the advanced WebKit document model, where wikiWORD will make it's stand.