tag:blogger.com,1999:blog-50798092011-12-18T15:01:00.291ZDevelopment stuffDavidnoreply@blogger.comBlogger131100tag:blogger.com,1999:blog-5079809.post-29593323923191158052010-03-03T16:23:00.000Z2010-03-03T16:28:28.089Z

Introduction GWT 2 has introduced the concept of declarative interfaces, that is, the interface can be described via an XML document, rather than built using code. The idea isn't new, it's seen in many new technologies such as Macromedia Flex, ASP.Net and JavaFX, however to the GWT developer it means the end of writing reams of boiler plate code. In this post I show you how to create a simple

Davidnoreply@blogger.com1tag:blogger.com,1999:blog-5079809.post-6180460227329578832010-02-24T11:55:00.012Z2010-02-26T10:19:57.477Z

Introduction In a previous post I showed how to create a custom GWT component based on GWT 1.7. In this post I'll show you how to perform the same thing using GWT 2's new event system. In order to make clear how custom GWT events are built, I'll be doing things slightly differently in that we'll be building it in a Model-Binder-View style. The Model The model is where we're going to

Davidnoreply@blogger.com8tag:blogger.com,1999:blog-5079809.post-88287171288205015992009-09-21T21:52:00.006Z2009-09-21T22:05:02.422Z

For the last few weeks I've been experimenting with Opera Unite, due to be release in the next version of the Opera browser. Opera Unite services are built in JavaScript, however this felt like a limitation as building anything big in JavaScript alone can get a little hairy. With this in mind I started on a few experiments to see if I could use GWT as a framework to build these services, thus

Davidnoreply@blogger.com0tag:blogger.com,1999:blog-5079809.post-82339168478847610442009-07-04T20:23:00.001Z2009-07-04T20:28:12.506Z

Logging is an essential component of any traditional Java environment, without it, tracking down issues would be time consuming. Unfortunately, on the browser, there's no standard place in which to output log messages. Sure, one solution could be to display a dialog box when something goes wrong, but normally you want to dsplay such things as debug messages which just won't work in a dialog

Davidnoreply@blogger.com0tag:blogger.com,1999:blog-5079809.post-58676651386966217682009-06-19T07:49:00.008Z2009-06-19T08:37:26.416Z

Google Visualization is an excellent API for adding graphing capabilities to any web application. Recently a GWT wrapper has been released which makes it easy to embed this API into GWT applications. The GWT module is really a wrapper around the standard Visualization JavaScript libraries and in order for everything to work the documentation says the following line is required in your GWT

Davidnoreply@blogger.com1tag:blogger.com,1999:blog-5079809.post-40248906267342437362009-01-30T13:05:00.006Z2009-01-30T13:10:33.170Z

This morning I spent over an hour tracking down and solving a client/server communication issue which I'm going to document here, for all weary travellers who come this way. The application in question uses the GWT RequestBuilder in order to make an HTTP GET request to the server. When running in GWT Hosted mode I have a relay servlet that acts as a proxy allowing me to test the application

Davidnoreply@blogger.com2tag:blogger.com,1999:blog-5079809.post-82925926348918783782009-01-24T10:15:00.011Z2009-01-26T11:03:01.244Z

Since Java is a statically typed language, the compiler is pretty good at spotting errors, but sometimes we do things that are syntactically correct, but which are semantically wrong; take for example the following code sample. public class TestError { String personName; public TestError(String personName) { personName = persionName; } public int getNameSize() { return

Davidnoreply@blogger.com2tag:blogger.com,1999:blog-5079809.post-10797820074235342472009-01-20T13:13:00.020Z2009-06-19T08:50:22.517Z

GWT widgets are the visible elements of a GWT application and so it's quite important to understand how they work. In a previous post I explained the rendering process but here we get a little less abstract by actually creating a simple GWT component. On the way we'll also look at using Java 1.5 Enums to great effect in order to reduce the amount of runtime errors our browser app may have. I've

Davidnoreply@blogger.com11tag:blogger.com,1999:blog-5079809.post-90643973893499411642009-01-17T14:35:00.008Z2009-01-17T15:17:45.733Z

Yahoo Pipes is something I've been meaning to get to grips with for quite a while but just never had the right application for it. However before heading home last night I did my quick check of the tube status page for any usual problems and it suddenly hit me, wouldn't it be great if this information was machine readable! I raced home and checked around to see if something similar had already

Davidnoreply@blogger.com1tag:blogger.com,1999:blog-5079809.post-67767199965949642272009-01-12T14:52:00.023Z2009-01-13T21:30:56.997Z

We're all told that browsers differ in their interpretation and rendering of HTML but sometimes it's hard to find a simple concrete example. Recently I decided to remind myself of everything HTML has to offer and re-read the HTML 4 specification. The HTML 4 specification was published in 1999 so you'd think that all current modern browsers would support it fully, but you would be very wrong.The

Davidnoreply@blogger.com2tag:blogger.com,1999:blog-5079809.post-57479871247438268922009-01-08T13:11:00.010Z2009-01-08T14:42:44.319Z

I take quite a few photos, admittedly not as many as I'd like, but that's another story. All these photos need to be stored somewhere which leads to an escalating amount of disk/backup space being used. Over the years there has been the inevitable copy made of a photo, along with re-importing the same photos again from an SD card that wasn't cleaned down. All these leads to quite a bit of disk

Davidnoreply@blogger.com0tag:blogger.com,1999:blog-5079809.post-30782899895351934192009-01-02T14:38:00.020Z2009-01-05T11:41:07.130Z

GWT uses CSS styling in order to format rendered widgets, but since your abstracted away from the underlying DOM, it can sometimes be hard to create the exact CSS rule.  I recently created a composite GXT component and as a result couldn't quite get the CSS rule correct, (as it turns out, it was a rogue DIV element messing things up).  The following shows how to use some advanced features of the

Davidnoreply@blogger.com1tag:blogger.com,1999:blog-5079809.post-55029839379545158202008-12-27T22:42:00.036Z2009-01-02T22:08:41.273Z

The project I'm currently working on uses GWT and GXT and so I decided to dig into the frameworks to figure out how the both perform their magic of turning Java components into HTML elements. Since I've done the work, I thought I may as well share it incase anybody else is curious!GWT RenderingIn order for GWT to render any component it MUST be added to the RootPanel, which is just a standard

Davidnoreply@blogger.com2