J. Wolfgang Kaltz schrieb:
Andreas Hartmann schrieb:
Felix Röthenbacher schrieb:
Hi Andreas
I noticed (apart from some formatting changes) that you extended the
document info module with the possibility to get the document's
visibility in navigation. I wonder if that's the right place as document
visibility is dependent on the chosen navigation.
Is this really the case? In the repo draft, I assigned the navigation
visibility to the content node -
That actually doesn't follow from the repository-api.pdf
I didn't add the method to the class diagram, but you can take a look
at the code. Unfortunately the javadocs on lenya.apache.org are not
up to date ...
> IMO the general classification as
"visible" or "hidden" is rather a property of the content item and
should apply to all navigations.
In the above-mentioned class diagram, I would expect this property to be
an attribute of the class SiteNode.
IMO visibility is navigation-dependent, and not content-dependent (so I
agree with Felix here). Consider content reuse. If I use the same
content piece in two places, maybe I want it to have a visible
navigation entry in one place, but not in the other. Or, I have
different navigations, depending on the type of user. Or, ...
WDYT ?
IMO that could be handled implicitly by the navigation. Either you add
the reference to the content item, or you don't.
IMO the navigation visibility is a property of the content, for instance
to implement utility pages used by website editors.
Thinking about this, I think that the navigation visibility property is
obsolete. With the 1:1 mapping from documents to site structure nodes it
wasn't possible to decide if a content item should appear in the
navigation. But if we allow to arbitrarily assign content items to
navigation nodes, the visibility property won't be necessary anymore.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
