One thing I especially had trouble with was understanding what the workflow specification in the trac.ini was. I kept thinking that the values in there referred to some kind of internal call or constructs, when in reality they really are just abstract names that can be made up at will. (I did finally notice two lines in the wiki page about workflow that said as much ).
In general, if I had been aware of the way that the Python config reader works, I probably would have come to that conclusion much sooner. Being totally ignorant of python, I had no idea what to expect and everything looked like code to me at that point. So, some topic suggestions would be : 1. Detailed explanantions about workflow and how to set it up to meet various 'best-of' practices. Now that I have some idea of what I am doing I am setting one up for us to use, and I'd be happy to post an annotated copy of it somewhere. Here's some things I'd still like to know about (thread hijack warning): 1. How to validate fields pre-commit and block the commit with a fail warning. I know about the ticketvalidator plugin but so far it doesn't seem to work, and even if it did it doesn't seem to be able to validate field content, just whether or not it has something in it. What we need is either way more field types or a validation callout of some sort that we can hook to. A SQL query tag comes to mind. 2. How to restrict fields from display/and or edit based on some condition. This might be able to be done via a user-specifiable SQL query tag on the field returning true or false. The query gets run, if its true the field gets displayed, if its false it doesn't. Or something like that. 3. How to modify workflow to select different states depending on condition. Again, if I could specify a query that returned the status I wanted, instead of having to specify it by name in the workflow, things would be a lot more flexible. -----Original Message----- From: trac-users@googlegroups.com [mailto:trac-us...@googlegroups.com] On Behalf Of Lance Hendrix Sent: Wednesday, June 03, 2009 1:28 PM To: trac-users@googlegroups.com Subject: [Trac] Re: Trac Recipies In line with your note, perhaps you could suggest a few items (or a few topics) that you especially feel would be important/critical/useful to develop (what were you unable to find documentation about). IMHO one of the biggest issues facing the adoption of OSS is the lack of documentation and as a result one of my major objectives to support the OSS effort is to attempt to provide or at least assist with the development of (I am capable of at generating content quickly, I'll let someone else be the judge of it's usefulness) documentation; however, in order to be most useful, I think the effort should be driven by the community (as to what to develop). In short, while you could develop the documentation yourself (as has been suggested), there is also the option of assisting or collaborating with someone (me?) to help improve the documentation. Anyone else with any documentation requests would also be welcome. (I know, be careful what you wish for...) Lance Dan Winslow wrote: > > So do I. Track hacks is a OK place to get plugins from, but not > information on how to do things. In general there is a crippling lack > of information all across the web about TRAC. I have spent two weeks > trying to understand various aspects of TRAC, and I am just now > starting to get a vague idea. I am not a python programmer, nor do I > have any wish to become one. All of the documentation I can find about > a specific subject is usually only a few terse sentences, maybe a > **very** short example, and then they all trail off with ' .. and of > course, you can always write a plugin to do anything more.'. I don't > want to write plug-ins. I don't want to have to read through bunch of > alien-looking code to try and figure out what it means. I'm not > faulting the developers in particular, they've done a fine job and > it's a huge amount of work to maintain decent docs. > > I was so frustrated that I tried to get management to let me write my > own system, but they declined. I think a collection point for trac > recipies would be a greta idea. > > ------------------------------------------------------------------------ > > *From:* trac-users@googlegroups.com > [mailto:trac-us...@googlegroups.com] *On Behalf Of *Ariel Balter > *Sent:* Wednesday, June 03, 2009 12:59 PM > *To:* trac-users@googlegroups.com > *Subject:* [Trac] Re: Trac Recipies > > I disagree. > > Noah Kantrowitz wrote: > > Trac-hacks is that site. > > --Noah > > >> -----Original Message----- >> From: trac-users@googlegroups.com <mailto:trac-users@googlegroups.com> [mailto:trac-us...@googlegroups.com] >> On Behalf Of abalter >> Sent: Wednesday, June 03, 2009 10:52 AM >> To: Trac Users >> Subject: [Trac] Trac Recipies >> >> >> I would like to help put together a site of recipes for using Trac. >> There is a ton of great information in this email list and forums and >> out there on the web. I think it would be great to take a sort of >> "best of" of the actual solutions and organize them into a set of >> recipes such as "You want to do XXX...Do this:". >> >> Not surprisingly, I thing the best way to build this recipe book is >> with a Trac site. The first thing I would need would be a place to >> host it. Perhaps the folks that run Trac-hacks would be willing to >> give me some space. Or, perhaps edgewall.com. I'm open to >> suggestions. >> >> I'd love to hear feedback on this idea. >> >> Thanks, Ariel >> >> > > > > > > > > -- > /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ > > Ariel I Balter, Ph.D. > Postdoc > Biological Monitoring/Modeling > Fundamental and Computational Sciences Directorate > > Pacific Northwest National Laboratory > Mail: > PO Box 999, MS P7-58,Richland, WA 99352 > Shipping: > 790 6th Street, MS P7-58, Richland, WA 99354 > > Tel: 509-376-7605 > Cell: 509-713-0087 > ariel.bal...@pnl.gov <mailto:ariel.bal...@pnl.gov> > www.arielbalter.com <http://www.arielbalter.com> > www.pnl.gov <http://www.pnl.gov> > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
