I think expecting a WO newby to learn WO plus WOnder concurrently
may be enough to drive some newbies to other technologies. I'm a
proponent of the KISS principle wherever possible; e.g., learn WO
basics first, then add WOnder when you understand WO basics.
Art, I think you are missing the point. Create a new Wonder app in
WOLips. That is it. That is all that you _need_ to learn to
benefit. The app has a properties file (see below) that turns on
the benefits. You can edit the properties if you do need mail or
something. But you don't have to worry about EC locking etc.
Don't do this, and _then_ how much do you need to know?
1000% agree. Wonder is designed with two goals -- 1) don't let you
shoot yourself in the foot and 2) make powerful things easier. The
idea that to achieve #1 that you must also fully achieve #2 is not
true. You use what you need. There is almost zero learning curve to
START using it. Use ERXEC.newEditingContext() instead of new
EOEditingContext(). That's it ... The other stuff was written by the
WOLips template for you.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
