On May 2, 2009, at 5:24 AM, Paul Hoadley wrote:
Hello,
Say I have an application that depends on some frameworks containing
some more general code and components. Some of the general
components are page-level components. Every page-level component in
the application contains a wrapper component (LAF.wo) as its
outermost element to give a consistent look and feel.
What I want to do is simple: have the general (non-app) page-level
components wrapped by the (app-specific) LAF.wo. At the moment, I'm
doing this by creating a proxy page-level component in the app which
does nothing more than wrap the framework component in the LAF
component. For example, say there's an EditFooPage.wo in
Foo.framework, I create SomeAppEditFooPage.wo which puts
EditFooPage.wo inside LAF.wo. This works just fine, but it would be
nice to do it without the additional components in the app.
My first thought was to pass the name of the app-specific wrapper to
EditFooPage.wo, and use a WOSwitchComponent in EditFooPage.wo to
wrap it in LAF.wo. Although I haven't tried this, I assume it would
work. However, LAF.wo offers some bindings to customise some of its
behaviour. What I'd really like to do is be able to pass an actual
component with some bindings set to EditFooPage.wo, which would then
use this as its outermost component. Is there a standard approach
for doing something like this?
--
Paul.
Direct to Web. You'd pass the extra bindings via the d2wContext.
Just create a new Wonder D2W app in Eclipse and look at the
PageWrapper there.
Ramsey
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
