-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make it ready #31
Comments
demo |
When you're ready to try it out OS X, push the source and I can see if I can get it to compile and test it on iterm2. |
Thank you for your attention to the project. This is a good motivation for work when the project is interesting not only for the developers themselves. The situation here is a little more complicated than just building for a specific platform. The VTM project depends on the Desktopio TUI Engine, which is the engine that powers all the UI and rendering in the VTM. Desktopio is being developed from scratch as a standalone project without any dependencies and has never been published anywhere. At the moment, it is not clear whether the TUI concept is a relic of the past and should be forgotten in favor of the GUI, or simply its potential has not yet been fully revealed. The VTM should clarify this and show the Desktopio Engine perspective. Its source code will be published in the individual repository of the NetXS-Group. The VTM source code in this repository will end up with the following structure:
|
Thank you for the clarification, that provides the details I was interested in. And while I am knowingly in the minority, I like the TUI as I do my work from the command line and text based tools. So, providing a similar environment to GUI without the requirements of a GUI would provide an environment that I could be more productive with and look forward to being able to use this in both OSX environment as well as Linux (I don’t do ms windows). |
All sources are now available, and you can compile this project yourself. The sources for VTM and Desktopio Framework (namespace nexts::*) are not yet separated and are in the same project, as many changes are expected, and changes affect both at the same time. Later, I will make the Desktopio Framework as a header-only library to make it easier to use in other projects. |
Problem Description: Source tree says it's not ready.
Expected Behavior: There's code in the source tree that builds.
The text was updated successfully, but these errors were encountered: