Google Web Toolkit to Include Speed Tracer and More Productive Tools

By Partho, Gaea News Network
Wednesday, December 9, 2009

With Goolge’s spree of announcements for new innovations continuing, we’ve grown more and more inquisitive over the days. For the latest, Google has new technologies appended to Google Web Toolkit. One of the top revelation from Googleplex was the new Speed Tracer tool designed to help developers speed up their web apps. The GWT would also include a code splitting tool that would allows the developers to deploy apps as incremental downloads and UiBinder, an UI framework for developers to separate the logic presentation of their apps from the layout portion. Let’s delve into the three interesting tools that could soon change the whole scenario for developers.

Speed Tracer

Out of the several new extensions for Google Chrome, Speed Tracer seems high on prospect for its unique and effectual functionality. Using the extension would not only streamline a developers job, also tracks performance over an extended period of time, as users tap into an various functions of the app. More precisely, the tool would assist in optimizing the AJAX based application. There are several other tools for speed optimization, given that they have to do with the load time.

What makes Speed Tracer standout is the fact explained by Google’s Andrew Bowers, it can track performance bottlenecks in ways that were not previously possible, because it taps into APIs that were built into Webkit for that very purpose (APIs other browser engines don’t offer).

Working with the tool will allow the developers to isolate selected functions in their app that are time consuming. It will allow them to monitor performance in real time. It will suggest that developers take a look at certain problem functions.

UiBinder Tool

Another productive tool launched by Google this evening with UiBinder. The tool as described by Bowers is a declarative UI that allows developers to bind a layout template and associate it with a Java file, without having to merge the two. Typically, developers often need to combine a typical Java file, layout portion of the application with the logic portion of the app. With UiBinder developers will be able to keep the two portion separately. This will allow the developers to tweak the layouts without having to write any logic code.

Split code Tool

This is a really exciting piece of tool on the GWT, which would guide the developers with code splitting. According to Bowers, while Google Wave team was first building Wave, the size of their JavaScript app grew to 1.4 megabytes. This was heavy and could take a long initial loading time for users.

In order to deal with this Google found a way to split code into segments and offer the portions that the users needs. This would imply that if you use Goolge Wave now, the browser would download only a specific portion of the app that could run the most basic functions. In case, you wanna access beyond that, you would have to go for Setting menu. Click the settings button to fetch the app.

The inner implication of the development. There are developers who have been successful in automating the process of splitting the code. According to Bowers Google takes a distinct approach. Google Web Toolkit will allow developers the choice to pick the function users will need to be able to access. The tool will then identify, which code corresponds to those functions.  Still the developers can choose the functions they wanna have. It is available on the app’s initial load, but the tool can manage things beyond.

YOUR VIEW POINT
NAME : (REQUIRED)
MAIL : (REQUIRED)
will not be displayed
WEBSITE : (OPTIONAL)
YOUR
COMMENT :