Really I don't think we want to move in this direction. The wiki isn't supposed to be some generic data storage mechanism. It is just a simple wiki with one text blob per page. This kind of generic data storage system just doesn't fit with the Trac design philosophy.
--Noah > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of Catalin Balan > Sent: Tuesday, September 30, 2008 1:53 AM > To: [email protected] > Subject: [Trac-dev] Re: Resource Meta Data > > > Hi trac-dev, > > In case anyone is still interested in this issue, I have it implemented > here: [1] > WikiToolsPlugin provides a set of features like wiki custom fields and > page/resource relation, based on resource tools. > > Some feedback would be very nice. > > [1] > http://code.optaros.com/svn/oforge/trunk/plugins/resourcetoolsplugin/ > [2] http://code.optaros.com/svn/oforge/trunk/plugins/wikitoolsplugin/ > > ps. No documentation yet available, since this feature is still under > development. > > Thank you, > Catalin Balan > > Williams, Stanley E wrote: > > All: > > I want to do something similar. I want to be able to upload a series > of > > documents and view them as a file tree. I could to this if the > > documents and virtual folders had custom property lists associated to > > them. > > > > Stan Williams > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Friday, July 04, 2008 10:17 AM > > To: Trac Development > > Subject: [Trac-dev] Resource Meta Data > > > > > > 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 -~----------~----~----~----~------~----~------~--~---
