Emmanuel, Well I imagine whatever kind of lexicon one used in the templating system would have to easily map to the custom field in the database:
CustomField_<MyCustomField> CustomField.<MyCustomField> or something similar.... not sure how custom fields are stored in the database... Prepending with CustomField would enable the parser to know that it has to handle this tag specially ... -Chris On 1/22/07, Emmanuel Blot <[EMAIL PROTECTED]> wrote: > > > notification e-mail suppose we worked off a user defined template? Of > > course, we can keep the default templates the way they are now... > > There is now notification email template per se: the 'box' (with all > the parameters, except the description and the comments) is hardcoded > in Python for now. > > I'm not sure how hard it would be to create a template for email, > knowing that the list of available parameters can be augmented with > custom field values. > > Cheers, > Manu > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
