It seems that users are looking forward to the feature:
http://groups.yahoo.com/neo/groups/kicad-users/conversations/messages/16647
Regards,
Orson
On 12/01/2013 06:59 PM, Martin Janitschke wrote:
Heyho,
I've created the blueprint [0] we've started to discuss in the Next
Steps thread. Comments
Trying to use my debian build scrip (that used to work) and it fails with:
-- Build files have been written to: /usr/src/kicad-0.0.20131206/build/kicad-doc
mkdir -p /usr/src/kicad-0.0.20131206/build/kicad-library
cd /usr/src/kicad-0.0.20131206/build/kicad-library cmake ../../kicad-library
Hi Karl,
The libraries have moved to Github, here https://github.com/KiCad. The
old repo is still available, but it has been moved and renamed to
library-read-onlyhttps://code.launchpad.net/~dickelbeck/kicad/library-read-only.
Its use is discouraged, as it will eventually be removed.
With the
I have just committed a small change to the testing branch (r4529) to
the Pcbnew footprint viewer that will allow the main toolbar to be
dockable. I would like some feedback about how well saving and loading
the window state between session works on various platforms before I
start to do this to
I'd like to propose a new format for components libraries. The summary
of the proposal is as follows:
* XML is used as the serialization format
* one directory per library
* one file per component
* boost::property_tree is used as internal, abstract data format. This
allows translating to/from
I've already got a reply off-list that equivalent functionality is
already developed (I couldn't find any discussions on the list until now
unfortunately). It thus makes sense to scrap the proposal. Perhaps I can
help whoever is working on the new library file format?
Regards,
Povilas
6 matches
Mail list logo
