You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I work at Intuitive Machines, which makes extensive use of Trick (thanks!), and I'm also the director of the SciRuby Project, which has participated in the last few Google Summers of Code.
I'm happy to mentor for this project, but wanted to see how you felt about it. I wouldn't want to have someone spend three months coding something that you weren't interested in merging.
Cheers,
John
The text was updated successfully, but these errors were encountered:
Thank you for the offer, but maintaining one interface language is quite enough for us to handle. So at this time I am not interested in merging in another Interface.
Trick has the capability for users to insert alternative scripting interfaces. We even do it ourselves with our alternative c++ compiled input file. See the sim_object in our default_sim_object.sm file and the class underneath it. You can build your interface as a user model and not have to merge it in with Trick's source.
Hi there,
I work at Intuitive Machines, which makes extensive use of Trick (thanks!), and I'm also the director of the SciRuby Project, which has participated in the last few Google Summers of Code.
I was thinking it might be a good summer project for a student to create a Ruby interface for Trick:
https://github.com/SciRuby/sciruby/wiki/Google-Summer-of-Code-2016-Ideas#ruby-api-for-nasas-trick-simulation-environment
I'm happy to mentor for this project, but wanted to see how you felt about it. I wouldn't want to have someone spend three months coding something that you weren't interested in merging.
Cheers,
John
The text was updated successfully, but these errors were encountered: