Alex,
These are things in no particular order. Because of the nature of SQL, and that you simply can't tack fields onto the end of links.def some utilties are really needed.
The more flexibility that's coded in now, the easier it will be to add/modify the programs later.
Some of these things may sound simplistic, or obvious, but answers will help everyone.
1) backup/restore database -- in the works
-- the ability to chose the back up rotation schedule as previously discussed.
2) add a field to a table -- needs to be a complete solution, in that the field is properly added to all places it needs to be -- and how to make it useable in templates if all variables are not available by default.
3) modify a table (if necessary create new table --> copy old table --> drop old table --> rename table or re-add old table and copy then drop new table)
4) fields I'd like to have added to the category database:
a) short description (used home page/sub page)
b) long description (used on category pages/links pages)
5) ability to make Page 1 of any category/span pages different from subsequent pages. ie: put the long description, hints, help on the first page, and short description on the next pages.
6) file upload -- integration with a program like your fileman, to upload files and graphics and have their size, and other data added to the database automatically. Ideally you can pick the upload area, but putting the graphics in an 'upload' area until validated (like old BBS systems). (I'm working on a kludge to let me do this my way, but it has some general appeal in the area of logos, banners and other forms of graphics (status). If you are interested, I can point you to some very good source code for graphics I've found).
I don't know what else you have on the burner, but the 3-level new mod because it's so popular, and the bug fixes, and backup are certainly at the top.
I know you are working on efficiency algorithms, but MAINTENNANCE UTILITIES for the SQL end are very, very important. A site grows, and doesn't only add new links. Every so often, to remain competitive, a new field to the database has to be added.
Please also keep a very detailed list of changes you make to the program -- even a small change may affect some modification we have made.
Especially now, when the program is still actively growing/changing, your additions and fixes have to be worked into our modifications.
LinkSQL will undergo some major revisions in the near future, it's inevitable. Please take the time to document your changes in the changes.txt AND in the code! Comments can always be stripped out for speed, but they are invaluable to us, your users.
Thanks... and keep it up!!
These are things in no particular order. Because of the nature of SQL, and that you simply can't tack fields onto the end of links.def some utilties are really needed.
The more flexibility that's coded in now, the easier it will be to add/modify the programs later.
Some of these things may sound simplistic, or obvious, but answers will help everyone.
1) backup/restore database -- in the works
-- the ability to chose the back up rotation schedule as previously discussed.
2) add a field to a table -- needs to be a complete solution, in that the field is properly added to all places it needs to be -- and how to make it useable in templates if all variables are not available by default.
3) modify a table (if necessary create new table --> copy old table --> drop old table --> rename table or re-add old table and copy then drop new table)
4) fields I'd like to have added to the category database:
a) short description (used home page/sub page)
b) long description (used on category pages/links pages)
5) ability to make Page 1 of any category/span pages different from subsequent pages. ie: put the long description, hints, help on the first page, and short description on the next pages.
6) file upload -- integration with a program like your fileman, to upload files and graphics and have their size, and other data added to the database automatically. Ideally you can pick the upload area, but putting the graphics in an 'upload' area until validated (like old BBS systems). (I'm working on a kludge to let me do this my way, but it has some general appeal in the area of logos, banners and other forms of graphics (status). If you are interested, I can point you to some very good source code for graphics I've found).
I don't know what else you have on the burner, but the 3-level new mod because it's so popular, and the bug fixes, and backup are certainly at the top.
I know you are working on efficiency algorithms, but MAINTENNANCE UTILITIES for the SQL end are very, very important. A site grows, and doesn't only add new links. Every so often, to remain competitive, a new field to the database has to be added.
Please also keep a very detailed list of changes you make to the program -- even a small change may affect some modification we have made.
Especially now, when the program is still actively growing/changing, your additions and fixes have to be worked into our modifications.
LinkSQL will undergo some major revisions in the near future, it's inevitable. Please take the time to document your changes in the changes.txt AND in the code! Comments can always be stripped out for speed, but they are invaluable to us, your users.
Thanks... and keep it up!!
Wishlist / wantlist