Profiles

Example module: hellotypes, editabledata property.

hasprofile:true on a property is the framework’s most cost-effective mechanism: a single boolean, and the property gains named configuration save/load to the database, without writing a single line of code.

"editabledata": {
  "permission": 2,
  "hasprofile": true,
  "e": { "..." }
}

What this flag triggers, fully automatically

• Save/load: a client sends PS/PL with a profile name; the server builds a snapshot limited to the hasprofile:true properties and writes it to the database (or reads it back). Already handled generically by the framework — nothing to write in the module.
• On the interface side: a module’s “Settings” box only lists hasprofile:true properties; the profile load/save bar only appears if at least one exists.
• Two lists of values, also automatic: each module has its own list of saved profiles (empty at first, populated on every save), and the controller additionally maintains an aggregated list per module type, used by the interface’s profile selector.