well so far I don't know how to do this for example is I sent EphParser bpy data materials:'["Material"]' diffuse_color: '=(1.0,0.0,0.0)'.
bpy is sent to doesNotUnderstand: but data is sent to Object cause the debugger complains that Message(Object)>>messageNotUnderstood Another problem is that even if I get this to work how I know where the python command ends ? Where is the period that separate command statements ? Without knowing where the command statement end I cannot formulate correct python strings. The advantage of sending the whole thing as a single keyword message is that I know its one unit and its easy to parse it to a string since the whole thing gets passed to doesNotUnderstand message as argument. I am no expert on pharo so if anyone has better idea I am open to suggestions as I said also in the video. On Sun, Jul 20, 2014 at 10:06 PM, Damien Cassou <[email protected]> wrote: > On Sun, Jul 20, 2014 at 7:34 PM, kilon alios <[email protected]> > wrote: > > With the help of Damien I was successful in creating a parser for pharo > to > > python syntax. Using pharo messages you can now construct automagically > > python strings and pass it to blender . This way you no longer need to > type > > in python syntax to do python stuff. So a big thanks to Damien. Note this > > method of course is slower because of parsing and heavy usage of regex > > string matching. > > > are you sure you need to pass 'nil' everywhere? In > #doesNotUnderstand:, you could check for the number of arguments and > generate something appropriate based on that. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >
