Archiv fÃ¼r den Monat: Februar 2010

Here are the GWT sessions on the upcoming google i/o 2010 to keep an eye on.

Google usually publishes the sessions on youtube and uploads the slides to the respective session homepage. Ray Ryan is talking on two session, one of it is called â€žArchitecting GWT applications for production at Googleâ€œ â€“ maybe it is part two of his last talk on gwt architectures best practices.

Modern web applications are quickly evolving to an architecture that has to account for the performance characteristics of the client, the server, and the global network connecting them. Should you render HTML on the server or build DOM structures with JS in the browser, or both? This session discusses this, as well as several other key architectural considerations to keep in mind when building your Next Big Thing.

How can you take advantage of new HTML5 features in your GWT applications? In this session, we answer that question in the form of demos â€” lots and lots of demos. Weâ€™ll cover examples of how to use Canvas for advanced graphics, CSS3 features, Web Workers, and more within your GWT applications.

There have been some really huge improvements in GWTâ€™s UI fundamentals over the past year. Weâ€™ve introduced features such as UiBinder, ClientBundle, CssResource, and uber layout panels that allow you to build fast UIs in a sane manner. Come see how fun/easy/fast it can be to use these technologies in harmony to overhaul your UI.

GWT has a lot of little-publicized infrastructure that can help you build apps The Right Way: test-driven development, fast continuous builds, code coverage, comprehensive unit tests, and integration testing using Selenium or WebDriver. This session will survey GWTâ€™s testing infrastructure, describe some best practices weâ€™ve developed at Google, and help you avoid common pitfalls.

For large GWT applications, thereâ€™s a lot you should think about early in the design of your project. GWT has a variety of technologies to help you, but putting it all together can be daunting. This session walks you through how teams at Google architect production-grade apps, from design to deployment, using GWT.

It turns out that web apps can be slow for all sorts of opaque and unintuitive reasons. Donâ€™t be fooled into thinking that bloated, slow JavaScript is the only culprit. This session introduces you to Speed Tracer, a new GWT tool that can tell you exactly where time is going within the browser.

The GWT compiler isnâ€™t just a Java to JavaScript transliterator. It performs many optimizations along the way. In this session, weâ€™ll show you not only the optimizations performed, but how you can get more out of the compiler itself. Learn how to speed up compiles, use -draftCompile, compile for only one locale/browser permutation, and more.

At its core GWT has a well-defined and customizable mechanism â€” called Linkers â€” that controls exactly how GWTâ€™s compiled JavaScript should be packaged, served, and run. This session will describe how to create linkers and explains some of the linkers weâ€™ve created, including a linker that turns a GWT module into an HTML5 Web Worker and one that generates an HTML App Cache manifest automatically.

I found this one here in the atlassian forums, unfortunately the link posted there is broken.

Hi guys,

We are announcing our end of life of Atlassian support for Internet Explorer 6 on JIRA.

This will be effective from the launch date of JIRA 4.2 (target Q3, 2010). This means that JIRA 4.1 will be the last version of JIRA to support IE6. (From JIRA 4.0 to JIRA 4.1, all of the main functionality will work in IE 6; however, some of the visual effects will be missing).

This year is a great year for web development. We will witness the â€žend of lifeâ€œ of IE 6. And as far as I got it right from here, IE 7 is being trashed on the same day:

13-Jul-2010
Internet Explorer 7 on Windows XP Professional Service
Internet Explorer 6 on Windows XP Professional

And sincerely: this is good. I just hope companies start upgrading soon, why should we wait until July?Â I just hope that Google, Amazon, Ebay and others take the chance to honor this date. What about turning off IE 6 support completely for a week or two? This surely would help companies to speed up transitionâ€¦

But IE 6 was not all painâ€¦ Â did you see thisÂ one here?Â So sad and funny at the same timeâ€¦ There is even a website dedicated to the IE death march!

So before you update to IE 8 I just wanted to point out thatâ€¦

Internet Explorer is a piece of software more generally called â€žweb browserâ€ž

It might come as a surprise, but the Internet Explorer is not the only browser available for Windows usersâ€¦

Sadly, Internet Explorer browser updates are the only ones the inexplicably involve updating half of the underlying OS ;-)

So, before updating, have a look at Safari, Chrome, Firefox, Opera.Â They are all far better (faster, more secure, more compliant) in browsing the web than Internet Explorer.

And you donâ€™t have to fear your OS is vulnerable or broken after installing a update.

And, just in case you missed that one: HTML5 is the next big step in the web development. Google and Apple are the key players this time. Not Microsoft. Microsoft announced that they will setup a set of tests to evaluate HTML5. And they announced that IE 9 will be able to draw round corners (this is innovation from Microsofts point of view, really).

With HTML5 we will leverage the web to next level, the new features are awesome.Â Safari, Chrome, Firefox and Opera already support the vast majority of the HTML5 features: