The schematic editor is less stable in terms of internals and there are
some important changes happening with regards to sheet storage. I had not
started on the schematic API because we should not release any API until we
can consider it stable to support, and it is harder to chase a moving
target.

It would be fine if you wanted to work on it but the caveat is that I don't
think it should be merged if any of the parts that you expose are
potentially going to change in incompatible ways. So, I suggest starting
small (for example, creating/updating any object types other than symbols).
Please tag me for review of any proposed protobuf changes.

There is no documentation other than what is already at dev-docs.kicad.org
so please reach out if you are unsure about something.

Thanks,
Jon

On Mon, May 12, 2025, 03:45 Anthony Park <[email protected]> wrote:

> Thanks for your reply. I'll check the source code first and post any ideas
> I have.
>
> 2025년 5월 12일 월요일 오후 4시 11분 36초 UTC+9에 [email protected]님이 작성:
>
>> I'm also working on the IPC API for placing design blocks and symbols,
>> any ideas are welcome
>>
>> On Mon, May 12, 2025 at 3:07 PM Ethan Chien <[email protected]> wrote:
>>
>>> You can refer to the pro-api-sdk of jlceda:
>>>
>>> https://www.npmjs.com/package/@jlceda/pro-api-types
>>>
>>> https://gitee.com/jlceda/pro-api-sdk
>>>
>>>
>>>
>>> On Mon, May 12, 2025 at 1:38 PM 박범석 <[email protected]> wrote:
>>>
>>>> Hi, all
>>>>
>>>> I recently joined the KiCad developer forum to work on IPC API
>>>> development. Before writing any code, I'd like to check a few things about
>>>> the current progress.
>>>>
>>>>    1. As mentioned in this post [
>>>>    https://gitlab.com/kicad/code/kicad/-/issues/2077#note_2265266555],
>>>>    I understand the goal is to replace the functionality currently 
>>>> provided by
>>>>    SWIG bindings with IPC API. I know work is progressing on the pcbnew 
>>>> API,
>>>>    but is there anyone currently working on the eeschema API, or are there 
>>>> any
>>>>    ongoing efforts in this area?
>>>>    2. If not, I'm thinking I'll need to refer to the api_handler in
>>>>    kicad_source_code/eeschema and create proto files along with 
>>>> schematic.py,
>>>>    schematic_types.py, etc. in kipy. However, with recent changes to 
>>>> eeschema [
>>>>    
>>>> https://gitlab.com/kicad/code/kicad/-/commit/718bf408070198012b1a95ddfe2c84d2f9fe6b78],
>>>>    it seems difficult to proceed without knowing the plan for future 
>>>> eeschema
>>>>    functionality. What's the roadmap for eeschema changes? If there's any
>>>>    documentation I should refer to, please let me know.
>>>>
>>>> Thanks in advance for your help!
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "KiCad Developers" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> To view this discussion visit
>>>> https://groups.google.com/a/kicad.org/d/msgid/devlist/6b3068ac-7d4a-4da0-b00e-83154b1dde9fn%40kicad.org
>>>> <https://groups.google.com/a/kicad.org/d/msgid/devlist/6b3068ac-7d4a-4da0-b00e-83154b1dde9fn%40kicad.org?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> --
> You received this message because you are subscribed to the Google Groups
> "KiCad Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion visit
> https://groups.google.com/a/kicad.org/d/msgid/devlist/8d745d44-a88c-48df-9f8c-624e5f94e1b0n%40kicad.org
> <https://groups.google.com/a/kicad.org/d/msgid/devlist/8d745d44-a88c-48df-9f8c-624e5f94e1b0n%40kicad.org?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"KiCad Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/a/kicad.org/d/msgid/devlist/CA%2BqGbCABj8dszpm%3DMcHqBdY_AD6qa_kx%2B5oeNWaLDZQHe6rT4g%40mail.gmail.com.

Reply via email to