Chris Brown

Results 53 comments of Chris Brown

Here is an example script showing the C++/ChaiScript interaction ![image](https://user-images.githubusercontent.com/7495752/73113209-758fe500-3ec7-11ea-903b-26d1cb1d268f.png) ![image](https://user-images.githubusercontent.com/7495752/73113224-95bfa400-3ec7-11ea-93f7-aa02a8668a9a.png) And here I'm showing the chaiScript syntax, paired character, and currentline highlighting. Also the line numbers are displayed. ![image](https://user-images.githubusercontent.com/7495752/73113322-0961b100-3ec8-11ea-920c-aea7b90d7f66.png)

I have begun adding in the CCLib::CCGeom types and testing as I go, I can create CCVector(both 2d and 3d, using templates so all the same types available in c++...

Thanks @dgirardeau I am mostly at this point interested in the teams thoughts on the organization of the plugin, folder structure and class hierarchy. It is still far too early...

![image](https://user-images.githubusercontent.com/7495752/73311329-0b36b780-41db-11ea-890c-18ac1b9c389a.png) The plugin is almost somewhat useful, at least it can do something that there currently is no method in the main CC for a user to do.

Hey @dgirardeau have you had any chance to look at this at all? Here is todays new status. The plugin can now execute chai scripts from the command line, and...

Great, I'm pretty happy with how it's shaping up, I am reasonably confident in how the code that exposes the CC C++ to ChaiScript is done, it is essentially the...

> There's a QCoreApplication::aboutToQuit() signal. > Would that working timing-wise or is that too late? I didn't know about that signal... I will try it out. I had just noticed...

@asmaloney the QCoreApplication::aboutToQuit() signal appears like it is fired too late, I still could cause crashes when using it. but this worked for me ```C++ qAddPostRoutine([]() {ChaiScriptingPlugin::TheInstance()->destroyChai(); }); ```

@asmaloney @rjanvier Hey BTW since ChaiScript is cross platform, I figured I should follow the various platforms for folder search paths for scripts and modules. Modules are just shared libraries...

I was thinking I would add a configuration menu that let the user set additional search paths and save them to the QSettings for this plugin so they should be...