Hi , For a project I needed the ability to add to a wiki page some custom properties (key-value pair). Properties that were updated/managed by trac users.
Since this feature can enable some nice capabilities like: - Hierarchical wiki organization (parent) - Related pages tracking (related) - Approvals (approved-by, approved-date) - Privacy (user, role, or PERM) - Comments (commenter, comment, comment-date) - Tags (alternate implementation of tagging) - Hide from indexes or search (eg no-index-flag) I was thinking to put that work into a plugin, and maybe go a little more further. So, did anyone put some thoughts on having the ability to store/manage some custom properties related to a trac resource ? Something that, I guess, could be achieved by extending 'ticket- custom' and 'workflow' features to support a trac resource, not just tickets. Another approach, could be by building some plugins like: - ResourceMetaPlugin - Should provide only a simple storage api for various resources types. - WikiCustomFieldsPlugin - Based on config options(similar to ticket- custom), should inject custom fields on the wiki screens(edit/view) pages(Using ResourceMetaDataPlugin for storage). - WikiHiearchicalSitePlugin - Based on a 'parent' meta-data resource field(for a child-parent relation), wiki pages could be easily organized. - etc Any thoughts on this ? Thank you, Catalin Balan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
