summaryrefslogtreecommitdiff
path: root/todo
diff options
context:
space:
mode:
authorEudyptula <eitan@mosenkis.net>2009-07-05 13:55:03 -0400
committerEudyptula <eitan@mosenkis.net>2009-07-05 13:55:03 -0400
commit919316aa252440a3f9beed2c1276b4d70a827bab (patch)
tree197edb7e83a87318b03748ecc37d6193f6ea5ce7 /todo
parentSeparated configurations from builds of those configurations, added configura... (diff)
downloadingenue-919316aa252440a3f9beed2c1276b4d70a827bab.tar.gz
ingenue-919316aa252440a3f9beed2c1276b4d70a827bab.tar.bz2
ingenue-919316aa252440a3f9beed2c1276b4d70a827bab.zip
Add javascript-based searching to package adding stage
Diffstat (limited to 'todo')
-rw-r--r--todo7
1 files changed, 4 insertions, 3 deletions
diff --git a/todo b/todo
index b536ae1..3e2c716 100644
--- a/todo
+++ b/todo
@@ -1,8 +1,9 @@
Have backend handle builds that it finds to already be running (break in to steps and store current status)
-*** Make frontend package adding a little more user-friendly (ajax or client-side js search) ***
+Make package adding friendly for browsers without JS/CSS (use ul/li, not div)
+Reduce page size for package adding
Write a live git ebuild
Write an AJAX-based self-updating status viewer
-Add logging besides just commands
+*** Add logging besides just commands ***
Make backend do a dummy run through and queue all commands and other tasks, then execute them (for better status handling, easier debugging, etc.)
Have builds and tasks not give links to logs if we're already viewing the logs
Either make task status a TEXT or stop putting command name in the status (via thrown exception) - we can fetch this later anyway - just store the task id that failed (or use the last task)
@@ -13,7 +14,6 @@ Add configurable groups of suggested packages to frontend, backend
Add a statistics page
Add cleanup functions to the frontend and backend
Separate variables we got from the URL from the rest, stop using $request, instead keep super globals and strip slashes on them
-Get rid of backend use of echo, debug, etc. and do all logging in the db
Support ~arch installation or remove it from listings
Completely plan out how frontend modules should function - each step needs to report if it finished successfully (required values)
See if I can figure any way to use classes instead of funny named functions (namespaces in 5.3.0 perhaps) - also needs to have a depend of some sort so we can make a quick-config page that doesn't show things that we don't have enough info for yet (use AJAX to show them when we're ready)
@@ -21,3 +21,4 @@ Allow backend to define bail-out functions to call when it dies (things like unm
Add STDERR (maybe STDOUT) only option to log viewer
*** Make frontend/backend split possible *** - Stop directly accessing PKGDIR from the frontend - put whatever info we need in the database and write a script for updating it from the backend; track which backend is doing which build
Simplify status to numeric on builds, configurations - varchar isn't necessary
+Add config option to enable/disable user self-registration/invitations/admin-only invites