Feeds:
Posts
Comments

Posts Tagged ‘gwtClassRun’

The logo image45is designed on 16 May 2008 around 9:30am and it takes several paper prototype within a hour to come out this design.  The original design comprise of just purely text and is plain ugly. My intention is to deliver a working gwtClassRun first with all the functionality tentatively then spend some times along the way to spice up the cosmetic. Unfortunately, the logo is just too plain ugly to ignore. So how did I come such design ? This design is developed using Xara Studio which offers a real time view of graphics manipulation and effect. Due to unfamiliarity with the tool forces me to think out a simple and easy design that can be quickly mock up with the tool. So it begin by experimenting with Xara’s tools and find that it is intriguing to use circle within circle as logo.

This is how the logo is been interpreted. It requires some creativity and imagination but never mind, this is okay for me as I love to day-dream and wander my mind to lalaland Embarrassed. Each class is represented as a circle. Any Java application is actually comprises of many classes of various complexity and composition, and so one class ‘compose’ the other as depicts in the logo. And been circle means that it rolls fast just like a wheel. It runs like a wheel as metaphor and therefore Runnable class is EntryPoint class. Yellow gradient is used because Yellow is light and non-threatening, and it mix well with the gwt text. gwt text is placed there to indicate these EntryPoint class circle representative is pertaining to GWT. gwt is lowercase because it syncs with name gwtClassRun.

So how does the name gwtClassRun evolves ? In fact, this no brainer as it is about EntryPoint class execution, therefore it is easy to come out a list of name initially like

GWT RunClass

GWT ClassRunner

GWT ClassSwitcher

GWT ClassSwitch

ClassSwitch might reflect what it does accurately however it just too long and seem weird with two W. gwtClassSwitch.

So in the end gwtClassRun wins because it is shorter, fluent and easier to understand. The lowercase of GWT comes about as I surf the net to seek inspiration from existing artwork that pertain to GWT like extension eg. I came across gwtExt and it seems to me that such lowercase single-word naming is prevalent for product relating to GWT. Hence, GWT ClassRun becomes gwtClassRun, and I really like the new name. Capital letter words are somehow distractive and too standout. Since GWT is already so popular, why not give other product name visibility ? So I guess putting gwt as lower prefix really is attractive and suitable.

Read Full Post »

Demonstration of gwtClassRun

Vodpod videos no longer available.

After weeks of development  and preparation in the midst of other commitments, image45gwtClassRun image10 ,  as a side project,  is finally released in beta. The work begin on 24 April 2008 after around the week I suggest a proposal entitled Improving the development experience of Google Web Toolkit to propose a better way of building GWT application by making it easy to run a EntryPoint class so as not to consume too much time testing unnecessary integration. This is particular relevant as the compilation and execution times increase as GWT application becomes larger subsequently. So to manage the expectation, it might not be feasible to continue to rely on GWT team to improve the performance because each version of GWT takes few months for improved releases. Thus a viable option is to break GWT application down in each testable class that faster to test and perform integrated testing when necessary.

The proposal suggests that a “executable” GWT class is identified with its own main method similarly to a normal Java class that executed by a JVM. This required a standard method call that support across IDEs and the probability of such support is slim as it requires too much too work to gain such rapport. Before this, the use of EntryPoint is considered as a replacement for main method however GWT supports multiple EntryPoints , and there is a possibility for developers to depend on the order of EntryPoints for Initialization, and probably end up creating more problems than it solves. AFter playing around with gwt.xml descriptor file and understand it better, I figure that it just be easier and more effective to make use of EntryPoint tag so as not to introduce complication and unnecessary changes to GWT’s way of working, and maybe that’s what GWT team is thinking all this while.

After weeks of experimentation, development and testing, gwtClassRun is done as bug free as possible. The initial platform is Windows, and if reception is good, likely to port to other platform like MacOS and Linux. Since this application is written in pure Java without using any native OS call, the port shall not impose too much change. What is more problematic is probably file and directory handling. Anyway, gwtClassRun is officially released as beta test today and just have to wait and see how other GWT developers respond to it. In the mean time, I will take a good rest to day-dream and continue further work on other remaining projects that will be released in GeekyWare.

Read Full Post »