On Wed, Jun 10, 2009 at 6:54 AM, jkn <[email protected]> wrote: > > > Ah, excellent - so leoPluginsRef.leo is the 'parent' file for all the > derived .py files etc.
Right. The new terminology is "external" file instead of "derived" file. That switch-over hasn't been completed in the docs. To my knowledge, there isn't any official term for what you are calling a "parent" file, that is, a .leo file containing an external file. Perhaps there should be. > > > I hadn't seen this 'use case' (story ;-) in the docs. There's a > definite gap between Chapter 2 and Chapter 4 I think. Info on this > sort of workflow would IMO be a *big* help up on the learning curve. Let me say here that Leo's introductory chapters could be significantly improved. This point was brought home forcefully to me as I have been trying to understand calioPY. I suspect the calioPY docs are *almost* enough to get me to see the big picture, but I am still struggling. Newbies don't want to spend much time learning. We are all so inundated with possible new tools and projects that we typically give ourselves just a minute or two to judge whether a project is worth the effort to learn. So in Leo's case, the intro would, ideally, be something that somebody could scan in just a few seconds. It would convey the "Aha" behind Leo, and not much else. So far, I haven't discovered how to do it :-) As you say, after Chapter 2 gives the Aha, another section of documentation would give examples. Or maybe the examples would *be* the Aha... 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 -~----------~----~----~----~------~----~------~--~---
