4 ms·
"Class-based programming works great for GUI toolkits." I've programmed with 3 approaches to UI: every things a subclass, instance of class, and prototype-base
by protomyth 13y ago
"Class-based programming works great for GUI toolkits."
I've programmed with 3 approaches to UI: every things a subclass, instance of class, and prototype-based objects. I enjoyed programming UI on the Newton because of the prototype-based programming. It felt natural. NeXT / Apple's instance of a class works very well too.
Every time I see "every things a subclass", I wince and know its going to be a pain in the butt.
- lmm 13y agoEver use Wicket? It's an utter joy to work with, and the only framework I've found that really shows the good side of Java.
- protomyth 13y agoCannot say I have. I left Java at the 1.1 version and never made it back.
- wsc981 13y agoThat reminds me of a little quote by Aaron Hillegass in his book "Cocoa Programming for Mac OS X" (p. 73): > "Once upon a time, there was a company Taligent. Taligent was created by IBM and Apple to develop a set of tools and libraries like Cocoa. About the time Taligent reached about the peak of it's mindshare, I met one of its engineers at a trade show. I asked him to create a simple application for me: A window would appear with a button, and when the button was clicked, the words 'Hello World!' would appear in a text field. The engineer created a project and started subclassing madly: subclassing the window and the button and the event handler. The he started generating code: dozens of lines to get the button and text field on to the window. After 45 minutes, I had to leave. The app still did not work. That day, I knew that the company was doomed. A couple of years later, Taligent quietly closed its doors forever. "