Given the need to manage ActivityIndicators independently, you would probably need to use separate renderers for each Accordion header anyway, so the renderer loses much of its worth.
And as Accordion only supports adding a single renderer for the entire component, your renderer would need to be more complex and would probably end being a single wrapper class than then delegated to individual 'real' renderers depending on which panel was being renderered. You could get around this by modifying Accordion to accept multiple renderers, but again, that doesn't seem likely to simplify things overall. Anyway, good luck with it, and shout if you have any issues we might be able to help out with. Chris On 21 March 2011 22:13, Simon Chatelain <[email protected]> wrote: > For my specific use case: let's say that my application is some kind of > monitoring tool displaying the state of some machines that could be either > running or stopped, to keep it simple. The ActivityIndicator would show this > state for each machine, and the content of each panel will show some details > about the machine. > > So all the ActivityIndicator will be visible at all time and individually > started and stopped depending of the state of corresponding machine. >
