- Status Closed
- Percent Complete
- Task Type Feature Request
- Category Backend / Core
- Assigned To No-one
- Operating System All
- Severity Low
- Priority Very Low
- Reported Version Devel
- Due in Version 2.34
-
Due Date
Undecided
- Votes
- Private
FS#10 - Add generic key=value preference system
There are a lot of places where we could use the ability to arbitrarily store data points; things like custom fields for images, raw decode parameters (they're always changing!), or per-album/folder sort order (for things like subalbums, not just images!)
In any case, I'd definately like to see things like the image processing options moved out of their rigid, fixed database table.
Closed by pizza
2007-02-09 00:03
Reason for closing: Implemented
Additional comments about closing: Another old, old ticket implemented! key=value across the board, and eliminated four tables in the process!
2007-02-09 00:03
Reason for closing: Implemented
Additional comments about closing: Another old, old ticket implemented! key=value across the board, and eliminated four tables in the process!
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
The unification of the session lookup code has already started to rope in a few preferences. Once the new session stuff is completed, we can extend that code to look up the preference data too, and alter all pages to use that data instead of looking it up themselves.
Once the lookup/sets are centralized properly, we can much more easily move to a key=value model, as it'll just mean modifying code in one place for *all* lookups, and of course the pages that actually write preferences too.