[Mortar Issues] Issue 101 in mortar: Universal Model Settings Interface

[mor...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium

New issue 101 by charlequin: Universal Model Settings Interface
http://code.google.com/p/mortar/issues/detail?id=101

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

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups "Mortar Issues" group.
To post to this group, send email to mortar...@googlegroups.com.
To unsubscribe from this group, send email to mortar-issue...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mortar-issues?hl=en.