Posted by emanuel on Jan 31, 2025; 10:32pm
URL: https://forum.librecad.org/Incorrect-pen-results-from-the-entitycontainer-tp5726283p5726288.html

Yes, exactly, that's how I imagine the implementation in the end.

At the moment everything is still in the test development stage, everything is very encapsulated and very redundant (only a rough framework).

I wrote the Lisp interpreter before, just for fun. It was a pure command line interpreter.

I first tried bit by bit to see if I could integrate it into LibreCAD. (Especially whether it would work with the DCL gui, because the smart Lisp Type classes destroy themselves immediately after use and only appear as constants.)

The attempts to port the entire object model to Python using swig make no sense at all for script applications, because it is far too complex and can quickly lead to situations that cause a crash. So I tried to implement what Lisp does in Python in the same way. I will only use this kind of code for LibrePython. The rest will be thrown out of swig.

I already use some of the same in Lisp and Python. But it should all be better centralized in a scripting API.

My main problem at the moment is that the whole thing is so much work.

The object model is still very complex for me and I always try to incorporate as little as possible into the LibreCAD-API source so that the github doesn't break again with the next master update.

A scripting API is essential if the whole thing is to work well.

Then later on, things like:
* shared using LC-API/Plugin/Lisp/Python
* Plugin/Lisp/Python reactors/callbacks to functions like in VisualLisp.
* Outsourcing and loading the VisualLisp functions in shared plugin libs.
* Centralized command alias management...
* Centralized menu management...

You can't do this alone.

I'm grateful for any developer help and especially for tips like the one with the pen.

At the moment I have assigned both entity-name (DXF -1), parent-softid name (DXF 330), and the entity-id (DXF 5) group codes to the LC entity id.
I don't know how to get the correct entity-name (DXF -1) parent-softid name (DXF 330).