I always expected the focused pane would be c.p, all other panes would have no explicit reference other than being +/- N positions from c.p. I'm not sure I see the benefit of giving them a programmatic reference. The potential downside is serious, needing to wrap a more complicated model around Leo's existing model.
Your get-it-out-the-door solution is the simplest solution and therefor probably the best option. I can't wait to see what you're able to come up with. As discussed in Feb, it could be a game changer for many applications. I'm really excited about cell based (or node based in Leo's case) jupyter-notebook and org-mode style interactions within Leo. On Thursday, September 7, 2017 at 11:48:37 AM UTC-4, Terry Brown wrote: > > On Thu, 7 Sep 2017 05:34:28 -0700 (PDT) > john lunzer <lun...@gmail.com <javascript:>> wrote: > > > Anyway, just checking in. Multi-pane editing is definitely at the top > > of my list and it seems like Terry had put a bunch of work in, would > > be a shame if it never saw the light of day. > > Thanks for the nudge :-) I really should have another look at it. It > basically works, but needs Leo syntax highlighting (probably not a big > deal) and Leo key handling (much bigger deal). > > The challenge is that c.p isn't a clearly defined concept in the new > model. Maybe the best approach would be to make c.p follow the focused > pane as an initial 'get it out the door' kind of solution, then look at > possible decoupling further down the track. > > Cheers -Terry > -- 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 post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
