From: Tim E. R. <ter...@ro...> - 2014-01-23 05:47:15
|
On January 22, 2014 10:37:55 PM Tim E. Real wrote: > While looking at the undo/redo code I realized it can be destructive - > changes can be lost if you undo, then change something, redo turns off. > I thought "What if we could keep everything, discard nothing?" > > Thus I give you... Undo "Trees". > > Turns out emacs and vim have had "Undo Trees" for years. > But apparently not many other apps. Look it up! > As you can imagine, it needs a viewer of some kind, which emacs/vim have. > > Imagine being able to go to and from ANY modified state from ANY time > in the project's entire history ! Forgot to mention, I was reminded of... trees... like GIT trees. How about using a real CVS system for songs, changes, and project files? Concurrent music project users? And across the internet? GIT API? I mean... if someone was to simply post a MusE .med file to a CVS repo, it would automatically have CVS tree tracking eh? But is it really possible to go from ANY node in a (GIT) CVS tree to ANY other node and back again? I would hope so... T. |