On 10/26/12 1:53 PM, Chris Cunningham wrote:
On Fri, Oct 26, 2012 at 10:33 AM, Bob Arning arning315@comcast.net wrote:
This got me thinking and I cannot recall an instance where I actually benefited from having doits in the change log. Perhaps the simplest thing in your case would be to disable writing doits to changes. YMMV.
Cheers, Bob
There are 2 places where it was useful for me (and at least one of them is fairly important!): 1 - Class definition is stored in the change log as a doIt (as is class structure modification). You probably don't want to disable this.
Right, none of the browser-generated stuff, just the cmd-d (p/i/etc) in a text pane.
2 - when I am working, I often craft proto-type methods in a workspace
- if the system crashes during this time, having the doIts can be very
useful.
I guess that's a YMMV situation. I generally do all that kind of thing as a method in a class.
-Chris