Hallelujah, Praise the Lord, and Amen!

I agree with you 110%.

EOF, WOF and Foundation are great tools once you become familiar with them,
but they are so far ahead of, and therefore completely unlike anything else
out there that it is very easy to get confused if you do anything out of of
the ordinary.

One of the strengths of a tool like Cold Fusion, even though it is a piece
of crap, is that you can go to their web site and download literally
hundreds of modules which been contributed by third-party developers.  There
are also extensive examples, tutorials, online discussions, etc.  So for any
particular task you want to accomplish in Cold Fusion there are 10 different
suggestions on how to do it.

BTW, I made an attempt to put together a FAQ a year or so ago.  I culled the
list archives and came up with about 50 questions, which are posted at
http://www.wosource.com.  If people would like to help me revise, update and
extend this that would be great.

Bruce Fancher

Bruce Fancher

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of matt kangas
> Sent: Wednesday, March 17, 1999 2:04 AM
> To: Multiple recipients of list
> Subject: We need a WOCookbook!
>
>
> (foreword: yup, this should go in webobjects-talk when it's available.
> This is an opinion on how Apple could improve its WO documentation.)
>
> What WebObjects needs is not another manual, or another FAQ... what it
> needs is a good cookbook! aka a patterns book. (but "cookbook" sounds so
> much friendlier :)
>
>
> Allow me to elaborate...
>
> I just spent the evening pondering a component-nesting issue that's been
> bugging me for several months now. I've known all this time that I'm going
> about this in a bass-ackwards fashion in one of my programs, yet a
> functional and elegant solution has always eluded me. But tonight I
> started thinking about this again, writing down the exact things I want to
> accomplish with this and going over the WO dev guide & "What's new in WO4"
> doc with a fine-tooth comb. In the end I realized that the
> "carat notation" for non-sync components is all I really need for this.
>
> Or today I replied to Patrick Robinson's question on this forum, but it
> seems he has a more general issue:
>
> > Date: Tue, 16 Mar 1999 21:29:03 -0500 (EST)
> > From: Patrick Robinson <[EMAIL PROTECTED]>
> > To: matt kangas <[EMAIL PROTECTED]>
> > Subject: Re: how to trim leading and trailing spaces?
> > ...
> > I really just want to post-process the user input value.  Maybe a
> > validator is where this behavior belongs, but I can't believe this
> > isn't something that's much more commonly done, so that it's readily
> > available.
>
> AFAIK the common thread in these examples is that we're both looking for
> some input on *strategies* and common implementations for resolving a
> problem based on a set of requirements.
>
> An aside: Does the WO documentation suck or does it not? Depends on how
> you look at it. The WO Dev Guide makes for nice reading, but if you have
> a "How do I?" question the answer is (IMHO) often very hard to find in
> this book. Often what you really need to look it are the Foundation/EOF/WO
> references, but there is no coaching to this effect... the WO Dev Guide
> should at have a chapter explaining what kind of Qs are answered by the
> refs and how to find/navigate them.
>
> So, assuming this issue was resolved, there still seems to be a great need
> for an "Ask the Guru" book. Yes, this list is *wonderful* for exactly this
> purpose and trawling the archives is tremendously handy, but it is neither
> a) concise & authorative, nor
> b) an Apple publication
>
> I think lots of people get lost in WO trying to do what seem to be "simple
> things", running into a problem and not having a clue how to solve it. I
> also thing this points to a deficiency in Apple's documentation which, if
> resolved, would help more people grok WO more quickly.
>
> Humbly submitted for the betterment of us all...
>
> --
>  \7\3\d\e\k\b\8\u\o\x\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
> \m\a\t\t\.\k\a\n\g\a\s\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
> m\a\t\t\@\k\a\n\g\a\s\.\o\r\g\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
>

Reply via email to