3 ms·
Of course a tree would be best. I just wonder whether can be presented in a way that is still intuitive for common users. I'm thinking one could emulate a linea
by DeepDuh 14y ago
Of course a tree would be best. I just wonder whether can be presented in a way that is still intuitive for common users. I'm thinking one could emulate a linear history on top of the tree and just present the tree when desired by the user. Also, it would become very important to figure out what exactly is the most usable level of committing (words? phrases? text blocks?). I'm thinking about a system where a linear edit to one element of the underlying data structure (such as an xml element) is one commit, even if it's a whole story.
- dllthomas 14y agoInteresting - and I suppose obviously your history can be mapped onto a line with some loss of expressiveness, if you view it strictly as time. As long as the more detailed history is available, I do not object to exposing it that way as well or (necessarily) even primarily; I just wanted to be sure it wasn't being restricted unnecessarily.
- DeepDuh 14y agoThanks for your input. Yes, this is always one of the hardest things in UI design: Do I optimize for the "power user" (yes that dreaded word again) or the common user? Can I do both without any compromises? Besides possible monetary benefits it would immensely calm my ego as a developer having made something both easy and powerful. A good example of this principle IMO is Apple Pages and Numbers. They are both succeeding at being powerful/expressive when you need it (Cmd-alt-i) and easy for the other times. It's just a shame that they haven't been updated and still lack some important features like plugins and bibliography.