1 Speaking of that interface, I changed up the look and feel a bit last
2 weekend. It's still at http://bitbucket.org/sjl/cherryflavoredbugseverywhere/
3 -- if anyone has any feedback (on any aspect of it) I'd appreciate it.
8 On Jul 3, 2009, at 8:31 PM, Chris Ball wrote:
12 >> As i said in a previous mail, I am working on a "html" command
13 >> for be. The goal is to be able to do something like "be html
14 >> /web/page" to have in the /web/page directory some static html
15 >> pages that basically are the dump of the be repository, much like
16 >> ditz have. This will enable a simple and fast publish of the bus
17 >> list and details on the web, at least in read only mode.
19 > It might be a good idea for "be html" to use the CherryPy web
21 > that Steve is working on. The command could start up the CherryPy app
22 > and scrape all of the available pages to get a stand-alone dump; this
23 > would avoid having to keep two (okay, more than two at this point)
24 > separate sets of HTML templates in the source tree. What do you
27 >> 2) I see that every command is implemented with a python file in
28 >> the becommand dir. For a better code, I'd like to split the
29 >> command implementation into two files: a file that contain the
30 >> actual code and a second file that have the html related part,
31 >> any problem with this ? I don't like to have the html part and
32 >> the code part in one big and unreadable file.
34 > I agree that becommands/*.py commands should not contain any HTML
35 > layout code. Putting it somewhere else instead sounds fine.
41 > Chris Ball <cjb@laptop.org>
43 > _______________________________________________
44 > Be-devel mailing list
45 > Be-devel@bugseverywhere.org
46 > http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
49 _______________________________________________
51 Be-devel@bugseverywhere.org
52 http://void.printf.net/cgi-bin/mailman/listinfo/be-devel