> 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?
Not much. I don't like the way the configuration is laid out in the .ini file; I'm open to better ways of describing a workflow. That said, look at contrib/workflow_parser.py on the new branch. It sanity checks the configuration in the specified .ini, and generates a graphviz file to graph the workflow. Eli --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
