Re: EO & WebServices
Re: EO & WebServices
- Subject: Re: EO & WebServices
- From: Lotsa Cabo <email@hidden>
- Date: Tue, 27 Jan 2004 07:50:52 -0500
By "wizard" I mean any technology that automate or otherwise "handles"
a task so a developer will not have to code the same. This could be a
traditional step-by-step question/answer dialog that later spits out
code. A wizard could also be a rules-based system that automates a
task on one system that may otherwise need to be manually coded on
another.
Our logic with NOT using D2W is that certain pieces will be handled
through this rules base system and, therefore, not coded by our
developers. This will force us to be locked in to the WebObjects
platform much more tightly then we can afford at this stage.
Additionally, since all of our folks are .NET guys, by letting WO
handle tasks that would have otherwise been coded by hand, our
developers are not learning as much as they could have.
Simply put, if the D2W functionality allows us to create a block of
code that can later be manipulated without using D2W, then great. But
if any of the D2W UIs will be used in the future to update, enhance, or
troubleshoot the product, we cannot use it.
So, next idea?
R/S
Ryan
On Jan 27, 2004, at 2:39 AM, Anjo Krank wrote:
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.