Update 2.2: released

Maintainability is the intention of this Revision 2.2 which achieves several goals, among which, bringing a clear schema of the execution modes, introduce formatting help (libfmt) and output classes (UnidCells, GraphicSet), review coding practice and algorithms. This last objective led to the suppression of several redundancies and the introduction of more or less successful stylistic … Continue reading Update 2.2: released


Update 2.2: development within the limits of an hybrid system

Announcement of next Unidatab’s release (continued). Based on a static, single-threaded process, Unidatab is a hybrid system in which principles of programmation don't apply well. For example, having classes corresponding to the main objects we are dealing with isn't essential here and could even be disturbing when these objects already exist preformatted in the underlying … Continue reading Update 2.2: development within the limits of an hybrid system

Update 2.2: purifying Unidatab

Announcement of next Unidatab's release. The clarity reached by asking the right question, has consequences on the technical side, for we can now see what wasn't necessary in the previous architecture of Unidatab. In spite of the support I could get from the writings of respected scientists, it has become clear for me that properties … Continue reading Update 2.2: purifying Unidatab

CGI : write access restored

With version 2.0 of Unidatab, Unidatab-CGI had lost its ability to modify a database. The problem was coming from the strengthened access restrictions server-side and not easy to tackle at once, involving changes at various levels. Additionally, Unidatab-CGI (https://github.com/emilbarton/Unidatab-CGI) now offers a very basic style sheet in need for extension too; not real handy yet, … Continue reading CGI : write access restored

Version 2.0: the splitting of the node table

[ UPGRADE WARNING for Unidatab 2.0: The new version brings structural changes, in consequence older databases have to be migrated to the new standard (see this link). Besides, some functions have been improved in syntax and output. Therefore old documentation will reveal inappropriate in some cases and will be corrected gradually in the near future. … Continue reading Version 2.0: the splitting of the node table