[Phpsqliteadmin-devel] phpsqliteadmin2 todo.txt,1.1.1.1,1.2

[Slythfox <sly...@us...>]

Update of /cvsroot/phpsqliteadmin/phpsqliteadmin2
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29816/phpsqliteadmin2

Modified Files:
	todo.txt 
Log Message:
Updated todo with more recent entries

Index: todo.txt
===================================================================
RCS file: /cvsroot/phpsqliteadmin/phpsqliteadmin2/todo.txt,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -d -r1.1.1.1 -r1.2
--- todo.txt	24 Jul 2005 12:59:38 -0000	1.1.1.1
+++ todo.txt	12 Jul 2008 23:35:31 -0000	1.2
@@ -1,3 +1,24 @@
+Revised Todo (July, 10, 2008):
+
+ - Don't allow the removal of the phpsla.sqlite alias.
+ 
+ - Error checking for adding database aliases. How should general error handling work?
+
+ - Add row adding/editing/deleting. (I have a basic implimentation. -chale)
+ 
+ - When displaying the phpsqliteadmin version, it should display the number within the configuration table of the phpsla.sqlite database.
+
+ - (?) Reorganization of the main page: Main area should display phpsqliteadmin version, sqlite version, list all of the databases, have a database creation form/alias configuration links.
+ 
+ - Newer layout... use something like $pg['content'] .= "content" to update content rather than using print. That way we only need one layout file, and a layout inclusion at the end of every page. The sidebar should have that phpsqliteadmin logo as well.
+
+ - Better icons!
+
+ - Feel free to add more. I was unsure of a few of entries in the old todo's.
+
+ - Privilege checks for databases?
+ 
+Old Todo:
 - you can add an alias database w/out the alias filled, which is bad...
 
 - you can remove phpsla.sqlite alias, which is bad as well