Thanks a lot, I will look into it. I think TracDev deserve a line on the Trac front page, tho. :D
Or perhaps under TracGuide page. I guess I have to read the FAQ page when I peak into open source projects :) -- Deen On 5/7/07, Christian Boos <[EMAIL PROTECTED]> wrote: > > > Deen Sethanandha wrote: > > Hi All, > > > > I have been trying to creat a simple plugin for trac by reading > existing > > plugin code. I found that there are many function calles that I don't > > understand. > > > > Is there any document that provide API commonly used by Trac and > plugins? > > > > I wonder what would be the good approach to start learning how to > write > > code for Trac. If there is coding standard available it would be > helpful. > > I've see some comments on the mailing list about how code follows the > > style. But I can't find Trac style writen on the wiki. > > > > You must have missed the TracDev page and all its subpages ;-) > > Bonus points if you find the reference to the yet to be written > TracDev/HowTracWorks. > More seriously, the TracTroubleshooting page also contains some useful > hints for developers, > see http://trac.edgewall.org/wiki/TracTroubleshooting#DebuggingTrac > > -- Christian > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
