On Wed, 2002-12-04 at 21:32, Jason R. Mastaler wrote: > David Guerizec <[EMAIL PROTECTED]> writes: > > > OK, although it shouldn't have much command switches. > > True, but having the getopt interface in place will make it easier to > handle future command-line options, and also provide a known > interface. Users are already used to --help, --version, etc.
I agree. > > The reason is that I intend to be able to use it without TMDA library, > > ie. through a network connection, so it'll be easier to copy only one > > file to any client. > > I don't understand. How can it work with using the TMDA modules? > (Pending, Util, Defaults, etc.). I guess you meant 'without' (else I don't understand your question) ? The answer is: by inserting a network layer between the lib (TMDA's modules) and the graphical interface layer. If import TMDA fails, then ask the user (or read a config file) for a remote host:port to connect to a server. Benefits: - tmda-gui can be copied and run from virtually anywhere in the world - web/graphical interfaces can be developed in any language - if the server is run as root, no need to chmod 777 ~/.tmda/*, but fork to become the real userid after authentication (like tmda-ofmipd). > I don't think confirmed and released messages should be visible at > all. None of the other pending interfaces (tmda-pending, tmda-cgi) do > this, so I think it will just be confusing. OK > I think the message id is OK, but another option would be to display > the date of the message id instead. e.g, <snip> > A method could be added to Pending.py to make this calculation more > convenient perhaps. Done. Thanx for the piece of code. > The message id list is good to keep under the surface though, because > it makes sorting the messages by date/time very easy. Well, it is also the only "handle" to release/delete a message ;) David _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
