I actually have both API and web admin page that allows me to manage
custom fields. It is in production on 0.10.3, and works fine for the
types supported on this version. I have always intended to share it,
but have lacked the time and effort - I'll gladly share the .py
and .cs files with you it you are keen on reusing the code into a good
general plugin for trac-hacks. Send me an email and we'll figure
something out.

However, related to this is a discussion for trac developers: The API
I have implemented I use to create, update and delete custom fields -
while the current (0.10.3) API in TicketModule only allows to
get_custom_fields(). Custom fields managed through trac.ini settings
is not really a pretty way to manage field information, and my CRUD
code doing updates gets messy as it has to handle all sorts of 'if'
checks and writing and changing settings on a major scale. With the
proposal for WorkFlow (http://trac.edgewall.org/wiki/WorkFlow), I see
trac.ini settings expanding further... I suppose no one has planned an
actual API to manage this large number of field-related settings? Any
chance of there being an API to manage fields - attributes,
presentation logic, validation logic, fields in workflows and so on?


:::simon
www.coderesort.com


On Feb 27, 8:31 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> I want to create a custom admin plugin to manage Custom Ticket fields
> set in track.ini that will eventually be contributed back to the
> community
>
> I was curious if anyone had done any work on this already or if anyone
> has any specific ideas or requests for this feature.
>
> I would love to get some feedback on this.
>
> Jimmy


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to