Ver. 0.1 ALFA 1
I stoped thinking about thermodynamic processes calculator as thing worth working on. I stoped developing this version, it is dead end. It does something, it calculates, and it calculates good, unfortunately only in certain conditions :D. The user has to put correct data. Next version has to be more directed on calculations possibilities and data checking.
APP right now
the program can calculate a sequence of thermodynamic processes, the sequence is set in compile time, no data input integrity is checked. So if user will provide right data for calculations then output will be correct. But everybody knows that user never provide right data ;p And usability of this program is limited due small amount of calculations customisation. A lot must be done before release of the next major version. GitHub commit messages s**ks too.
Next Version – 0.2 – some day
List of things to rethink before starting next version.
- Mollier chart domain of delivered data,
- data integrity against every point parameter?,
- correctness of wanted processes against thermodynamic laws,
- posibility of changing the sequence and the number of calculated processes,
- more understandable developing process – better GitHub commit messages,
What to do now
I learned lately that GUI isn’t so important ;p. Now I think about a program that reads and sends data by serial device. I hope I will write about it on the blog soon. I think that I learned new way of thinking about application developing 🙂 I wrote something about that couple of months ago: a lot must be reconsidered BEFORE writing an application code.
What I learned
- basics of object objected programming – praparation on using basic classes in C++,
- inheritance – whole app is coded with classes and inheritance,
- basics of UML – a part of activities of the app were described with UML diagrams,
- RAII – Resource Acquisition Is Initialization, every resource aquistion should be called in constructor and relinquish of it should be called in destructor