kicad-developers team mailing list archive

[Tomasz Wlostowski <tomasz.wlostowski@xxxxxxx>]

On 09/19/2013 04:53 PM, Miguel Angel wrote:
> 2013/9/19 Tomasz Wlostowski <tomasz.wlostowski@xxxxxxx
>
> I don't agree on this, my intention is to make them totally un-coupled
> to the UI itself.
>
> *hotkey:*
>
> The simplest hotkey plugin only needs to provide a function to tell
> which default hotkey does he want to hook on, and some kind of identifier.
>
> Then another function to receive the hotkey event... with will check the
> current context (selected elements, etc..) and act as programmed by the
> plugin designer.
>
> *toolbar:*
> *context menu plugin:*
> (...)
> I see no coupling to the wx, ... the C++ implementation can take care of
> how that's done over the UI.
Miguel,

Thanks for the explanation. Now I understand your idea and I fully agree :)

> I'm not sure if that was your concern.
>
>     My 5 cents for the plugin type list:
>     - S3D_MODEL_PLUGIN for loading VRML/STEP/IGES,
>
>
> I like it :)
> you could "import freecad" and then do whatever you want...
>
>     - APP_PLUGIN: an embeddable instance of a kicad application. In far
>     future, it may become possible to put apps in tabs, embed them in a
>     common shell application, etc.
>
>
> I can't imagine the interface of that yet. :)
Me neither, for the moment, but it looks dangerously close to OLE/COM :)

Tom