Deen Sethanandha wrote: > Thanks a lot Erik. You answer many things that I need to know. I will > start with feature that doesn't require changing Trac's page first. I like > the idea of MVC. I think it might be good to add _ui to the module that has > web interface. I start to recognize some of the method that deal with web > request. > > Based on the MVC is it correct to say that > > - api.py is the controller of the package > - model.py is the model of the package > - web_ui.py is the view of the package. > > I notice that some package has other files such as report.py which seem to > be View since it has something to do with template. > > Assuming that Trac follow MVC. Is there any keywords that I can look into > the .py file and able to determine right away whether it is Model, View or > Controller?
Trac does not follow MVC, its just a sort of rough guideline. The view, as with most MVC systems is abstracted inside the Trac chrome and Genshi systems. web_ui is often the controller-ish thing, usually the primary UI. api usually contains Interface-related stuff, and possibly some central functionality if you have multiple UIs or something. --Noah
signature.asc
Description: OpenPGP digital signature
