20 Mar
2010
20 Mar
'10
12:53 a.m.
On 19.03.2010, at 17:46, Lukas Renggli wrote:
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?
Norbert
I'm sorry
but I don't know how I can explain that in a more understandable fashion. But maybe
you understand it and have some hints or pointers how to approach that use case.
What about creating a WATask or WAComponent and embedding it directly
as a PRComponent so that you have the complete logic in Seaside code?