> -----Original Message----- > From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] > On Behalf Of Eleonore DUVELLE > Sent: Wednesday, June 04, 2008 8:14 AM > To: trac-users@googlegroups.com > Subject: [Trac] Organisation of trac code > > > Hi everybody, > > I'd like to know more about the way trac's code is organised. Is this > information available somewhere? > I've found .py files in python\Lib\site-packages\trac\ but I'd like to > get an overall vision of all trac's organisation...
http://trac.edgewall.org/browser/trunk/trac Each subsystem is in a package or module. Templates for each package in the "templates/" folder. web_ui.py is generally the user interface, admin.py is the admin panels, api.py is central functionality and public API stuffs, model.py is data models. This is all just by convention, some things are done a bit differently (example, the ticket query UI and model object are both in trac/ticket/query.py). --Noah --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
