PhiloLogic4: The Big Picture

While Clovis and I continue to document various aspects of PhiloLogic4's architecture and design, it may be helpful to keep in mind a sort of top-level "bird's-eye view" of the system as a whole.  PhiloLogic does a huge number of different things at different times, and it can be very difficult to keep them all organized. My best attempt to convey it in a single diagram is below: As with PhiloLogic3, the foundation of all PhiloLogic...

Read More

General Overview of PhiloLogic4's Web Architecture

Very early in the development of PhiloLogic4, we decided to separate the core library (the C core and Python bindings) from the actual Web interface. While there is still a clear separation between the Web environment and the library code, the two are nevertheless interdependent, which is to say that one cannot function independently of the other (unless you intend to use the library functions on the command line...) As such, the Web component of PhiloLogic4 was designed as a Web Application, and each database functions as...

Read More

PhiloLogic4 Load Script Architecture

Clovis and I have been doing a great deal of work lately on PhiloLogic4's document-loading process, and I feel that it's matured enough to start documenting in detail.  The best place to start is with the standard PhiloLogic4 load_script.py, which you can look at on github if you don't have one close at hand: https://github.com/ARTFL-Project/PhiloLogic4/blob/master/scripts/load_script.py The load script works more or less like the old philoload script, with some important differences: The load script is not installed...

Read More