I am now switching smoothly between working on Rope and Leo. There is no longer any friction (mental effort) in doing so.
Working on Rope has given me a new perspective: I recently simplified g.printObj and related code. I needed similar code in Rope; it was unbearable to use complex bespoke code when a thin wrapper on python's pprint module sufficed. Aha! Neither leoInteg nor leoJS care about g.printObj. Aha! Some of Leo's (core) code will become part of leoJS. Some will not. This distinction changes how I think about Leo! Working on Rope has also created a surprising Aha about studying code. I'll discuss this Aha in a separate post. 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/059567fa-ee37-46eb-8916-9c48c3c27d59n%40googlegroups.com.
