point
The Smart Techie was renamed Siliconindia India Edition starting Feb 2012 to continue the nearly two decade track record of excellence of our US edition.

June - 2008 - issue > Technology

JBuilder 2008:Focusing on code reuse

Jayakishore Bayadi
Friday, May 30, 2008
Jayakishore Bayadi
Say, you are building a house and struggling to visualize the interior of it. The cost may pinch if you go to a designer. What can be done? You may visit your friend’s house and try to bring some of the design aspects of his house to your house and adapt the same according to your requirement and suitability. In essence, you’ve saved lot of money, time and energy, which otherwise you would have put to design your interior.

Now, apply the same analogy to software development. Every time a new software or application is developed one need not have to begin it from scratch. Already there are trillions of codes available that were used to develop millions of software and applications. Why can’t we use them while developing new software?

CodeGear, a subsidiary of Borland Software, has come up with a concept that is similar to this. With its newly released JBuilder 2008, the company claims that it has added a methodology and tools called “Application Factories” for simplifying code development to its flagship integrated development environment (IDE).

“Application Factories is a fresh method to help Java developers to better navigate the range of complex framework choices, open source, internal code, and deregulated technology standards available for reuse in order to deliver quality solutions quickly,” states Ravi Kumar, Principal Architect, CodeGear.

Application Factories fosters reusable developer intelligence that can make developers more productive and speed up projects, especially among fluid, globally distributed teams. David Intersimone, VP, Developer Relations and Chief Evangelist, CodeGear, says, “What we have to look at is the ways in which we can reuse components or modules to save the developers having to write from scratch. What we’ve done is that we have packaged that ability into a single repository so that developers are presented with views of all modules that are available.”


Share on Twitter
Share on LinkedIn
Share on facebook