This is the bug tracker for Photo Organizer.
FS#10 - Add generic key=value preference system
Attached to Project:
Photo Organizer
Opened by Solomon Peachy (pizza) - Tuesday, 25 April 2006, 16:21 GMT
Last edited by Solomon Peachy (pizza) - Wednesday, 15 November 2006, 14:20 GMT
Opened by Solomon Peachy (pizza) - Tuesday, 25 April 2006, 16:21 GMT
Last edited by Solomon Peachy (pizza) - Wednesday, 15 November 2006, 14:20 GMT
|
DetailsThere 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. |
This task depends upon
Closed by Solomon Peachy (pizza)
Friday, 09 February 2007, 00:03 GMT
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!
Friday, 09 February 2007, 00:03 GMT
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!
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.