• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: State of Cocoa adoption
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: State of Cocoa adoption


  • Subject: Re: State of Cocoa adoption
  • From: Chris Meyer <email@hidden>
  • Date: Mon, 17 Mar 2003 11:17:30 -0800

Hi Jonathan,

Is it possible to give a link to a (concise?) description of EOInterface that you're talking about? I did a quick search of the web but couldn't find anything that seemed like it would do the things you're talking about... but it sounds really cool, if only as another way to look at the problem or an educational experience.

- Chris Meyer, LQ Graphics, Inc.

On Sunday, March 16, 2003, at 07:13 PM, Jonathan Hendry wrote:

On Saturday, Mar 15, 2003, at 16:38 America/New_York, Don Yacktman wrote:


I've repeatedly told a variety of people at Apple that if they just renamed EOF they'd be able to avoid that enterprise focus and at the same time make it more clear to developers just what this software is for and how it can be useful. There's a lot of programmers out there that hear "Enterprise Objects" and think it wouldn't be useful to them, yet there's some stuff in EOF that would be useful in EVERY Cocoa app written, especially the EOInterface layer!

Agreed.

For anyone who has worked through the Hillegass and/or other Cocoa
books: You know all that tedious code in the Controller layer classes,
the IB widget target (foo:sender) methods which just invoked an
analogous method in the model class, to set an attribute in the
model class? In other words, all that code meant to get information
from the UI to the Model classes?

That code pretty much goes away. Lots of code goes away. You
just associate a UI widget (like a field) with an attribute from the
model class, and things just get taken care of.

PLEASE, Apple, at least bring back EOInterface.

--
Jonathan W. Hendry NeXTSTEP/OpenStep/Cocoa
email@hidden programmer in Connecticut
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: State of Cocoa adoption
      • From: Finlay Dobbie <email@hidden>
References: 
 >Re: State of Cocoa adoption (From: Jonathan Hendry <email@hidden>)

  • Prev by Date: Re: [fixed]Programatically hiding Tablview column headers?
  • Next by Date: Re: State of Cocoa adoption
  • Previous by thread: Re: State of Cocoa adoption
  • Next by thread: Re: State of Cocoa adoption
  • Index(es):
    • Date
    • Thread