Dear GenericTrac fans, here is a question risen from current Trac plugin development.
I require a resource register to refer to arbitrary Trac resources by id. While I feel, that such an instance-wide unique resource-ID should be provided by the core, this is not done yet. I wonder, if it'll be part of the GenericTrac [1] approach later on. But the major question is, how to address my need for identifying parts of resources, like the description field for tickets or a single form field of TracFormsPlugin [2]. Initially I created a new class derived from Resource [3] with an additional attribute 'fragment'. But the longer I look at it, I feel more confident, that this should be just as generic an attachment is defined as a child resource of another resource. So I should specificity something dedicated to the ticket description as resource 'description' with a 'ticket' parent, shouldn't I? This way I could do it all with stock Trac resource attributes and additional recursions/JOINs on db lookup. Today I don't see multiple cascading levels of parent-child associations, like ticket - attachment, while I'll need something like ticket - description - form - form-field too. Any advice and suggestion is welcome. Sincerely, Steffen Hoffmann [1] http://trac.edgewall.org/wiki/GenericTrac [2] http://trac-hacks.org/wiki/TracFormsPlugin [3] http://trac.edgewall.org/browser/tags/trac-0.12.3/trac/resource.py#L84
smime.p7s
Description: S/MIME Cryptographic Signature
