In this thread I shall attempt to explain everything my successor will need know about Leo in order to carry on after I am gone. For the record, I plan to work on Leo for as long as I am able to do so.
I am particularly interested in explaining why Leo is the way it is so that those who work on Leo in the future will not be tempted to throw out excellent code merely because they don't understand it. Imo, that would be very sad. As I think about this project, I realize that the documentation will be unusual in many respects. Indeed, it might be said to be the antithesis of Donald Knuth's literate documentation. The emphasis will not be on the code itself. The emphasis will be on the ideas, attitudes and practices that I have that allow me to make large or small changes to Leo easily. If I can communicate these ideas, attitudes and practices to somebody else, that person can successfully move Leo forward. This thread will have many parts. It will be pre-writing for a greatly expanded and updated theory of operation chapter. Enough for now. The next post will give an overview of this project. 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.
