Text-Fabric is a core engine with an app infrastructure. Here is a quick overview of the main parts of the code:
- The core API of TF: TF core code
- The search API of TF: TF search code
- Writing system functions to deal with complext writing systems and transcriptions: TF writing code
- Conversion functions to convert to and from the Text-Fabric format: TF conversion code
- An app-API offered by TF that TF-apps can use: TF applib code
- A web interface and data kernel: TF server code
- The TF-apps themselves. They are outside the this text-fabric repo, you find them under the same
organization as the repos whose names start with
-app.
Text-Fabric has parts that deal with long tables of data, especially the core part. Here we adopt a plain, iterative style for performance reasons.
Parts that face the user directly, e.g. the top-level parts of an API are suitable for Object Oriented programming. We refrain from adding an OOP flavour all the way down to the smallest particles of data.
However, in many cases we prefer Functional techniques to organise functionality: taking functions as arguments and delivering functions as results of other functions.
In the Javascript parts we particularly are function-oriented.
Programming the core requires ordinary Python programming and a bit of HTML + JQUERY + Javascript for the web interface parts.
We use Python3 (currently 3.6.3) and ES6 Javascript.
In this project we use linters and formatters for both Python3 and ES6.
The linter and formatting options are in this directory:
Note that in both languages
- we use an indent of 2 characters; in Python we use 2 chars for control of flow indenting and 4 chars for sub-expression indenting;
- we prefer camelCase names; in Python we use underscores only in ALL_CAPS names, mostly constants, and private methods may start with an underscore.
We still do not have a formal release procedure with evaluation of intermediate releases. The user base is still small, and we react fast to upcoming requirements.
Once we have more diverse users and more developers, we will consider a more thoughtful release procedure.