kicad-developers team mailing list archive

["Mateusz" <komorkiewicz@...>]

It is hard for me to follow the discussion as we discuss too many problems at one time!

Vesa, I dare to propose a road map on libraries issues (based on our previous posts), what you think about this:

-------------------------------------
Libraries RoadMap
-------------------------------------
1. Tagging + tag searching
2. Files & components naming policy
3. Creation of GUI tool allowing libraries reordering + adding tags
4. Reordering libraries
5. Official components guidelines + license system
6. Dynamic styles
7. Fixing existing KiCad core libraries to meet the guidelines & styles
8. Web based library system
-------------------------------------
-------------------------------------

This list is simpler for my engineering mind;)

Lets focus on one point before we start discussing the next one ...

--- In kicad-devel@xxxxxxxxxxxxxxx, Wayne Stambaugh <stambaughw@...> wrote:
>
> SuperLou23 wrote:
> 
> << snipped >>
> 
> > Unfortunately, from a little digging, I think it would take a pretty big rewrite of the component file spec and other tools to allow tagging in there without it being a hack. I do think (from my own experience) however that the old method of browsing folders for components should have died longago. Filtering by tags and name in real time would make my life much easier (especially as the company parts db continues geting larger). I think there's a reason why autocomplete is very popular nowadays.
> 
> Tags are called key words in the component library object. There is
> already some simplified wild card searching built into the component
> library class. Adding regular expression searching is on my short list
> and should be fairly simple. It would allow for much more sophisticated
> search capability compared to the current solution. No rewriting of the
> library file structure is necessary. I have begun putting code in place
> to merge the separate library and document file implementation that we
> currently have. I still have some work to before that takes place but
> I'm sneaking up on it. Take a look at class_library.h and
> class_library.cpp in the eeschema directory of the Kicad source to see
> how key words figure into the library component object search.
> 
> Wayne
> 
> > 
> > Just my 2 cents.
> > 
> > 
> >>> Don't you think it should be fixed by somebody?
> >> That's what I'm making noise of :) Graphical tools for library
> >> reordering would be very nice, btw... I haven't yet decided how to do
> >> the task, but at least the task is clear.
> >>
> >> -Vesa
> >>
>