26 Mar
2010
26 Mar
'10
4:52 p.m.
On 20.03.2010, at 11:20, Lukas Renggli wrote:
No, I did not fully understand what you tried to do.
Another idea: Have a look at the Pier Randomizer plugin. Instead of
displaying a set of pages at random, you could implement a similar
widget that displayed the pages in sequence.
Thanks, that is a good example how a set of pages can be rendered. Inside of each
of this pages there needs to be a component that has been initialized already. I would
do:
- lookup template page
- make a copy of the page
- add a PRComponent as a child that has the same name as the link on that page
- add a component with state to PRComponent
My problem is that PRComponent only takes componentClass and creates a new component each
time. So I need a good way to add an existing component to PRComponent or something
similar. Maybe there is another good approach how to inject state into a PRComponent
component.
Norbert
What about creating a WATask or WAComponent and
embedding it directly
as a PRComponent so that you have the complete logic in Seaside code?
The problem I like to solve is to have an editable page for every single step of
the task. Users have to be guided through the process a WATask might fulfill. The help
text and description around the component isn't done by a developer and should be
accesible by "normal" editors of the CMS. So I would need a series of pier pages
were a the logic (each step of a task) is embedded.
Or did I misunderstand what you were saying?