store user configurations

[GoogleCodeExporter]

Describe the enhancement in detail.

This enhancement will allow users to store information pertaining to their
tracshell configuration (ie: their editor and other future settings) as
well as store connection information for several Trac instances should they
work with more than one.

What files will be affected?

bin/tracshell
shell.py
trac.py

How will the enhancement benefit the project?

It will improve usability for the users

What side-effects (if any) will the enhancement create?

We'll add a new file and class for loading and storing configurations.

Original issue reported on code.google.com by j.kennet...@gmail.com on 3 Mar 2009 at 3:35

[GoogleCodeExporter]

Original comment by j.kennet...@gmail.com on 3 Mar 2009 at 3:36

• Added labels: Milestone-Release1.0

[GoogleCodeExporter]

Issue 7 has been merged into this issue.

Original comment by j.kennet...@gmail.com on 3 Mar 2009 at 4:17

[GoogleCodeExporter]

added settings.py which defines a Settings class that will be used by the 
launcher
class to setup TracShell

introduces a dependency on PyYAML, added it to the setup.py script

Original comment by j.kennet...@gmail.com on 9 Mar 2009 at 5:33

• Changed state: Started

[GoogleCodeExporter]

Trac instances are internally called, "sites" which are represented by the
settings.Site class.

All configuration is done via settings file.

Command-line options changed; can specify a settings file to use (default is
{HOME}/.tracshell) and site (of which the settings file can specify the 
default).

Unless there are any objects to the removal of the former command-line options, 
I
don't intend to bring them back.

Original comment by j.kennet...@gmail.com on 9 Mar 2009 at 7:36

• Changed state: Fixed

[GoogleCodeExporter]

the changes are in r25

Original comment by j.kennet...@gmail.com on 9 Mar 2009 at 7:37