Thank you Miles, I have just pushed your patch. I agree with Wayne, one
day we will need to revise the Python scripting interface.
Regards,
Orson
On 03/06/2018 10:02 AM, miles mccoo wrote:
> Thanks all for your replies.
>
> I like the plugin mechanism. It does some nice things for python folks.
The best solution I've seen so far is the one that OpenCV implemented.
It's well described at
https://docs.opencv.org/master/da/d49/tutorial_py_bindings_basics.html
On 10.03.2018 21:44, Vesa Solonen wrote:
> Jon Evans kirjoitti 10/03/18 klo 15:57:
>
>> I'm interested in helping brainstorm this
Jon Evans kirjoitti 10/03/18 klo 15:57:
> I'm interested in helping brainstorm this more at some point; Python/C++
> interaction is something I'd like to learn more about how to do "right"
> both for KiCad and for some personal projects.
Depending what you consider "right", it may be well worth
I have never worked on Blender but just poked around the source a bit.
They write custom modules in CPython rather than using a wrapper like SWIG.
To expose internal data, they have a Python wrapper over a C data access
API.
The C API seems to have portions that are auto-generated by the build,
thank you all.
Yes, looking at other projects, blender in particular, would be wise. my
perception is they have a really nice scripting capability. You can do
anything there in scripting including commands that are indistinguishable
from the others.
I don't suppose anyone knows a blender
As a short term fix, I'll allow this patch to prevent the segfaults.
However, I do not want to continue to allowing these types of ad hoc
fixes. We should take Dick's suggestion and look at what other projects
are doing. We cannot be the only project wrestling with this issue.
On 3/8/2018 3:59
In my opinion #3 is acceptable. It does not require any extra changes in
the existing scripts and it fixes the problem until we come up with a
better scripting interface. If nobody has objections, I am going to
commit the patch.
Regards,
Orson
On 03/06/2018 10:02 AM, miles mccoo wrote:
> Thanks
Over many years I have adopted the habit of using an extended brainstorming
phase at the front end of any problem solving exercise.But for this to
succeed in a team environment it requires that everyone knows about the
brainstorming process, how it works and its various phases.It
Hi Miles,
I wasn’t around for the first discussion on the topic, but one of the reasons
(1) doesn’t work terribly well is that it’s not enough to know what changed;
one also has to know how to group the changes into individual undo/redo steps.
It sounds like the plugin infrastructure
Thanks all for your replies.
I like the plugin mechanism. It does some nice things for python folks.
Refresh, undo, garbage collection (I think). I want to see it succeed.
>From reading Orson's mail, I think I wasn't entirely clear, so let me try
to fix that first.
The plugin mechanism tries
LOL, I just replied to Miles. Thanks Orson for helping out!
On 3/2/2018 8:36 AM, Maciej Sumiński wrote:
> Hi Miles,
>
> I suppose the silence in the thread indicates there are not many
> developers knowing the Python scripting interface inside out. Since you
> are both studying the scripting
Miles,
I wish I had a answer for your but you are probably on your own here
unless the developer who implemented this steps in and helps. I don't
have the time to figure it out right now. Maybe someone else can help
you or maybe you could become the resident python expert and maintain
this. ;)
Hi Miles,
I suppose the silence in the thread indicates there are not many
developers knowing the Python scripting interface inside out. Since you
are both studying the scripting interface and developing own scripts, it
is quite possible you are the most competent person to give us an advice
on
13 matches
Mail list logo
