Lukas Renggli wrote:
> - there might be a problem with the versioning: the version of a
> structure is not the same as the version of the structures children
> (structure version != structure children first parent version)
> ...I'm not sure if the version should always be the same.
No, all structures are versioned independently. There is no need to
create new version for the parent, if a child changes.
yes, but I wanted to say that a child doesn't reference back to the
right version of the parent.
e.g node01 (version 500) has child node011, but node011 has parent
node01 (version 477)
this is a problem for the admin tool, because I want to be able to
collect all parent roles from e.g node011 in the structure-tree.
otherwise I would have to ask every single node in the tree if it is the
parent of node011 :-(
> - another question:
> I want the admin link to be visible just like the other ones: view,
> edit, contents etc., what is the best way to do this? do I have to
> modify each structure's template?
There are only about 3 templates defined on this wiki: the root, the
SmallWiki folder and the CaroAndBot folder. As you know, these
instances are shared among all their corresponding child structures,
so you have to change only those 3 places.
Weak as I am, I would use the powerful reflection mechanism of
Smalltalk and do something like:
SmallWiki.TemplateBodyActions allInstances do: [ :each |
each actions add: SmallWiki.AdminAction ]
Actually I would like to integrate some other actions into the central
admin menu-item, like the history, the template and the property
editor (something new I wrote yesterday night). We should also think
about a way to show the actions of a page in a tree-like structure, as
there are too many items to show in one line
...to render the admin menu I used some simple mechanism that renders a
menu according to a class and their subclasses:
eg. do AdminAction: render the menu of their subclasses (Security
do AdminSecurity: render super, render the menu of their
subclasses (AdminUsers and AdminRoles)
but this system is not very useful and fexible 'cause it uses only the
structure of classes and their subclasses and this should't have
anything to do with a html menu to render...