Page History
...
| byCode | byFile | ||
|---|---|---|---|
| See changes in config tree | could do | could do | |
| Benefit of code completion | yes | no (Could theoretically have something like that with an xml file with a dtd.) | |
| Easily see hierarchy | no | yes | |
| Good for non-java dev. | no | yes | |
| Possible to export from configTree | could do | yes |
Thought experiment: what if all bootstraps were installed everytime you restarted admin central?
So you would treat hand edits to the configtree as only experimental and temporary - like using firebug or browser dev-tools. You would know you have to "persist them" officially somehow. Hotfixes no longer possible.
Additionally - imagine that anytime the bootrap was changed it is reloaded. (problem with ordering, what if two bootraps write the same node, 2nd one overwrites. Then you edit the 1st file. Now repo is incorrect.)
So you could do your "hotfixes" by editing the files themselves.
Maybe a solution could be that if you edit in adminCentral - your changes are saved to a "manual change" layer - which is actually stored in another repository or file. This can be viewed independently and is therefore easy to re-integrate.
Thought experiment: could the repository know from which file all config comes from? What if whenever a bootstrap is loaded, an additional propertly is written to the root node in the config tree - the filepath of the bootstrap. So from any node you can walk up the tree to determine which bootstrap actually wrote that value. What about MVH, would they also write a note to root of every node they change? Or would this eliminate need for MVH?
Inplace editing of Templates & Resources: Access filesystem
...
Overview
Content Tools