hi Mats This is a brilliant idea and as you say is better than a bunch of cumbersome .bak files lying around. I haven't had too much time to explore the Commands (alas!) but it also sounds very feasible.
Could it be built into TM so when a project ("myproject") is created, a separate "myproject.log" or something is automatically created? Then there could be a way to "flush project log" (like flushing cache in Safari or Firefox)...
p.
On 15 Jan 2005, at 00:35, Mats Persson wrote:
OK, so what do you get out of this in the end. Well, you get sort of a log of all changes in an individual file in a single backup file for that file with dividers that sets the date etc info as you wish to have it and the code as it was at that time. Each file in your project would have it's own backup log file in the BackUp repos.
If you don't want a single log file but multiple files, well then that can be done just as easy, although I think it's pointless to be honest, because you will have to open loads of files to see what changes you have made. In my version your last saved version is always at the bottom of the backup file. Now this is NOT as good as you using CVS or SVN, but I'm working on solving that problem as well on each save.
Give us (me) your spec's and I'll see what we can do about it.
This command based workaround would only require Allan's mind for only a few minutes to implement (I'm sure) versus something that will take longer time to implement, and would not have a much better result. (at least in my mind)
I hope the above is ample illustration of how BBEdit can't compare to TM, and how we all need to "Think Different(ly)" about TM, since many things can be achieved with Commands and a bit of Unix knowledge.