kicad-developers team mailing list archive

[Oliver Walters <oliver.henry.walters@xxxxxxxxx>]

Wayne,

You're probably right that there's no good way to decide which libraries
are the "default" ones. Maybe this is the best entry-level approach.

I think that a background library loader will solve a lot of the "freeze"
problems, but I imagine that is a lot of work.

On Fri, Nov 10, 2017 at 11:17 PM, Wayne Stambaugh <stambaughw@xxxxxxxxx>
wrote:

> Oliver,
>
> Including all of the libraries has been requested many times in the
> past.  Personally, I don't work that way but it seems to be the
> preference of a large percentage of users.  My guess is new users will
> prefer to have access to all libraries initially and start removing them
> when they get tired of the the overhead involved in using them.  I
> wouldn't be opposed to removing some of them but I doubt you will get a
> consensus on this issue.
>
> Cheers,
>
> Wayne
>
> On 11/9/2017 10:38 PM, Oliver Walters wrote:
> > Wayne,
> >
> > That's great news, and a welcome addition.
> >
> > Regarding the decision to include all the libraries by default - is this
> > a sensible solution? No project requires all libraries to be added, and
> > some of the libraries are particularly large. Is it really that
> > difficult for new users to understand that libraries are there to be
> > added and removed at will? Personally if I found all libraries loaded by
> > default I would unload most of them straight away...
> >
> > Perhaps I am not aware of the justification for this approach.
> >
> > Cheers,
> >
> > Oliver
> >
> > On Fri, Nov 10, 2017 at 1:35 PM, Wayne Stambaugh <stambaughw@xxxxxxxxx
> > <mailto:stambaughw@xxxxxxxxx>> wrote:
> >
> >     I finally got the symbol library table changes merged into the
> >     development branch of KiCad so be prepared for some pretty
> significant
> >     changes in the way symbol libraries are handled both from a user and
> a
> >     developer perspective.  Also be prepared for a massive amount of
> >     complaining about the change.  I wrote a blog post for the KiCad
> >     website[1] with all of the pertinent information you need to know
> before
> >     you remap your schematic symbols.  If users have any questions,
> please
> >     point them to blog post.  One thing I didn't mention in the blog post
> >     (although I may add it) is the component (now symbol) chooser dialog
> >     took another performance hit.  The default global symbol library
> table
> >     contains all of the symbol libraries of which there are over 90 so
> the
> >     symbol library load time shot up significantly when using the
> chooser.
> >     The Eeschema load time actually go better since like the footprint
> >     library table, symbol libraries are now loaded on demand so only the
> >     libraries that contain symbols in the schematic get loaded.  The
> rest of
> >     them get loaded as required.  If you find any issues please file a
> bug
> >     report and include a copy of the project files and symbol libraries
> (if
> >     possible) prior to the remapping that are causing the issue so I can
> fix
> >     them.
> >
> >     This should be the last major change except for the new symbol
> library
> >     manager before the feature freeze of the stable 5 version.  Thank you
> >     for your patience during this transition and enjoy.
> >
> >     Cheers,
> >
> >     Wayne
> >
> >     [1]: http://kicad-pcb.org/post/symbol-lib-table/
> >     <http://kicad-pcb.org/post/symbol-lib-table/>
> >
> >     _______________________________________________
> >     Mailing list: https://launchpad.net/~kicad-developers
> >     <https://launchpad.net/~kicad-developers>
> >     Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> >     <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> >     Unsubscribe : https://launchpad.net/~kicad-developers
> >     <https://launchpad.net/~kicad-developers>
> >     More help   : https://help.launchpad.net/ListHelp
> >     <https://help.launchpad.net/ListHelp>
> >
> >
>
>