|
From: Joe z. <jz...@at...> - 2002-08-10 23:09:55
|
I got the admin interface working just enough that you can create server definitions and modify them. It still needs much work. I'm planning to break out the html code from class_config and put it in admin.php or class_admin.php. I followed your "config editor suggestions" email from July 14th. The server definitions are now in config.php. The share input fields will show based on which backup/restore method you choose. I simplified the rules a bit to make life easier on myself. Let me know what you think. The following is a list of some of the things I did and still need to do: ------------------------------------------------------------------------------------------- Admin Interface: done - Show only one password (temporarily) - will be moving user/group/password to another screen. done - Fixup menu buttons. Create images with text, similar to the BOBS user menu. done - Replace server.definitions.ini. done - Add lots of comments. done - class_config.php - Add/change functions as specified in config editor suggestions email July 14. Remove server.definitions.ini from CVS. Take html stuff out of class_config.php. Possibly create a class_admin.php. Classes should be simple. "special" fields: run days - display as checkboxes. Allow for parms to smb, like user id and password per share. Headings "Server: xxx Share: xxx" in edit server details and forward. Edit server modes support - protect fields in delete mode. Change button to "Delete". Show mode on screen. Make "Delete" actually delete. Compare actual screens to design screens and fixup some. Like back/next buttons. Change icon "login" to "login/logout" Redisplay "edit server details" until no more changes and all edits passed. Use saved-config array to compare? wish list item: Allow to search/select from list of network computers (based on subnet) and/or list of shares (nfs, rsync, smb) on the computer. Add input field edits. Add message routines New file and interface for user (and group) administration. Cron: cron/check_loop is hardcoded. create 'make install_cron' INSTALL: Add more instructions on how to uninstall, because 'make uninstall' won't necessarily remove all the files and directories. ------------------------------------------------------------------------------------------- Joe |