I, the author, am undertaking no work on this project at the moment, and this is unlikely to change for the foreseeable future.
The reason is that openmolar1 is working well in my practice, despite the crappy backend design.
Any work I do adding new features and correcting bugfixes in Openmolar1 are, therefore, instantly rewarding.
regards
Neil.
The text was updated successfully, but these errors were encountered:
It's not ready.
Feature list of openmolar 1 is approximately 100 times more than that of openmolar2.
I'll switch to openmolar2 if (and when!) they are feature compatible. At current rate of progress I made have retired or sold my practice by then.
This is a classic case of writing a version for others to be used being much more difficult than getting one written just for oneself.
A General practitioner, and an programming a bit as well.
--
Dr. Christian González
nerdocs.at
Am 1. Februar 2018 05:54:02 MEZ schrieb Holger Otto Andre <notifications@github.com>:
rowinggolfer commentedMay 21, 2014
I, the author, am undertaking no work on this project at the moment, and this is unlikely to change for the foreseeable future.
The reason is that openmolar1 is working well in my practice, despite the crappy backend design.
Any work I do adding new features and correcting bugfixes in Openmolar1 are, therefore, instantly rewarding.
regards
Neil.
The text was updated successfully, but these errors were encountered: