Greetings to all!
Since renatose already introduced me, I'll skip the introductions
@jimbauwens: I've finished looking over EEPro's manual and by what I can figure out, the common denominators between EEPro and Asstermo are:
- The need for detailed interaction with the user, not just a simple QA interface, nor RPG/game like interface (just clicking around).
- EEPro it's very heavy on equation inputs; Asstermo only needs equations for the combustion part (about 10% of the code).
- EEPro uses graphs for some simple finance issues; Asstermo uses this for psychrometrics (not psycho, psychro as in "cold measurement")
Other than that, Asstermo is very heavy
on table lookup (60-70% of the program). I've never looked very well into MEPro, so I'm not sure of what it does.
So I propose that instead of merging both projects, we instead create a common project for creating the infrastructure/framework for the user interface, or even a fully working GUI framework. Associated with this can be the translation mechanisms as well, since it's directly related to the user interface.
This has been the one big detail that has always kept me away from the almighty-powerful
TI-nSpire calculators: TI took away our beloved
dialogs and menus...
Currently the tasks on Asstermo-D (the new variant of Asstermo for nSpire, where D is for Document) are split as follows:
- Porting TI-Basic code from TI-89 to TI-nSpire - wyldckat
- Lua based GUI for replicating an user interface similar to TI-89 and then interacting with the TI-Basic code - renatose
- Simplified translation mechanism for extracting texts from Lua onto XML then back to translated Lua, using Qt Linguist for XML translation - base infrastructure by wyldckat for Lua->XML->Lua and all of the Lua code by renatose
The objective is to have the GUI in Lua and the legacy code in TI-Basic, in an attempt to save time in both coding and documentation! The translation mechanism is inspired and based on Qt's Linguist translation software (Qt is at its core an UI framework
), but since Qt is C++ and too complex for nSpire, therefore the need for writing an app to pre-process Lua to Qt Linguist compatible XML and post-process XML back to Lua.
So, what do you guys think? The other advantage of creating the GUI framework is that many other programs can take advantage of that framework and more contributions can flow into this common project and benefiting all projects which use it!