On Thu, Feb 9, 2012 at 2:20 PM, James Bowery <[email protected]> wrote:
> I'd like to get a company I'm contracting with to go Literate with Leo but > we're starting with a Illiterate source code that needs to be incorporated > (hence imported) into Leo. This means we have a _lot_ of work to do, of > course. Moreover, the code is in git repositories and written Perl and PHP > (and maybe some "C") -- nothing is in Python. What I need is something to > introduce the other team members to the use of Leo in this context. An exciting project. I suspect that far less work is required than you might imagine. > Here's an example of a screencast I did for my team members Excellent. No one knows better than I how hard it is to do such tutorials. > I'd like to do a screencast like this for Leo but I honestly haven't been > able to grok how one would go about using Leo to convert an Illiterate > project into a Literate one. > If someone could take some time, at their convenience, to "hand hold" me > through this process, I'd create a screencast tutorial or three with the > experience fresh in my newbie mind. I'd be happy to do this. There is a vital distinction here. The process of converting a project to Leo is one thing, the process of converting Leo outlines to *literate* outlines is actually something completely different. I have often said that Leo shows the limitations of traditional LP. The more I use Leo, the less I like section references, except for references like << imports >>. Having said that, Perl and PHP may be better candidates for LP than Python. Let's ignore, for now, the question of whether LP is right for your project. In that case, the task is to import many project files into one or more .leo files. Presumably, only one project member needs to do this: the others in the project can simply use the created .leo file. Importing large numbers of files into Leo isn't too difficult--I have done it many times. The trick is to use an **import script** to automate the task. scripts.leo contains a top-level of a script called "Recursive create @auto nodes". For each import project, I copy this script to a personal .leo file and modify as needed. You will want to modify the source directory and the types of the files you want to import. You do that by modifying data in the top-level node of the script. Creating @auto nodes is a cute trick: you can immediately see whether there are import problems. When all files import correctly, you can simply change @auto to @file if you like. But you don't *have* to change @auto to @file: you can ease into Leo by using @auto. HTH. Please feel free to ask more questions. 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.
