5 ms·
The block coding interface looks smooth. I'm curious about how the interface scales for complex projects. The documentation integration is nice. Great work!
by physicsgraph 6y ago
The block coding interface looks smooth. I'm curious about how the interface scales for complex projects.
The documentation integration is nice.
Great work!
- calhoun137 6y agoThank you so much! Well I tried to make it work so that literally any project you have sitting on your system can be imported into the app. In principle it should work, in practice the amount of block code elements can quickly become overwhelming. At the end of wrapping up the beta version, I was using math inspector to create math inspector, this is how I wrote the TextParser[1] class, and there is a certain beauty to the way the files were synchronized, but since everything was still in development I finished up by running a test file from the command line instead, and have not had a chance to keep working on that aspect. I think the more the app gets dog-fooded in this way, the more clear it will become what the optimal UI/UX is. Math Inspector is not an IDE, but it does create an additional visual layer that is kind of helpful during development, especially for quickly testing/iterating any changes [1] https://github.com/MathInspector/MathInspector/blob/master/mathinspector/doc/show_textfile.py https://github.com/MathInspector/MathInspector/blob/master/m...
- vvanders 6y agoIt's a pretty standard practice for shader editors(which are surprise, heavily math based!) and some game scripting engines. The systems that I've seen handle large-scale titles usually had a mechanism to define a "function"/"inner-block" with inputs/outputs and visually show values at the "edges". I haven't seen a system handle refactoring/large scale changes but I saw some pretty impressive things put together by our art/animation/design part of the studio in it.