On Apr 9, 2009, at 3:07 AM, Felix Schwarz wrote: > > Hi, > > I'm just wondering why the TicketModule contains all these Optiosn for > default attributes (e.g. [1]). As far as I can see, all these options > are never used. > > Even the TicketSystem does not use them but accesses the configuration > directly [2]. While I like that the TicketSystem does not depend on > the > TicketModule, I think that the right place for these Options would be > the TicketSystem itself. > > Probably I just missed (at least) one important point, right? > > fs > > [1] http://trac.edgewall.org/browser/trunk/trac/ticket/web_ui.py#L66 > [2] http://trac.edgewall.org/browser/trunk/trac/ticket/api.py#L231
Creating the Option attributes adds those options to the central registry of config options. This is how things like IniAdmin and the TracIni macro can introspect what config options exist. --Noah --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
