Re: Cocoa downgrade from openstep?
Re: Cocoa downgrade from openstep?
- Subject: Re: Cocoa downgrade from openstep?
- From: Jean-François Veillette <email@hidden>
- Date: Fri, 10 Aug 2001 10:27:22 -0400
I also have concern about coding style ...
Openstep made eavy use of delegation, very few subclassing.
WebObjects came in and started to use subclassing instead. I was told
this was because developer where having hard time getting the concept
of delegation, that delegation was slowing the learning curve. I'm
earning money working with WebObjects now. All I will say, is that I
prefer delegation style over subclassing style. It is simpler (ok,
probably harder to understand if you come from C++ or Java) and better
encapsulate the oo principle (if done right, as AppKit was done).
With new Cocoa classes like NSDocuments (and friends) using subclassing
over delegation, I wonder if on long term we are going to loose the
elegance that AppKit had. Sure subclassing can work just as well, only
in a different mind set. Is Cocoa officialy going "subclassing
style" ? Please tell me it is not.
After thinking about what I wrote ...
now that EOF is gone, will Cocoa reintegrate the concept that was
EOAssociation, and all the EOInterface layer that was mostly usable
outside an EOF centric (db driven application, with all the EOF stack)
application?
EOInterface layer provided a mean for connecting "generic data" with
"generic UI", not just EO to UI. Well ... yes, just to EO because they
had to have KeyValueCoding, but that could be anything.
EOF is an example of a Kit that went beyond AppKit, but at the same time
extended it nicely.
Are those features gone for good ? Can we expect a new
Generic_DataSource_Interface framework ?
... obviously I would prefer to have all EOF frameworks back :-)
- jfv