It is still not certain whether or not the GUI is necessary at all. It still needs to be shown that *only* GUI is fit for the goal of seeing how the change in the data parameters will affect the structures on the lattice. What is wrong with achieving this goal in the plain text mode. I am now considering abandoning GUI altogether.
In my previous attempts to build a prototype, I tried to concoct some kind of a multifunctional application, which turned to be too time-consuming for me to finish it within my between-the-jobs window. I would like to emphasize that the goal of the project is to create research tools, not the end-user application. It is a good idea to forget about the multifunctional GUIs, and focus on releasing something very simple that, perhaps can do only one thing well, that is to display changes views synchronously in the interactive mode as a response to the changes in only one control. No tabs, everything is on one form. I must scrap the tab-based prototype created last year.... read more
I decided to follow three directions of the project: GUI, computational, and theoretical. To be able to work on GUI independently, I want to specify interfaces (this was in part done earlier).
The proposed logical re-arrangement is that the development should be split into two independent parts - the GUI, the data generators, and the analyzers. These parts should be decoupled from each other.