Re: EO & WebServices
Re: EO & WebServices
- Subject: Re: EO & WebServices
- From: Anjo Krank <email@hidden>
- Date: Tue, 27 Jan 2004 08:39:45 +0100
- Xx-reply-to: email@hidden
Am 27.01.2004 um 04:00 schrieb Lotsa Cabo:
Been there, done that with the assistance thing. I'd love to find
someone else, but finances don't really permit it at this stage.
The requirement of not using the Direct to Web stuff is from
professional dependancies. Meaning, we need to understand every line
(or at least 99%) of code so that we can fix and enhance the product
in the future WITHOUT the use of wizards. Simply put, if something
breaks where we do not have access to the wizards, we will need to fix
it. Likewise, if a client requests a tweak somewhere in the field, we
MAY have to do it somehow manually.
Make sense?
No, not really. The assistant (not "wizard") is one front end to a very
powerful rule system that actually does the work. These rule files can
be edited with the RuleEditor app, too, so you are not really dependant
on the assistant.
However, D2W *is* pretty complex and its workings are not really
trivial to understand. I recommend the chapters dealing with it from
the Wrox book.
David Teran will demo a very cool project at the Wocoa where D2W is
used to spew out XML, defining the UI that is later processed with XSLT
to the final HTML. Very cool, flexible and powerful.
My approach would be to define the page flow in WO and the edit and
list pages as D2W components. This will alleviate the need to plug into
the flow of D2W, while stil sparing the hassle to create all the HTML
by yourself.
Cheers, Anjo
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.