Hi Allan (and others:),
Recording and saving macros is great, editing macros is even greater. With commands like "pastePrevious:" and "pasteNext:" we can do a lot of work. But we have to record and edit a lot of macros to find all available commands. So, to spare us time, will you publish the commands list?
Thanks,
On 14. Oct 2004, at 10:48, José Campos wrote:
But we have to record and edit a lot of macros to find allavailable commands. So, to spare us time, will you publish the commands list?
hehe... but officially I condemn all who manually edit their macros! ;)
Why is this easier than recording your macros?
Kind regards Allan
Allan Odgaard allan@macromates.com wrote:
hehe... but officially I condemn all who manually edit their macros! ;)
life|death sentence?
Why is this easier than recording your macros?
When I have recorded and saved a macro that works fine, and need a new one, slighty different, I think it's quicker to edit the first one than recording a new one.
On 14 oct. 2004, at 13:52, José Campos wrote:
When I have recorded and saved a macro that works fine, and need anew one, slighty different, I think it's quicker to edit the first one than recording a new one.
Not to mention fixing potentially inefficient macros, have a look at the "Insert ISO Date" one, in the Defaults bundle. Yuck !!
In my opinion, macros should be implemented through AppleScript recording/playing anyway, instead of this ObjectiveC selectors list hack. Don't you think ? :)
On 14. Oct 2004, at 15:49, Luc Heinrich wrote:
Not to mention fixing potentially inefficient macros, have a look at the "Insert ISO Date" one, in the Defaults bundle. Yuck !!
If you're doing that, I'd say you have too much free time! ;)
In my opinion, macros should be implemented through AppleScript recording/playing anyway, instead of this ObjectiveC selectors list hack. Don't you think ? :)
So why is this a hack? actually, internally many of the things are _not_ ObjectiveC methods, I just expose my functionality as named selectors, so that it also works with key bindings etc. Why not re-use that functionality?
But down the road there will of course be AS support, and it'll be recordable. But Rome wasn't build in one day, and I think it's much better to have recordable macros in first version, than non-recordable AS.
Wasn't the reason for "text factories" in BBEdit 8 actually that AS simply was too complex for most users? ;)
Kind regards Allan
On 14 oct. 2004, at 17:07, Allan Odgaard wrote:
If you're doing that, I'd say you have too much free time! ;)
Doing what ? Trying to fix potentially inefficient macros or looking at their guts in the first place ? :)
I'm still tinkering with a bundle editor, so yeah, I have looked at these pretty closely ;)
-
Allan Odgaard -
jose.campos+tm＠galacsys.com -
Luc Heinrich