On Thu, Apr 13, 2006 at 12:15:29PM -0400, Todd Nine wrote: > Hi all, > I'm using trac at home for my personal projects and I really like it. > I've recommend it to my manager, and she's considering using it as a > centralized source of our requirements and developer documentation. As a > result, I have a couple of different plug ins I need to evaluate. > > 1. Is there a source browsing module for CVS in the works?
I don't believe so, no. #2643 [1] is about as close as it gets. > 2. Is there any sort of time tracking module in the works? I assume you mean tracking time spent working on tickets? If so, have a look at #710 and maybe #2961. If you base your plugin off the WorkFlow branch a time tracking plugin should be possible. Against 0.9.x or trunk you will probably have to create and maintain a patch. > If neither module exists my highest priority would be to create a time > tracking module since we already have viewcvs. I still need a definite yest > that my organization will host trac(Python 2.4). I've looked at > > http://trac-hacks.org/wiki/EggCookingTutorial > > which helps me with creating eggs (similar to a .jar in java), but I would > like to follow best practices for Python if I develop this. Are there any > standards pages I could review to keep my code clean, as well as some good > tutorials on creating a trac plug in? Trac style guidelines are on the Trac Wiki [2]. The EggCookingTutorial is pretty much the best tutorial, with some useful stuff also on the Trac Wiki [2]. Other than that, using other plugins as an example is probably the best way. TracHacks has a wide variety, but I'd go for the simple ones first: EasterPlugin, TocMacro (just recently converted to a plugin by coderanger) or ChangeLogPlugin. And of course, looking at the Trac source. If you have specific Trac API questions, feel free to drop by #trac on freenode. Good luck, Alec [1] http://projects.edgewall.com/trac/ticket/2643 [2] http://projects.edgewall.com/trac/wiki/TracDev -- Evolution: Taking care of those too stupid to take care of themselves. _______________________________________________ Trac-dev mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac-dev
