Mindless Mind©

Just yesterday I posted about “thinking” to create the Java API to work for Dojo on GWT. And today, it’s kind of official.

Edujini Labs is going to sponsor this project. Check the posting on Eduzine here.

In fact, a mail to the Dojo Team has already been sent about the intimation of the same.

Have a look at the “Hello, World!” on the early-stage DWT.

My real love for GWT started only a couple of days ago… and it prompted me to get started with Dojo on GWT.

I have, so far, written a couple of core-classes in Java mainly to abstract out the interaction with JavaScriptObject.

My next target was to directly jump on to dijit, and start creating the UI. And then I realized that it uses mixins. And now I am left wondering what’s the best way to handle mixins.

For the new comers, JavaScript allows single inheritance but Dojo (and other libraries) make use of mixins to pseudo-inherit methods and properties from other objects by copying them to the sub-object.

In Java, this can be achieved only by making use of interfaces. The other possibility is to introduce a class between the parent and the child class that encapsulates the mixin objects.

I think the latter is a better approach. Simply expose the object or may be create delegate methods.

Let me think over it… what’s the best way to marry Java and JavaScript.

On Monday, I talked about the training on Visual Studio Team System 2005 Extensibility and I said that I would probably post across a sample piece of code.

But I did not get time.

What more interests me is the web. And there is Google Web Toolkit to help us write structured JavaScript in Java. Sounds great, isn’t it?

So, what I did was to quickly compile a couple of articles on GWT and post at Eduzine™ here and here.

Enjoy working with Google Web Toolkit, JavaScript and Ajax!