On Jun 20, 2006, at 10:29 AM, Guido Neitzer wrote:
On 20.06.2006, at 19:14 Uhr, Pierce T. Wetter III wrote:
For that matter, there's always WOSwitchComponent. At my site
90% of the look/feel is one component called "PortfolioFrame",
which is the basic wrapper for every page.
Isn't that what WOComponentContent is for? I use WOSwitchComponent
for example in lists with mixed EOs where I set the table row (or
its content) as a WOSwitchComponent and insert the appropriate
component to show a row for a given entity.
Yep, PortfolioFrame is basically the boilerplate for the page
(HEAD/BODY tags, etc.) wrapped around a WOComponentContent tag. But I
could replace PortfolioFrame with a WOSwitchComponent wrapped around
a WOComponentContent, and then have 3 different PortfolioFrame clones
instead.
In fact, PortfolioFrame already does this to distinguish between
pages you have to be logged into to view and pages where that isn't
true.
Pierce
WOTip: Use a direct action unless a <FORM> tag or Ajax was involved
somewhere.
More Tips: http://www.twinforces.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [email protected]
