SWT is the base UI toolkit to create the UI, mainly the native widgets. Then there is JFace, an abstraction that sits on top of JFace (a large part of it) and adds power to native widgets. And finally, there is Eclipse Plug-in Framework that helps creating applications in a modular fashion. Default implementation of the Eclipse Workbench (the main UI cockpit) uses SWT and JFace for its UI.
Following the tradition started few decades back, we start with "Hello, World!" application.
In the third and last article of the series of "Exploring OOPS - JavaScript Style", we look at polymorphism in JavaScript.
Polymorphism literally means "multiple forms". In OOAD, it means that an object reference can take different behave differently depending upon the scenario.
Technically, there are two types of polymorphism - compile-time polymorphism and runtime polymorphism. One of the ways to implement compile-time polymorphism is method overloading while runtime polymorphism can be implemented by method overriding.
Downloads
The downloads are available in the Downloads area.
In the second article of the series of "Exploring OOPS - JavaScript Style", we look at how inheritance is implemented in JavaScript.
Inheritance can be described as reusability by virtue of heritage. An inherited data-type automatically obtains the functionality defined in the data-types from which it inherits.
JavaScript supports single inheritance, i.e., you can inherit from maximum one type. Also, it does not support the concept of interface introduced in languages like Java, C# to support multiple inheritance.
In JavaScript what we have is instance-inheritance (or runtime inheritance) rather than class-inheritance (or compile-time inheritance) making inheritance more powerful than probably any other language around (barring the ones like Smalltalk)!
Downloads
The downloads are available in the Downloads area.
In the Part 1 of the series, we learnt how to get started with creating custom UI widgets using Dojo Toolkit. In Part 2, learn to separate the UI from the business logic. Technically, we learn how to use templates to design the UI using simple HTML while keeping the functionality as separate JavaScript code.
Downloads
The downloads, as ever, are available in the downloads area.
Templated Widgets
Dijit sub-framework in Dojo Toolkit provides a support for templated widgets through the object dijit._Templated. Well, we do not inherit this but use as a mixin and choose dijit._Widget as the parent object.
Did you know that the Edujini Gang is working on Dojo for more than a year now! Surprising right? Since there has been not a single entry on Dojo until the recent the recent announcement of the Project DWT (Dojo on Google Web Toolkit).
Introduction
Dojo Toolkit offers a simple yet powerful architecture to be able to create custom widgets. In Part 1 of the series of articles, we look at how to create a custom widget - probably with minimal styling and functionality.
Downloads
Yo! Buddy. The downloads are available in the downloads area.
This is the updated version of the announcement - the License has been changed to New BSD
To take the development experience with Dojo Toolkit on to the next level using Google Web Toolkit, Edujini™ Labs plans to port Dojo Toolkit for GWT.
The project would soon be hosted at SourceForge under both GPL v2/3 New BSD and commercial license. We have sought for the project name "DWT" (applied under APT process, and may take 2-3 weeks for complete takeover).
The project would be led by Gaurav Vaish, initially supported by core team comprising of
Abdul Prodhani
Hair S Nair
Shake Sajan
To get started, a quick proof-of-concept demo has been created. It's not a very clean implementation - just a get started stuff.
You can support this project by spreading the word, to start with . Just "Digg It". Some people have reported problems with Digging the articles on Eduzine... if that's the case with you, "Digg This" - http://blogs.edujini-labs.com/2008/05/30/dwt/
In Part 2 of the series of articles on "Flex Data Driven Controls", we learn about how to provide custom rendering to a data bound control. And we choose List.
In the previous article, Part 1 of the series, we got ourselves started with data driven controls - ComboBox and DataGrid. In this article, we will lean to cutomize the how the items are finally presented to the end user.
The source code for this article is available in the Downloads area.
Data driven controls are key to any UI toolkit, and Adobe Flex is no different.
In this article, we explore some data driven controls in Flex and look at their basic functionalities, especially the data binding and custom rendering.
In case you need a professional support on RIA, Web 2.0 and/or Adobe Flex, feel free to mail