How to understand the structure of this code better #2644
Replies: 2 comments 3 replies
-
It is difficult to understand the code. The documentation consists of a few files in the Technical section (see https://divinumofficium.com/www/horas/Help/technical.html), and inline comments, which are often wrong and always inadequate. Fundamentally the code does this:
but these processes are not at all modular and it is not actually a pipeline even if it could be. Also it is written in an old dialect of Perl and without regard for even elementary programming principles. Soon (but not too soon) I'll post (and we’ll put in production) a comprehensive revision which takes a first step towards improvement, namely : declaring all the variables and turning on warnings, and rationalising the options processing a little. Just that is already non trivial. Later (but not too much later) I’ll post to production a second step which will make the pipeline visible and modular, using objects and methods instead of global variables. After that, we should be able to move the HTML to HTML5 with CSS, and expose a real mobile UI and real APIs on the network and standalone. But not before, because the code is far too brittle at present. |
Beta Was this translation helpful? Give feedback.
-
Dear Andrew, |
Beta Was this translation helpful? Give feedback.
-
There is any doc detailing all the architecture of this code?
I want to contribute more, but I have a lot of doubts about it...
Beta Was this translation helpful? Give feedback.
All reactions