Quote from: lossendae at May 18, 2011, 03:54 AM
But the point of those global vars would be to be editable from a resource edit page, not from a CMP.
Do you mean that the field would show up when editing
any resource - perhaps on a ’settings’ tab alongside the TVs tab? Sure, that would work, but as a personal preference I would rather have them in one separate location. Perhaps under the ’Site’ menu.
Consider this: when editing a resource, all fields available - pagetitle, content, tvs - apply
only to the current resource. Why confuse things by adding site-wide settings in the same place? In that context a client might edit a global setting thinking it only applies to the current page, but then the whole site has changed. Also, why clutter the resource editing page with settings that are unlikely to be changed very often?
Those are just my thoughts... I would say both are valid implementations depending on the project