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
Alongside developpement of the new file format, a plugin for Ogitor would help
visualisation of procedural scripts.
There would be raw visualisation of a given operator output + in-situ
visualisation, ie the ability to put procedurally generated objects into the
ogitor scene (especially great when placing meshes shaped for the terrain, aka
roads and the like).
Original issue reported on code.google.com by michael.broutin@gmail.com on 6 Apr 2012 at 9:10
The text was updated successfully, but these errors were encountered:
As the file format is not yet available, and won't be available soon, the
easiest thing we could do, for starting, would be implementing a lua
interpreter as an Ogitor plugin.
The interpreter already works standalone, but integrating it in an IDE would be
a way for users to quickly experiment without having to configure their own
project for OgreProcedural.
To even simplify things further, we could display a combo box with the list of
bound classes and methods.
Original comment by michael.broutin@gmail.com on 26 Nov 2012 at 3:39
At the moment, a placeholder has been added.
It builds as an ogitor plugin that is accepted by Ogitor, but doesn't do
anything.
I'm gonna first experiment a little bit with ogitor before doing the real
implementation...
Original comment by michael.broutin@gmail.com on 7 Dec 2012 at 5:02
Issued a bug on the Ogitor tracker, will resume after it is fixed :
http://tracker.ogitor.org/projects/ogitor/issue/view/938
(At the moment, it's not really possible to have a dialog box + the text
editor, and I'd like to display the script result in such a window)
Original comment by michael.broutin@gmail.com on 19 Dec 2012 at 10:14
Original issue reported on code.google.com by
michael.broutin@gmail.com
on 6 Apr 2012 at 9:10The text was updated successfully, but these errors were encountered: