Firstly, thanks Georges for your interest and eagerness.
I do really like the idea of having a plugin for wikkid.
I forsee something like:
$ cd some-dir
$ bzr branch lp:my-project/wiki my-project-wiki
$ cd my-project-wiki
$ bzr wikkid
Perhaps it even fires up a webbrowser pointing at the right port, and the user is free to edit the wiki offline.
I think it would be good to have it in the wikkid codebase somewhere, but I agree with Paul that having an __init__.py in the project root is a little icky.
Perhaps we put it somewhere like a plugin directory, and have a make target to add it to the ~/.bazaar/plugins directory. Although we'd still need to have to do something with the PYTHONPATH to get it working.
I'd like to be able to have a simple way to have the wikkid plugin point at my feature branch rather than my trunk branch (on packaged code one day) so I can still go 'bzr wikkid' (or bzr wiki) in my sandbox branch.
Firstly, thanks Georges for your interest and eagerness.
I do really like the idea of having a plugin for wikkid.
I forsee something like:
$ cd some-dir
$ bzr branch lp:my-project/wiki my-project-wiki
$ cd my-project-wiki
$ bzr wikkid
Perhaps it even fires up a webbrowser pointing at the right port, and the user is free to edit the wiki offline.
I think it would be good to have it in the wikkid codebase somewhere, but I agree with Paul that having an __init__.py in the project root is a little icky.
Perhaps we put it somewhere like a plugin directory, and have a make target to add it to the ~/.bazaar/plugins directory. Although we'd still need to have to do something with the PYTHONPATH to get it working.
I'd like to be able to have a simple way to have the wikkid plugin point at my feature branch rather than my trunk branch (on packaged code one day) so I can still go 'bzr wikkid' (or bzr wiki) in my sandbox branch.
Ideas?