- Joined
- Feb 6, 2008
- Messages
- 37,632
- Reaction score
- 2,350
- Points
- 203
- Location
- Wolfsburg
- Preferred Pronouns
- Sire
Due to the problem of using libUltra explained by SiameseCat I thought that we were stuck with C++. In that case between Qt and WxWdigets it will be Qt IMHO. However, it's true that doing communication between applications may be easier in other languages.
---------- Post added at 11:44 ---------- Previous post was at 11:41 ----------
Also, on the other side you have the SSU lib code which is C++ too. So if you have to communicate with a C++ compiled app (SSU) maybe it makes sense to use C++ for the client too (SSUToolbox/MCC).
I don't agree on having to use libUltra. It is a nice to have, but the amount of really useful code for a mission control application is tiny there. It is not that much, as that we will really have any benefits from depending on it.
What matters is not the implementation, but the algorithm. Also, I see libUltra as something for real-time simulation, which will always be designed for faster calculations in Orbiter than perfect accuracy or simple to understand.
We can't make one C++ library that is perfect for all applications, having a Java or C# library that has some intersections with libUltra, but then having spaceflight related functions for visualization and not all the Orbiter-specific stuff would be smarter.
I feel like you oversophisticate things - and that I get this feeling should be a terrible warning sign, because oversophisticating things is usually my job here.
Also: We should use the toolbox and the mission control application as primary research driver to get a better working Mission file format. What we currently have was a first quick shot at it and I would like to keep the next iteration close to it, but as you can easily see, it is extremely limited and not even slightly suitable for the task. We should define a better format that can be used by such an external application without too many considerations of how this will work with the SSU vessel module. Otherwise, we are already thinking about the problems we will have in 10 years, and not about the problems that are directly in front of us.
I think, I should maybe make the JavaFX prototype a project independent of SSU and for all Orbiter or non-Orbiter projects and leave you some room here to do yours. Just as some kind of comparable project.
Last edited: