A Conversation With Creator’s Creator



Email    print   
October 15, 2005 —  (Page 1 of 3)
A few weeks ago, I wrote about my disappointment with Sun’s Studio Creator. My main problem is Creator’s flavor of model-view-controller, which puts a straitjacket on the tool, preventing you from using a more flexible (and more object-oriented) UI architecture, such as Presentation Abstraction Control. The net effect of this tight coupling it that your Creator application is doomed to a life of difficult maintenance because the UI is too tightly coupled to both the underlying database and to the implementation of the application-level classes. (I should say that the real flaw is the JSF framework that underlies Creator—most of the commonly used UI frameworks, including JSF and Struts, are not particularly well thought out.)

Well, Sun called me up to arrange an interview with Craig McClanahan, Studio Creator’s architect. Interestingly, the software we used during the interview was as interesting as the interview itself—more on that in a moment. McClanahan’s motive was to prove to me that I could do what I wanted to do using Creator. In fact, you can get about halfway there, but I’m still not sold.

In the most successful systems I’ve written, the objects that constituted the “business logic” were responsible for creating that part of the user interface that represented their own state. Think of it as if every object has a “display yourself” method. (That’s obviously not how a real system works—real systems use things like the Gang-of-Four “Builder” design pattern to separate business and representation logic, and they can represent attributes of themselves with finer granularity—but it’s a good conceptual model.)

Studio Creator’s main flaw is that you must lay out widgets on the screen and then hook those widgets up to the object. If the object’s implementation changes, then all of the infrastructure that hooks up the object to the widget is now broken. I, on the other hand, want all changes to an object to be localized in a single place—ideally a single class definition and its inner classes. If the class definition changes, the UI should scale automatically. Studio Creator won’t do that because that’s not the way model-view-controller works.




Pages 1 2 3 


Share this link: http://sdt.bz/28924
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Illumination Software Creator 4.2 adds 'Portal Blocks'
Radical Breeze today released version 4.2 of Illumination Software Creator for Linux, MacOS X and Windows Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb