At 12:17 PM -0800 3/19/99, Derek Eide wrote:
> I guess when I take a good look at Web Objects as a whole, I think of it as
> this very well built, well organized, powerful application server with poor
> documentation. What *could* happen is companies like SAMS Net, O'Reilly,
> and whoever else could come along and save us all with wonderfully
> descriptive reference books. But shouldn't the basic functions of all of
> their classes be properly documented? Shouldn't at least half of the
> hyperlinks work? Try finding info on some of the custom WO components...
> like type in WODictionaryRepetition into the WOInfoCenter search. Hell, I
> didn't even know there was such thing as a dictionary repetition.
> Previously, I just hacked my way around it. I've taken both levels of
> their training courses and during each, the documentation was quite
> the issue.
WODictionaryRepetition is in WOExtensions (I just found these today, jeesh.)
Its funny, because the 4.0 additions to WOExtensions are documented
in the "Whats New in 4.0" pages, but the 3.5 WOExtensions don't seem
to be.
Even better, the WO Developer guide says "The first thing you
should do is document your custom component". Yet I couldn't find any
documentation for WOToOneRelationship ( I did a find by content on
/System/Documentation.)
Its funny, because I see the WO learning curve as:
Step #1: WebObjects alone, write an app with no persistance.
Step #2: WOF + EOF, write an app that reads/writes from a DB or file.
Step #3: WOF + EOF + Components.
Write a bunch of components that automate standard tasks for you.
Like: WOToOneRelationship
Assemble those components into an app.
Step #4: WOF + EOF + Components + hard core EOF
Do step #3, but now use a lot of EOF directly instead of indirectly
to make your app more polished (Sort on multiple keys, etc.)
The docs take you to step #2, unless you're the type of person that
starts at the top of the class hierarchy, and reads every single
class description...
Reading the source to the WOExtensions library gets you to step #3
(the chapter on writing reusable components wasn't very useful IMHO,
but a working example was.)
I'm not sure how you get to Step #4. :-) Perhaps reading the output
of the Direct2Web stuff?
Pierce
----------------------------------------------------------------
Pierce T. Wetter III, Director, Twin Forces, Inc.
e-mail: [EMAIL PROTECTED] Phone:520-779-4227
<http://www.twinforces.com/>
U.S. Mail: 1300 South Milton Rd, Suite 206, Flagstaff, AZ 86001
