I threw a blog together and posted a short tutorial here
(http://blog.torr.redijedi.com/2007/08/t5-tab-component.html). The
code as well as a jar is available through the links there. Hope
someone finds this useful. I've got a couple other components that
I'll probably end up throwing up there too.
Todd Orr wrote:
[...] This is where I
found Environment to be deficient. It seems that no matter what
combination of phases of rendering I use I cannot get the data back to
the tabnavigation before it is finished rendering and therefore cannot
alter it's display.
Not sure that it matches what you
Great. Or put it on the wiki so others can use and improve it.
Cheers,
Nick.
Todd Orr wrote:
As imperfect as it is, I'll probably post the code after I've tinkered
with the capabilities a little bit.
Thanks all.
-
To unsub
Since I'd like the number of panels to be configurable by the page
building programmer, having a set number of @Components in my TabGroup
will not work. I've found a workaround for now:
This is stuff 1
This is stuff 2
Hi Todd.
The documentation is not exactly clear on this topic, so I'm not sure
whether that or the implementation is incomplete ...
The docs say:
"Components inside another components template are called embedded components."
Whereas the implementation WRT getEmbeddedComponentIds() is:
"Compone
I absolutely agree that the components should have as loose coupling
as possible. However, from my testing on simple, non-form related,
nested components the components that render later cannot pass any
information to the components that render sooner.
Perhaps a solid example will better illustrat
The design as it stands exists to remove invisible and unwanted
dependencies. Component names, ids, types and classes can change ... and
yet, using Environmental or ASOs to communicate will stand up to many kinds
of refactorings, large and small.
Introducing the ability to create arbitrary linkag
I've been running my debugger to try to determine what is available to
the components at various points during rendering. As far as I can see
there is very little information provided regarding what other
components exist anywhere else in the page. The only thing I can get
for sure is the Page. How
BTW _resources.getComponentModel().getEmbeddedComponentIds() would be
really really useful if it didn't return an empty list every time
during my testing. Is there any way for a component to know what it
contains?
On 7/30/07, Todd Orr <[EMAIL PROTECTED]> wrote:
> I've found out how to pass data be
I've found out how to pass data between components so long as it's
downstream. Is there a way to pass data from a component (B) that is
physically below another component (A) to component A?
I've found that performing any data passing (per situation above)
during the RenderSetup, etc. methods usin
10 matches
Mail list logo
