Mindless Mind©

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.

Without any introduction, let me just list down some intersting events of the day…

Reached the entry gate of the company premises only to find that the contact person is on leave.

The contact person did not delegate his responsibilities, if at all any, to somebody else.

Upon reaching the training room, there was not a single computer for the audience to lay hands on for the case studies. Hey, you know that it’s an IT Training.

(more…)

Yes, that’s what I am doing for couple of days.

No, it’s not about customizing how TFS works but looking at the integration points. In short, the TFS SDK.

The following items are the items on my radar immediately:

• Customizing WorkItem Types
• Creating custom fields
• Creating custom UI controls during WorkItem display in Visual Studio
• Creating custom check-in policies
• And making all of them backed by some database?

Well, I have already worked with the first two items - creating custom fields and customizing WorkItem types, predominantly using custom fields and choosing the layout - several times.

Now, I need to master the remaining items.

And yes, it’s mainly for Edujini™, my baby. So, what I promise is that once I am through with my experiments, I will publish them at Eduzine™ and Edujini Downloads™.

When I started my day yesterday, I thought I would be going off to a great day ahead for my training.

The Monday evening, I was severly troubled because of the red-burning-eyes and severe headache caused due to inefficient and insufficient lighting in the training room. As such, I did nothing in the evening but took dinner and went off to a long sleep.

Reaching the venue, I noticed that not all machines were properly configured, yet. We spent another 1hr for the setup - just to ensure that we get going as quickly as possible and do not waste more time.

And by the end of the day, I figured out that we are running late by around 4hrs or so. Really, couldn’t see any hope to recover that time anywhere.

So, here’s a list of things that you must take care of before / during the training:

• There should be appropriate and sufficient ligthing
• There should be lights focussed at your laptop screen, to say the minimum, lest your eyes get strained
• The screen should be sufficiently large
• The maximum distance between the screen and the participant should be such that he is able to view any content / text / code written at font-size of 14-16.

If not, be prepare to strain yourself and get doomed!