kicad-developers team mailing list archive

[Seth Hillbrand <seth@xxxxxxxxxxxxx>]

Hi Andrew-

First, my apologies for the lateness of this reply.  I've unfortunately
fallen a bit behind in my e-mails and yours was set aside to respond to but
I hadn't yet gotten around to it.

1. I haven't published the api for this yet.  The basic work is bringing
eeschema into the plugin architecture and getting both old and new API to
compile and work from the same codebase.  I'm not sure who moved the
eeschema api to v7 but it shouldn't have.

2. As you'll recall, I mentioned that the plugin manager did need to follow
our basic goals pretty closely.  If your development work has done that,
then we may be able to incorporate some of your work into the release.  If
you send me a link to the branch where you are working on it, we can look
together to see what can get merged into the manager.

-Seth

On Sat, Oct 17, 2020 at 9:47 AM Andrew Lutsenko <anlutsenko@xxxxxxxxx>
wrote:

> Hi all,
>
> There were a couple features mentioned in KiCon 2020 q&a session that are
> apparently planned to be in v6 but it was a surprise for me since I'm
> closely following these and even directly involved (or I thought I was) in
> one of them.
>
> I'd appreciate some info. I know Seth is working on these but I can't seem
> to reach him by email so I'm trying the broader mailing list.
>
> 1. The stable python API. Is there a spec for it? I didn't see a
> discussion for it on the mailing list. As an author of one of the popular
> plugins I'd like to start looking into it early and provide feedback if
> possible.
> Also I'm assuming this is about pcbnew api only, as eeschema api was
> pushed to 7.0 https://gitlab.com/kicad/code/kicad/-/issues/2077
>
> 2. Plugin manager. If you recall last year I started a design doc for my
> vision of this feature and I admittedly dropped the ball on it for a while
> and, well, 2020 happened. But I've been chipping away at it and got pretty
> far. I even have a gui mock up almost ready.
> Link to the doc can be provided to interested parties but I was asked to
> not share it broadly until it gets initial approval by the core team.
>
> Hearing that you are close to merging your own implementation means I
> shouldn't continue with my work? I'm assuming you are close because it is
> supposedly on ff-exception list.
> Is the documentation for your implementation available somewhere? Again,
> it was not mentioned on the mailing list so maybe I'm not subscribed to the
> right sources.
>
> Regards,
> Andrew Lutsenko
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>


-- 
[image: KiCad Services Corporation Logo]
Seth Hillbrand
*Lead Developer*
+1-530-302-5483‬ <+12126039372>
Davis, CA
www.kipro-pcb.com    info@xxxxxxxxxxxxx