Alec Thomas wrote:
> I'll kick off the editor war by saying:
>
> vim++
>
> mgood also uses vim, so that's
>
> vim += 2
>
> ;)
>
.. which accounts to vim == 3, for only 2 users, well that's not fair...
So let's say XEmacs = 10, one user but the editor is an order of
magnitude better ;-)
> On 5/20/07, px <[EMAIL PROTECTED]> wrote:
>
>> Do Trac-developers use any particular IDE? I am looking for a simple
>> development flow that works out well.
>> * Do you develop on the target installation or do you modify files in
>> your local directory and run the install process again
>>
For development, nothing is more convenient than using trac in
standalone mode, straight from the checkout of the particular branch
you're working on. With the "-r" option, it auto-restarts after every
code change, making the need for manual restarts only minimal (e.g.
after [components] changes in the Trac ini, after the whole thing
crashed because of a syntax error, etc.)
In the same way, you'd also benefit from using the [trac] auto_reload =
yes configuration option, which makes the template engine re-parse the
templates if they were changed (0.11 / Genshi specific, of course).
Example of the command line I'm using right now,
from the .../src/trac/branches/t4686-trunk folder:
$ PATH=/C/Program\ Files/PostgreSQL/8.1/bin:$PATH \
python trac/web/standalone.py -p 8000 \
-a '*,C:/Workspace/local/trac/htdigest.realm,realm' \
-e C:/Workspace/local/trac -r
Also, if you're using a 0.11dev branch, you need to run the following:
python setup.py egg_info
before being able to run Trac from the local folder.
Hope this helps!
-- 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
-~----------~----~----~----~------~----~------~--~---
