One way to think of WOComponentContent is to consider a WORepetition.
You have an iterator around a hunk of HTML. Other Web technologies
have similar things. Well, how would you go about implementing
something like that?
WOComponentContent allows you to make your own thing that wraps other
pieces of HTML.
-arturo
On Nov 13, 2005, at 2:17 PM, Gavin Eadie wrote:
At 10:20 AM -0800 11/13/05, Chuck Hill wrote:
It can be hard to wrap your mind around it, though.
... yes, it takes a little while till the brain snaps into place, but
it's very powerful. Here's a tiny example to make it more real.
Note that the Wrap component carries the standard look and feel of
your page 'template' and contains a header, footer and menu (just for
the sake of having something a little more complex) plus the
WOComponentContent in the place where you want all the non templated
content to appear. Main and More carry that content and refer to the
Wrap, this way, whatever HTML that More and Main render will appear in
the WOComponentContent place in Wrap. Final note: ONLY Wrap is a full
page, ALL the other components are partial, so any HTML headers that
you want to use on every page only need to be in Wrap ...
Gav<WOComponentContentDemo.zip>
_______________________________________________
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/
arturo%40ethicist.net
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
