|
List Info
Thread: what is the most common IDE trac-developers use?
|
|
| what is the most common IDE
trac-developers use? |
  United States |
2007-05-19 15:26:34 |
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?
* Do you use any IDE for extra convenience in trac or
plugin
development.
thanks.
- px
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Trac Development" group.
To post to this group, send email to trac-dev googlegroups.com
To unsubscribe from this group, send email to
trac-dev-unsubscribe googlegroups.com
For more options, visit this group at http://
groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
|
|
| Re: what is the most common IDE
trac-developers use? |

|
2007-05-20 08:27:21 |
I'll kick off the editor war by saying:
vim++
mgood also uses vim, so that's
vim += 2
;)
On 5/20/07, px <prakarp gmail.com> 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?
> * Do you use any IDE for extra convenience in trac or
plugin
> development.
>
> thanks.
> - px
>
>
> >
>
--
Evolution: Taking care of those too stupid to take care of
themselves.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Trac Development" group.
To post to this group, send email to trac-dev googlegroups.com
To unsubscribe from this group, send email to
trac-dev-unsubscribe googlegroups.com
For more options, visit this group at http://
groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
|
|
| Re: what is the most common IDE
trac-developers use? |
  Netherlands |
2007-05-20 08:32:07 |
-On [20070520 15:27], Alec Thomas (trac-dev-list swapoff.org) wrote:
> vim += 2
vim += 3
There's some good scripts out there for helping Python
coding. Also the
OmniFunc stuff in vim 7 now is quite nice for completing
basic Python stuff
(^X^O).
--
Jeroen Ruigrok van der Werven
<asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル
ウェルヴェン
http://www.in-nomine.org/
a> | http://www.rangaku.org/
Beware of the fury of the patient man...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Trac Development" group.
To post to this group, send email to trac-dev googlegroups.com
To unsubscribe from this group, send email to
trac-dev-unsubscribe googlegroups.com
For more options, visit this group at http://
groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
|
|
| Re: what is the most common IDE
trac-developers use? |
  France |
2007-05-20 08:41:45 |
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 <prakarp gmail.com> 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 trac-dev googlegroups.com
To unsubscribe from this group, send email to
trac-dev-unsubscribe googlegroups.com
For more options, visit this group at http://
groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
|
|
| Re: what is the most common IDE
trac-developers use? |

|
2007-05-20 08:46:37 |
On 5/20/07, px <prakarp gmail.com> wrote:
> * Do you develop on the target installation or do you
modify files in
> your local directory and run the install process
again?
For trunk, I now use:
python setup.py develop -m
I also use workingenv [1] to install all the requirements,
including trac
itself in development mode, in a sandbox. To set up my Trac
development
environment I'd do something like:
$ svn co http://svn.e
dgewall.com/repos/trac/trunk trac
You can put your workingenv and Trac test environment
anywhere, but for the
purposes of this mail I'll plonk it under the checked out
trunk:
$ cd trac
$ mkdir sandbox
$ workingenv -Z --site-packages sandbox/wenv
$ . sandbox/wenv/bin/activate
(wenv)$ python setup.py develop -m
(wenv)$ trac-admin sandbox/trac initenv
....
You can install your plugins into this working environment
in exactly the same
way:
(wenv)$ cd ../myplugin
(wenv)$ python setup.py develop -m
Start Trac:
(wenv)$ tracd -r -s --port 8000 ./sandbox/trac
...
Edit Trac and/or plugins to your hearts content.
When finished, deactivate the workingenv:
(wenv)$ deactivate
$ tracd
-bash: tracd: command not found
My actual environment is a bit more streamlined than that,
but that's
essentially how it works.
Any of the other developers got useful tips? I know
coderanger has a
spectacularly large set of scripts to make his life easier
[1] http:
//cheeseshop.python.org/pypi/workingenv.py
--
Evolution: Taking care of those too stupid to take care of
themselves.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Trac Development" group.
To post to this group, send email to trac-dev googlegroups.com
To unsubscribe from this group, send email to
trac-dev-unsubscribe googlegroups.com
For more options, visit this group at http://
groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
|
|
| Re: what is the most common IDE
trac-developers use? |
  Netherlands |
2007-05-20 09:13:03 |
Part of my vim set up is like this:
$HOME/.vimrc
runtime autocmd.vim
And in $HOME/.vim/autocmd.vim I have amongst other things (I
need to review
all this again):
augroup python_autocmd
" Remove all python autocommands
autocmd!
autocmd FileType python set smartindent autoindent
autocmd FileType python set formatoptions=croql
autocmd FileType python set cinoptions=t0(0
autocmd FileType python set textwidth=78 shiftwidth=4
autocmd FileType python set softtabstop=4 tabstop=8
autocmd FileType python set expandtab
autocmd FileType python compiler python
autocmd FileType python hi PreProc ctermfg=DarkCyan
guifg=DarkCyan
autocmd FileType python set dict=$HOME/.vim/python.dict
autocmd BufEnter *.py if getline(1) == "" | call
setline(1, "#!/usr/bin/env py
thon") | call append(1, "") | call
cursor(2,1) | endif
autocmd BufWrite * if &ft == 'python' | call
StripTrailingWhiteSpace()
autocmd BufWritePost *.py if
FileExecutable("%:p") | :!chmod a+x % ^ endif
augroup END
And these are additional things I have inside my
$HOME/.vim:
autoload:
pythoncomplete.vim - 0.7
http://www.vim.org/scripts/script.php?script_id=1542
compiler:
python.vim:
http://www.vim.org/scripts/script.php?script_id=1439
ftplugin:
python_encodings.vim:
h
ttp://www.vim.org/scripts/script.php?script_id=756
xml.vim - 1.33
http://www.vim.org/scripts/download_script.php?src_id=
5909
indent:
python.vim:
h
ttp://www.vim.org/scripts/script.php?script_id=974
plugin:
a.vim - 2.15
ht
tp://www.vim.org/scripts/script.php?script_id=31
matchit.vim 1.12
ht
tp://www.vim.org/scripts/script.php?script_id=39
project.vim - 1.4.1
ht
tp://www.vim.org/scripts/script.php?script_id=69
pydoc.vim - 1.1.1
h
ttp://www.vim.org/scripts/script.php?script_id=910
snippetEmu.vim:
http://www.vim.org/scripts/script.php?script_id=1318
taglist.vim - 4.3
h
ttp://www.vim.org/scripts/script.php?script_id=273
vcscommand - beta 12
ht
tp://www.vim.org/scripts/script.php?script_id=90
syntax:
clearsilver:
http://www.vim.org/scripts/script.php?script_id=1100
django:
http://www.vim.org/scripts/script.php?script_id=1487
genshi:
http://www.vim.org/scripts/script.php?script_id=1869
gtk and such:
http://www.vim.org/scripts/script.php?script_id=1000
mathml.vim - 1.1
http://www.vim.org/scripts/script.php?script_id=1235
python.vim:
h
ttp://www.vim.org/scripts/script.php?script_id=790
svg.vim - 1.2
h
ttp://www.vim.org/scripts/script.php?script_id=935
txt.vim:
http://www.vim.org/scripts/script.php?script_id=1532
--
Jeroen Ruigrok van der Werven
<asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル
ウェルヴェン
http://www.in-nomine.org/
a> | http://www.rangaku.org/
De nihilo nihil...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Trac Development" group.
To post to this group, send email to trac-dev googlegroups.com
To unsubscribe from this group, send email to
trac-dev-unsubscribe googlegroups.com
For more options, visit this group at http://
groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
|
|
| Re: what is the most common IDE
trac-developers use? |

|
2007-05-20 10:56:31 |
px 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?
> * Do you use any IDE for extra convenience in trac or
plugin
> development.
>
For my editor I use TextMate. There is a Genshi bundle
available from
genshi.edgewall.org, and I have a (somewhat limited) Trac
bundle I can
make available if people are interested. I have a rather
large bash
script that I use for support tasks (available at
http://dev.c
oderanger.net/src/bashrc.txt), though if you aren't
working
with a large number of versions/environments/plugins it may
be overkill.
--Noah
|
|
| Re: what is the most common IDE
trac-developers use? |
  United States |
2007-05-21 08:01:19 |
I usually use pyscripter (http://pyscripter.
googlepages.com/).
It is a windows application, though I've seen references of
it also
working on linux with wine: http://groups.google.com/group/PyScr
ipter/browse_frm/thread/abd4303743c6ccf9
cheers,
Filipe
On May 19, 9:26 pm, px <prak... gmail.com> 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?
> * Do you use any IDE for extra convenience in trac or
plugin
> development.
>
> thanks.
> - px
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Trac Development" group.
To post to this group, send email to trac-dev googlegroups.com
To unsubscribe from this group, send email to
trac-dev-unsubscribe googlegroups.com
For more options, visit this group at http://
groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
|
|
| Re: what is the most common IDE
trac-developers use? |

|
2007-05-21 08:09:07 |
Hi Noah,
> For my editor I use TextMate.
So do I.
(for the record, TextMate is a Mac OS X editor.)
> I have a (somewhat limited) Trac bundle I can
> make available if people are interested.
I'm definitely interested in it. Is it available on
trac-hacks.org?
Cheers,
Manu
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Trac Development" group.
To post to this group, send email to trac-dev googlegroups.com
To unsubscribe from this group, send email to
trac-dev-unsubscribe googlegroups.com
For more options, visit this group at http://
groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
|
|
| Re: what is the most common IDE
trac-developers use? |
  United Kingdom |
2007-05-21 08:58:52 |
On Sunday 20 May 2007, Jeroen Ruigrok van der Werven wrote:
>
> -On [20070520 15:27], Alec Thomas (trac-dev-list swapoff.org) wrote:
> > vim += 2
>
> vim += 3
>
> There's some good scripts out there for helping Python
coding. Also the
> OmniFunc stuff in vim 7 now is quite nice for
completing basic Python stuff
> (^X^O).
vim++
Eli
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Trac Development" group.
To post to this group, send email to trac-dev googlegroups.com
To unsubscribe from this group, send email to
trac-dev-unsubscribe googlegroups.com
For more options, visit this group at http://
groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
|
|
|
|