Re: Aha! A better way to study code

Heh - I was half-expecting that answer! No worries, I will do that. (who else looks at code sometimes and thinks ... did *I* write that?!) On Friday, February 10, 2023 at 2:35:57 PM UTC Edward K. Ream wrote: > On Fri, Feb 10, 2023 at 4:34 AM jkn wrote: > >> A slight follow-up to this, might be

Re: Aha! A better way to study code

On Fri, Feb 10, 2023 at 4:34 AM jkn wrote: > A slight follow-up to this, might be a bit OT: How is the icon actually > stored and used in the Leo outline? > I can't tell you anything about this. Read the code, Luke. Edward -- You received this message because you are subscribed to the Google

Re: Aha! A better way to study code

A slight follow-up to this, might be a bit OT: How is the icon actually stored and used in the Leo outline? When I did the simple " insert-icon command | navivate to icon file | select | see result" experiment I took a look inside the resulting outline. I saw something like this: ... body of

Re: Aha! A better way to study code

PS: I agree that to my ear, 'insert/remove' would pair better than 'insert/delete' On Saturday, February 4, 2023 at 5:42:24 PM UTC jkn wrote: > *delete-last-icon * > > there is also *delete-first-icon*, and *delete-node-icons* > > On Saturday, February 4, 2023 at 4:09:06 PM UTC tbp1...@gmail.com

Re: Aha! A better way to study code

*delete-last-icon * there is also *delete-first-icon*, and *delete-node-icons* On Saturday, February 4, 2023 at 4:09:06 PM UTC tbp1...@gmail.com wrote: > I don't see a matching *remove-icon* command, though. > > On Saturday, February 4, 2023 at 9:45:49 AM UTC-5 Edward K. Ream wrote: > >> On Sat,

Re: Aha! A better way to study code

I don't see a matching *remove-icon* command, though. On Saturday, February 4, 2023 at 9:45:49 AM UTC-5 Edward K. Ream wrote: > On Sat, Feb 4, 2023 at 6:35 AM jkn wrote: > >> That's cool, thanks. so even now I can do "insert-icon" / (browse to an >> icon) , and have it be added to a node ;-

Re: Aha! A better way to study code

On Sat, Feb 4, 2023 at 6:35 AM jkn wrote: > That's cool, thanks. so even now I can do "insert-icon" / (browse to an > icon) , and have it be added to a node ;-) > Hehe. I did not remember that. Edward -- You received this message because you are subscribed to the Google Groups "leo-edito

Re: Aha! A better way to study code

That's cool, thanks. so even now I can do "insert-icon" / (browse to an icon) , and have it be added to a node ;-) Amusing how you use Terry's "3rd-party" plugin to reference back to you own code - you are not the first... Cheers, j^n On Friday, February 3, 2023 at 3:15:38 PM UTC Edward K

Re: Aha! A better way to study code

The attached outline has some icons attached to headlines. It was posted for issue 3121 by @wangzhaohe. I don't know how he attached them, but it gives a dramatic example. On Friday, February 3, 2023 at 10:15:38 AM UTC-5 Edward K. Ream w

Re: Aha! A better way to study code

On Fri, Feb 3, 2023 at 6:36 AM jkn wrote: > is it possible to mark headlines with icons of different kinds? Yes. At first I remembered only that it involves adding some key to p.v.u, the user attributes dict. I'll describe a slightly cleaned up version of my study process. Terry's todo plugin s

Re: Aha! A better way to study code

It's always interesting to see other people's work... Two trivial things I noted in rope.leo, neither rope-related 1) you use a checkbox style for 'things to do' which I quite like - [x] a done item - [ ] a 'to be done' item, I presume (haven't seen one yet...) I tend to use the following

Re: Aha! A better way to study code

On Wed, Feb 1, 2023 at 3:35 PM Edward K. Ream wrote: >> I should have said, "*Two or more*" levels... To see the revolution in action, see rope.leo , in the leo-editor-contrib

Re: Aha! A better way to study code

On Wednesday, February 1, 2023 at 10:14:20 AM UTC-6 Edward K. Ream wrote: > This post describes a new (for me) way to study complex code! ... > [summary]*Two *levels of organization provide the space needed to summarize complex data. I should have said, "*Two or more*" levels... For example, in

Re: Aha! A better way to study code

Well, it's not really a bug - you just have to prefix each body of code in the tree with a code language directive (@language code), otherwise VR3 doesn't know that the node is code and not markdown/rst/etc. On Wednesday, February 1, 2023 at 1:51:07 PM UTC-5 Thomas Passin wrote: > You can actua

Re: Aha! A better way to study code

You can actually do literate programming - meaning explanatory text mixed in with code - with VR3, and you can run the resulting program. You cannot directly currently export the VR3 tree to a file, but you can have VR3 display and export only the code, which you can then get from the browser

Re: Aha! A better way to study code

On Wed, Feb 1, 2023 at 10:40 AM Thomas Passin wrote: Yes, one step closer to literate programming without weave, etc. Often I > use << named sections >> as a kind of pseudo-code to clarify what's going > on. I'd like it if we could have organizer nodes like this in external > files, too. Than

Re: Aha! A better way to study code

Yes, one step closer to literate programming without weave, etc. Often I use << named sections >> as a kind of pseudo-code to clarify what's going on. I'd like it if we could have organizer nodes like this in external files, too. On Wednesday, February 1, 2023 at 11:14:20 AM UTC-5 Edward K. R

Aha! A better way to study code

This post describes a new (for me) way to study complex code! *The old way* I created an organizer node whose children are the clones of nodes that I want to study. This study pattern works well for programs that I mostly understand. But this pattern doesn't work so well for more mysterious co