On Sat, Aug 10, 2013 at 3:05 PM, Terry Brown <[email protected]>wrote:
Done, also added font menu, seeing it was a copy/paste of the color > code. > Terry, please turn this into a plugin asap. This is too interesting and important code to bury in the great Sargasso Sea of scripts.leo ;-) As I write this, it seems that important scripts will be noticed more if they are plugins. True, some scripts (like my recursive import script) seem hard to package as a plugin because it would be clumsy to set the required args. There is another reason why I prefer plugins to scripts: it's not easy to track versions when scripts are presented in emails. Hmm. There is a conundrum here: version control systems work on files, but it's much easier to just dump a Leo script into a Leo node. I've never considered this before... Perhaps a good compromise is to "promote" important scripts into commands (c-to-python) or plugins. But this isn't a general solution. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
