Re: component definitions

Actually,  I used the property file because it was something that was going
to change frequently, and because I coded that before OGNL was available.

So I could have done it as:

<binding name="tabOrder" expression='{ "Home", "Foo", "Bar", "Baz" ... }'/>

If I was doing it today.

Either way, it is only configured once.

Does WOF have this feature you are suggesting?

----- Original Message -----
From: "Christian Sell" <[email protected]>
To: <[email protected]>
Sent: Thursday, December 19, 2002 9:37 PM
Subject: Re: [Tapestry-developer] component definitions


> your quote from my mail below may have been the point where you stopped
> reading. For your convenience, here are the lines that followed:
>
> > (1) in the case ot the border tutorial, calling back into the
> > engine to get a statically defined value
> > (2) in the workbench example, defining the menu items in a
> > property file
>
> for clarity, I will repeat myself again:
>
> in the workbench example, the Border component pulls its "tabOrder"
> configuration from a properties file. That is clearly stuff (IMO) that
would
> belong with the component configuration in the JWC file - if that wasnt so
> repetitive.
>
> Christian
>
> ----- Original Message -----
> From: <[email protected]>
> To: "Christian Sell" <[email protected]>
> Sent: Thursday, December 19, 2002 8:14 PM
> Subject: Re: [Tapestry-developer] component definitions
>
>
> > > > > Border needs a parameter which provides the items to be
> > > > > displayed on the menu (or in tabs for the workbench example).
> > > > > This parameter has to be re-specified for every page using
> > > > > that border, even though it never changes. In the example
> > > > > programs, you circumvent this by
> > > > >
> >
> > Yes, I'm reading your mail!
> >
> > The Workbench Border does not have any parameters.  It only works inside
> the
> > Workbench, and therefore knows where to look for its data.  If you look
at
> the
> > HTML templates and page specifications for the pages within the
Workbench,
> > you'll see the minimal representation I've been talking about.
> >
> > 2.3:
> >
> > <span jwcid="border"> ... </span>
> >
> > AND
> >
> > <component id="border" type="Border"/>
> >
> >
> > 2.4:
> >
> > <span jwcid="@Border"> ... </span>
> >
> >
> > Where, exactly, are the unwanted, duplicate declarations you're so
worked
> up
> > over?
> >
> > --
> > [email protected]
> >
> > http://tapestry.sf.net
>
>



-------------------------------------------------------
This SF.NET email is sponsored by:  The Best Geek Holiday Gifts!
Time is running out!  Thinkgeek.com has the coolest gifts for
your favorite geek.   Let your fingers do the typing.   Visit Now.
T H I N K G E E K . C O M        http://www.thinkgeek.com/sf/