Dwt has been updated to the following:

1. It now uses Git
2. Updated to GWT 1.7 with Eclipse plug-in (I currently use Galileo)
3. Updated to Dojo 1.3.2

Migrated completed a few minutes ago.

My current target is to implement the Dijit “Button” widget ASAP.

Wish me luck!

No no… don’t think that Dwt is dead just because there seems no visible activity for last two months.

In fact, I just got so busy that there was hardly any time to look into Dwt. Can’t help, I’m not 100%-time into Dwt.

Anyway… that was recent past.

Ok… now coming to the rebirth of Dwt - that I don’t think should happen again, at least in near future, here are the latest updates:

1. Focus continues to have on the core design, for the moment, to ensure that we do not have half-cooked or uncooked design.
2. Refactoring of dijit.Widget class: It does not use several class-level fields to store styleClass, dir, lang etc. It uses a HashMap<String, Object>, and additionally provides get/set apart from getXXX and setXXX.
3. Added JavaScriptObjectWrapper class since interconversion from JavaScriptObject to Java-Object was troublesome area in quite a few scenarios. The benefits will be visible at several places.
4. Refactoring of IJavaScriptFunction interface to use JavaScriptObjectWrapper class.
5. TemplatedWidget uses HashMap<String, List<Element>> for dojoAttachPoints and HashMap<String, HashMap<Integer, List<EventListener>>> as event-listeners store.
6. TemplatedWidget, at least for now - until we get the magical wand, does not support dojoAttachEvent.
7. The immediate next step is get TemplatedWidget back in shape because after these changes, the code breaks.
8. Subsequently, implement the replaceProperties method.
9. And then, provide overloaded addEventListener methods as discussed in the previous entry.

I would be committing the code sometime tomorrow. It’s been quite hectic recently.

Catch up with lot of action…