Organise specto source into modules

[GoogleCodeExporter]

Currently, specto source is just a single module.  Some parts cry out to be
turned into a submodule of their own (all the watch_* stuff is *definitely*
the low hanging fruit here).

The source would be much tidier organised into modules.  Certainly a watch
module, and possibly others (gui? configuration?).

Original issue reported on code.google.com by chalsero...@gmail.com on 21 Nov 2006 at 9:04

[GoogleCodeExporter]

Aaargh!  How do you turn this into a wishlist enhancement?

Original comment by chalsero...@gmail.com on 21 Nov 2006 at 9:06

[GoogleCodeExporter]

Could you give some more information?
Specto uses classes and all the watch_* classe inherit from the class watch and 
the 
configuration is the class watch_io in the file watch.py, so i don't see the 
problem 
here.

Or do you mean clean up main.py (class specto) and move all the gui functions 
to a 
new class gui?

Original comment by woutclym...@gmail.com on 21 Nov 2006 at 10:12

[GoogleCodeExporter]

I basically mean having a watch directory, with an __init__.py, which contains
watch.py and watch_*.py.

Then you can rename watch_* to just *, and then do things like
import watch.mail.gmail

Basically, it just cleans up the specto directory a bit, and allows you to 
replace
all the '_' with '.' :)

Original comment by chalsero...@gmail.com on 21 Nov 2006 at 11:04

[GoogleCodeExporter]

Of course, it looks like main.py could also do with a bit of a spring clean :).

Original comment by chalsero...@gmail.com on 21 Nov 2006 at 11:05

[GoogleCodeExporter]

[just passing by to switch this issue as a "task", because it's not really a 
feature
request and it's not a bug ;) ]

For the "Aaargh! How do you turn this into a wishlist enhancement?" question, 
only
project members can change the issue types, I guess it's a done-by-design 
feature of
google (it does annoy me a bit). If you start contributing to specto once in a 
while,
I would gladly add you as member if you request so ;)

Original comment by nekoh...@gmail.com on 21 Nov 2006 at 10:40

• Added labels: Maintainability, Type-Task
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by chalsero...@gmail.com on 2 Feb 2007 at 4:15

• Changed state: Started

[GoogleCodeExporter]

when doing this i think it would be great to make watch types work like 
plug-ins, so
that new types can easily be added by just dropping a file in the directory, ie 
not
hardcoding the types of watches there are into main.py anymore...(that would 
make
main.py a lot leaner, too)

Original comment by thomas.m...@gmail.com on 13 Feb 2007 at 6:45

[GoogleCodeExporter]

I know at least two ways to do that, and I'll implement it once I get around to
refactoring watch.py.

That may take a while, though, and I'd publish it in a branch at first.

Original comment by chalsero...@gmail.com on 14 Feb 2007 at 12:17

[GoogleCodeExporter]

chalserogers, Could you provide this new setup.py file so we can start working 
with
modules? thank you

Original comment by woutclym...@gmail.com on 20 Sep 2007 at 9:59

[GoogleCodeExporter]

Isn't that partly started in Wout's branch?

Original comment by nekoh...@gmail.com on 4 Dec 2007 at 12:26

• Added labels: DevBranch-Chris, DevBranch-Wout

[GoogleCodeExporter]

Original comment by woutclym...@gmail.com on 4 Jan 2008 at 7:20

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by nekoh...@gmail.com on 16 Mar 2008 at 6:16

• Changed state: Verified
• Added labels: Milestone-Release0.3