Leo : Examples The Evisa Site

This has been a brief overview of the language applications at evisa.com. As you can see, all of the code, and virtually all of the supplemental information needed to work on this application is embedded in one Leo file. The programmer opens the file, works on the application in Leo, and then tangles the output code files.

This application was written in Perl, because of Perl's excellent text manipulation capability and speed of development. There is no scalability problem with this kind of Perl application, because it runs with Apache mod_perl. While programming this application in certain other languages would have given it some more inherent structure, this would sacrifice some of the advantages of development with Perl. In fact, one can think of Leo doing for the supposed "structure" problem of Perl what mod_perl has done for the scalability problem. The application as written in Leo simply could not be easier to understand.

Are there alternatives to this approach? There are more than fifty files embedded in this one Leo file. Every file is grouped and described not just with a name, but with whatever additional information is necessary. Some files are sharing components, i.e. nodes.

This application was developed on a very constrained budget and simply would not have been possible without Leo.

28 of 28
Text Author: Joe Orr Copyright 2002 All Rights Reserved
Created with ScreenBook Maker Last update: 8/3/2002 Additional Trademark and Copyright Information