1 On Saturday 04 July 2009 02:19:35 Ben Finney wrote:
2 > Gianluca Montecchi <gian@grys.it> writes:
5 > > I am open to suggestion about it of course.
7 > Instead of a separate command for each output format, could we have a
8 > single “produce a static report of the bug database” command, and
9 > specify output format as an option?
14 > be report --format ascii
15 > be report --format rst
16 > be report --format html
18 > Where the ‘--format’ option has a default of, e.g., “ascii”.
20 > This would mean that you are implementing the ‘html’ format of this
24 This sound like an interesting idea, but what i'd like to do is not, strictly
25 speaking, a report. It is a full tree of html pages that are browseable, both
28 > > 2) I see that every command is implemented with a python file in the
29 > > becommand dir. For a better code, I'd like to split the command
30 > > implementation into two files: a file that contain the actual code and
31 > > a second file that have the html related part, any problem with this ?
33 > This sounds quite sensible to me. The existence of a command implies a
34 > module of the same name in ‘becommand’, but there's no necessary
35 > implication that that module can't import modules from elsewhere to do
38 The "elsewhere" for now is the same directory, just another module
44 _______________________________________________
46 Be-devel@bugseverywhere.org
47 http://void.printf.net/cgi-bin/mailman/listinfo/be-devel