(Philipp, bitte sag mir wohin damit :) . Jira-Ticket?) It is currently too easy to get a repository into a unworkable state by changing some non-suspicious-looking property value, like virtual URI settings.
Inspired by gconf-editor ( http://en.wikipedia.org/wiki/Gconf-editor ), I suggest implementing property descriptions, and adding descriptions at the very least to those properties where changes might be dangerous to repository operation. AFAIK, properties are atomic values (strings, integers, booleans) that can't hold an additional "property description". But what about adding a node (e.g. PropertyCaptions, like MetaData) that holds property descriptions for properties within the same parent? These descriptions should be visible and editable in AdminCentral in some way (a separate column seems overkill if only 0.1% of all properties have descriptions). And if XML exports can be manipulated this way, they could also appear as XML comments right before each described property in the exported file, in addition to showing up in the isolated PropertyCaptions node. - Felix ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
