Andreas Hartmann wrote:
Jann Forrer wrote:
Andreas Hartmann wrote:
Andreas Hartmann wrote:
[...]
- We could treat the site structure as a separate entity and apply
a workflow to it. This means that moving a document would be
an editing operation on the site structure, and you could
publish the site structure again. You could imagine the site
structure as a document which contains references to other
documents. Side note: Maybe it would be even appropriate to
implement it like this (this SimpleSiteManager is already
implemented this way).
There's problem with this approach:
If you move the documents A to A' and B to B', you can't publish
the change to A without publishing the change to B.
Is it not possible to update only a part ot the site structure and
keeping the workflow state to authoring as long as not all changes are
published?
Well, IMO that would contradict the current meaning of "publishing".
Either something is published, or it isn't ...
I think I'd prefer the other approach (publishing single documents)
from a user's point of view.
What do the others think?
I prefer the "publishing single documents" approach. Even though the
sitetree file handles the mapping for us, I still see this as metadata
which belongs to the doc (doc has these parents, and has these children).
The problem with this approach is when someone shuffles around the
sitetree in a really cool sitetree editor usecase, then they have to
publish each doc they moved individually. Perhaps if such a "sitetree
editor" usecase existed, the user could shuffle the site around, click
submit, and then get a list of changed docs with the option of publishing.
--Doug
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
