On Wed, 18 Jan 2006, Andreas Hartmann wrote:
Josias Thoeny wrote:
[...]
I added the method SiteManager.isVisibleInNav() to allow CreateLanguage
to use the value of the existing language version. In fact, IMO the
DocumentManager.add() and SiteManager method signatures should be changed,
as the visibility attribute belongs to the node and not to the document.
Ok. I also think the visibility belongs to the node. And there may be other
attributes which are properties of the node, this is why the idea to use
meta data for the node came up some time ago. What about about having a
method contentNode.getMetaData(...), just like
document.getMetaData(...)?
+1
Or is it better to use specific methods like isVisibleInNav()?
I don't mind if I write
node.isVisibleInNav()
I still have an open task to add a method getVisibleInNav() in order to
use the existing value of the Visible_in_nav attribute if a new language
is created otherwise the node beomces visible again. Or is that already
solved?
or
node.getMetaData().getValue(SiteNodeMetaData.VISIBLE_IN_NAV)
IMO the second should be implemented anyway, the first could be added
as a shortcut.
Up to now the visibleInNav attribute is stored in the sitetree. Should
that attribute be stored in the MetaData?
Jann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
