kicad-developers team mailing list archive

[LordBlick <lordblick@xxxxxxxxx>]

In response to a message written on 28.09.2015, 22:37, from Wayne Stambaugh:
> On 9/28/2015 2:56 PM, LordBlick wrote:
> > In response to a message written on 28.09.2015, 20:31, from Wayne
> > Stambaugh:
> > > Maybe we should put the python scripts in share/kicad/scripting/python
> > +1
> > > > > > ${KICAD_PATH}/scripting/plugins ${HOME}/.kicad_plugins
> > > > > > ${HOME}/.kicad/scripting/plugins
> > Also with minimum, add ${HOME}/.local/share/kicad/scripting/python here.
> This would be something the user would have to do.  Installer packages will
> always install in the preferred install path where all users have access.
> Maybe one of the scripting devs can look at the kicad python scripting code
> and add the user path to the python paths.  Of course you could always
> configure python to look in your user path(s) as well.
Those paths are for per user footprint generator plugins(proudly named wizard).
Nobody bothered. User can remove, add, modify(usually for develop) without
superuser access and recreating system package. Unix way…
IMHO calmly these plugins(pcbnew/scripting/plugins) can be transferred to a
separate repository, eg. on Github.
In future there would be need to other kind of plugins in pcbnew, in addition to
generate footprints - to modifying edited boards, so it may be necessary to
divide into subdirectories.
In the current situation Python scripts are most effective for external
applications, and not inside the pcbnew. PyCrust is all rather just for decoration.
--
Best Regards,
LordBlick