Build a universal system (actions interfacing with a series of database
tables) for storing model settings. Each setting would be registered (as a
plugin) by a specific module, and then be added to a settings form for
that model type where the settings could be tweaked.
Ultimately this system should roll in existing systems of module-specific
model settings, such as the Graffiti action to allow various models to be
tagged and categorized, as well as the default markup for each model that
uses richtext inputs.
(3:21:00 PM) tedivm: havig a "modelsSettings" table with group/name, and
then a "modelsSettingsValues" table with an fk to the modelsSettings table
and Models table as well as a value column?
(3:21:37 PM) tedivm: but we'll need a little more than just that, because
we'll want to pull in the custom form items and stuff rather than simply
just generating forms
(3:22:09 PM) tedivm: like the group/name would correspond with the form
section/input thing
(3:22:30 PM) tedivm: but then we need to find a way to deal with options
that are only available for some models, things like that
(3:22:40 PM) tedivm: and it doesn't even touch on how to deal with
locations
Original issue reported on code.google.com by charlequin@gmail.com on 25 Apr 2010 at 7:26
Original issue reported on code.google.com by
charlequin@gmail.comon 25 Apr 2010 at 7:26