On Feb 21, 8:47 am, Kent Tenney <[email protected]> wrote: > It's hard to watch and not be consumed by envy of his tools. > So the challenge is scaling that desire down to my capabilities.
Haha. > So, can I create a task list which feels aligned with, (at my scale) > the advantages he demonstrated. Yes. We have to start somewhere. Probably with a prototype, rather than with Leo itself! > For me it comes back to hooking events. An interesting point of view. What I like about the first demo is that the events happen in both directions: from the code to pictures, and from pictures to code. Neither direction seems at all easy to me. > The stuff he demo'd looked like frameworks of event hooks, the keyboard and > mouse watched carefully informing a layer of interpretation which drove > graphics, and fed back to the text. This is indeed deep structure. > We have some of that in the rendering family of tools. Are you talking about Leo's rendering pane? > There is room for improvement in Leo in the event tracking scaffold. Well, that's an understatement. I know from experience just how difficult it is to have bi-directional interaction with Leo's outline. The demo is simply mind-blowing in this regard. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
