Just had a moment to put together the rest of my accordion component with two
components. It's definitely more elegant than all the slinging of parameters
and coercing blocks out of informal parameter titles and of course it
affords you looping.
I'd have to agree that the t5-jquery tabs could be r
Yes!!
IMHO I think the tapestry-jquery tabs component uses the "messy" parameters
I was referring to
http://tapestry5-jquery.com/components/docsjquerytabs
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Component-Utilizing-PropertyOverrides-Adding-Override-Blocks-Dynamic
Hi
Something like our Carousel component :
https://github.com/got5/tapestry5-jquery/blob/master/src/test/resources/org/got5/tapestry5/jquery/pages/CarouselPage.tml?
Manu
2013/2/12 Lance Java
> I much prefer to use components for this sort of thing. If you use
> parameters, you start to do all
I much prefer to use components for this sort of thing. If you use
parameters, you start to do all kinds of messy stuff with naming
conventions:
eg:
Body 1
Body 1
I think 2 components is much cleaner and has the benefit IDE tooling
support.
--
View this message in context:
http://tap
Hi Lance,
That really is looking like the only plausible solution that hides away
boilerplate mark-up/config. All these kinds of components are very similar
in nature. (Bung some things into other named things under a thing). It
would be cool to be able to mangle (read: modify) the parameter tag t
Why not use two separate components.
Item 1 Body
Item 2 Body
I do a similar thing with TabGroup/Tab here
Demo:
https://github.com/uklance/tapestry-stitch-demo/blob/master/src/main/resources/org/lazan/t5/stitch/demo/pages/TabGroupDemo.tml
https://github.com/uklance/tapestry-stitch-demo/b
