yes the one I am considering as strong candidate is
(BPYObjects at: 'Cube' ) location : #( 0 0 0 )
I would try to simplify bpy ( Blender Python API) and make it a lot more pharo friendly.��
However plain python string will be kept as well, so you can copy paste existing python code.��
One thing to note here is that Blender python addons are a huge deal. Python addons are actually full blown python apps. Blender python is basically a regular cpython 3 which is by far the most popular python implementation , meaning not only that you can use blender api object but any python library you can find. As a pharo developer you also can tap into this power via Ephestos.��
something that I forgot to mention in the video, in the github repo there is a rawcode.py. This is a strip down version of the Blender code that will separate to its own project that I am naming "Atlas".��
The goal of Atlas, is to create a two way communication socket bridge between cpython (most popular python implementation) and pharo. Very similar to Ephestos but you will no longer need Blender. That means that pharo coders will be able to use python libraries from inside pharo and even mix python with pharo code. So you could make part of your application in python and part in pharo and still function as a single application.��
If I find the time I would like to expand Atlas to other languages too, so that pharo can take advantage of any library written in any language without the trouble of FFIs. But most likely I will stick to python and let others do the work.
But even with just python as you imagine python is extremely popular and quite friendly with the pharo way of thinking. Meaning that in python its all about live objects too. Pharo will be able to tap into thousands of powerful python libraries.�����
I reserve some doubts to the amount of problems I will have to face to accomplish this and I am no way claiming it wont be a long process but so far through these very first steps the idea seems to go well in practice.