Re: Documentation frustrations
Re: Documentation frustrations
- Subject: Re: Documentation frustrations
- From: Steve Weller <email@hidden>
- Date: Sun, 10 Jul 2005 19:57:47 -0700
At 3:41 PM -0700 7/10/05, mmalcolm crawford wrote:
On Jul 10, 2005, at 3:12 PM, Steve Weller wrote:
* Give some example programs that instead of using complexity to
show off how clever the tools (such as Core Data) are, use
simplicity to show how they work.
Do you have specific instances that you think are showing off rather
than showing?
Event Manager is an example.
I'll turn this around and tell you what I am looking for. Create a
single entity with one attribute. What does this get me that I cannot
get by using a different method? Use examples that do the same thing
in different ways so that the reader understands what core data is
doing for them. Explore this staggeringly simple case by playing with
all the check boxes and fields that describe the attribute and
showing how the behavior changes. Store in persistent storage,
exercise undo, do fetches. Create a custom class.
Now add a second attribute and repeat. Now add a relationship that
points back to the same entity. Repeat. Show all the delete modes.
Add another entity. Repeat with a one-way and two-way relationship.
Finally introduce to-many relationships, then inverses for those. Now
the learner may be ready for Event Manager.
My rationale for jumping into Core Data with both feet is that if I
am to write a new app with no legacy and I have no legacy thinking in
my head I want to use the most powerful tool first and then move to
less powerful tools to fill in the parts that it cannot do. I think
this is the route that many others will follow.
--
How much art could an artichoke choke if an artichoke could choke art?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden