On Mar 20, 2008, at 2:59 PM, Guido Neitzer wrote:
On 20.03.2008, at 14:20, Mr. Pierre Frisch wrote:
I would totally disagree with that. Wonder introduce another layer
of complexity and patching on top of WO.
That is just not true. When you add Wonder to an existing, complex
application that does a lot of the stuff Wonder does - maybe.
That is true. Which is why I pick and choose which parts of Wonder I
use - it has to co-exist with our frameworks. But the important point
here is that I _can_ pick and choose.
But only maybe. If you start fresh - it's way better to get the bugs
that exist fixed and the features that are missing in WO with Wonder.
You would have to be NUTS to start a new project and not use Wonder or
the GVC frameworks or _something_ that does this stuff for you.
Wonder is the least pain of the ones that I know.
Just for autolocking and the localization support it's worth using
Wonder.
You might have a different opinion, but there are bugs in WO and
Wonder fixes some of them. And there are missing features in WO and
Wonder provides them. So, from an Apple perspective, you might not
like that, but from a user's perspective, the value Wonder adds is
incredibly time saving.
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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]
