bugseverywhere - Bugtracker built on distributed version control

	Commit message (Collapse)	Author	Age	Files	Lines
*	Reorganized directory structure, mostly to put all the interfaces in	W. Trevor King	2009-07-14	4	-196/+39
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	one place and make things clearer to the uninitiated. Here's my current understanding: . \|-- libbe (the guts of BE) \|-- becommands (plugins for all "be *" commands) \|-- doc (documentation, currently just the man page) \|-- interfaces (non-commandline interface implementations) \| \|-- web \| \| \|-- Bugs-Everywhere-Web (in Turbogears) \| \|-- gui \| \| \|-- beg (in Tkinter) \| \| `-- wxbe (in WX) \| \|-- email \| `-- xml (xml <-> whatever conversion) `-- misc (random odds and ends) `-- completion (shell completion scripts) Note that I haven't attempted to use the web or gui interfaces in a while, so I'm not sure how well they're holding vs the core development.
*	Updated misc/gui/wxbe with wxPython -> wx changes.	W. Trevor King	2008-11-19	1	-36/+74
\| \| \| \| \| \| \| \| \| \| \| \|	I'd like to be able to sort the bugs by clicking on the various column titles, but I don't know enough about wxPython to pull it off. After wrestling with it for a bit, I realized that I'll only be using the command line interface anyway, and other people can use the web interface. Probably a common feeling, which would explain why the GUIs feel so abandoned ;). At any rate, I think the effects of turning the RCSs into classes have been passed through and stabilized, so my churning should decrease...
*	Added logo	Aaron Bentley	2005-05-18	4	-0/+241