It's definitely CSS for objects.
But in a sense it is also WO square: D2W = WO^2.
That's because in concept D2W applies WebObject's page generation
mechanism once more, at the component level. Instead of having to
program an editor component for every entity in your model you use a
generic editor that depending on the entity will show matching
attribute editing fields.This reduces the number of pages you need to
handcraft by a factor! The square factor :-)
Rudi Angela
On May 19, 2006, at 19:51, Pierce T. Wetter III wrote:
On May 19, 2006, at 9:53 AM, David Holt wrote:
After reading all the Direct to Web stuff I could get my hands on,
I was trying to describe to my boss why we need to be looking at
it and moving towards it. The metaphor I came up with was that D2W
is like CSS for objects. I think that sort of describes its power,
but I would be interested in how others make the argument for (ER)
D2W to non-programmers (or programmers for that matter!).
CSS for objects is a pretty good one-line answer.
A longer one would be that D2W lets you describe the meta
information about an object: How to format its data, how to label
it, what data should be editable, etc. It can then build user
interface from that description.
Pierce
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/blue.moon%
40tiscali.nl
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to archive@mail-archive.com
