Thanks, Oliver and Wayne, for the replies. Keep us posted with all progress related to this.
Thanks, Diego On Fri, Jul 14, 2017 at 2:45 PM, Wayne Stambaugh <[email protected]> wrote: > On 7/14/2017 9:31 AM, Oliver Walters wrote: > > Hi Diego, > > > > > > > > Thinking of naming, should we use "kicad-packages3d" to keep the > > same format (kicad-symbols)? > > > > > > That's not a bad idea, I was considering this myself. It would make > > sense to rename this before a v5 release > > > > On a separate note, how does this work with the future symbols > > (.sweet)? Would that happen on v5 as well? Would that be a different > > repo? > > > > > > I'm not sure on the plan for .sweet in v5, I thought it was just the > > symbol-table and .sweet was v6, which means that the reorganization will > > be separate from the transfer to using .sweet libraries. I imagine there > > will need to be some scripts written to convert all the symbols. > > Sweet will not be completed for v5. Only the symbol library table will > be implemented. The new symbol library file (sweet) and schematic file > formats are expected to be part of the v6 release. > > > > > You say footprint libraries will remain as they are. Does that > > mean no unified repo? > > > > > > For now, at least. I want to merge them into a single kicad-footprints > > repo but this will require a lot of work because we have to maintain > > support for users who use the GitHub plugin to access repositories > > individually. I have yet to develop a clear plan to address this. One > > thing at a time :) > > > > Thanks! > > > > On Fri, Jul 14, 2017 at 11:24 PM, Diego Herranz > > <[email protected] <mailto:[email protected]>> > > wrote: > > > > Hi, Oliver. > > > > When I started using KiCad I got confused with the repos for > > symbols, footprints and 3D models. I think it's getting better and > > this will make it easier. > > > > Thinking of naming, should we use "kicad-packages3d" to keep the > > same format (kicad-symbols)? > > > > On a separate note, how does this work with the future symbols > > (.sweet)? Would that happen on v5 as well? Would that be a different > > repo? Or kicad-symbols would get updated to hold .sweet files > instead? > > You say footprint libraries will remain as they are. Does that mean > > no unified repo? > > > > Thanks! > > > > On Fri, Jul 14, 2017 at 2:18 AM, Oliver Walters > > <[email protected] > > <mailto:[email protected]>> wrote: > > > > To the package maintainers: > > > > There has been a lot of movement of late by the library team, > > with a view to improve (vastly) the quality of the symbol > libraries. > > > > The major change is our plan to reorganize the symbol libraries > > to bring some consistency - currently they are scattered and > > there is no real rhyme or reason to library convention. > > > > Reference - https://github.com/KiCad/kicad-library/issues/1402 > > <https://github.com/KiCad/kicad-library/issues/1402> > > > > This is a big change - so much so that I would like to retain a > > separation between the current symbol libraries (for legacy > > compatibility). My suggestion is to enact the new symbols in a > > new repository: > > > > <http://goog_1316844941> > > https://github.com/kicad/kicad-symbols > > <https://github.com/kicad/kicad-symbols> > > > > We currently have a separate discussion underway as to how we > > manage migration to the new repository (or whether we simply > > make a block change to the current one) > > - https://github.com/KiCad/kicad-library/issues/1415 > > <https://github.com/KiCad/kicad-library/issues/1415> > > > > A further very important note is that there is a new repository > > for 3d models, which is of far higher quality > > - https://github.com/kicad/packages3d > > <https://github.com/kicad/packages3d> > > > > This repository should supersede the 3d models currently located > > in the kicad-library repository. This also brings a functional > > separation between the symbol libraries and the 3d library, > > which is fantastic. > > > > > > My goal for release concurrent with KiCad v5 is thus: > > > > a) Mark kicad-library as legacy and don't package with v5 > > b) Package kicad-symbols as the symbol libraries > > c) Package packages3d as the 3D model libraries > > > > I'm not 100% on top of how the packaging takes place so if there > > are any good reasons that this should not take place as I have > > laid out above, please let me know now. > > > > The footprint libraries will remain as they are for v5. I have > > some ideas there but they require a lot more work - this is the > > first step towards the KiCad Library Management Manifesto (evil > > laugh). > > > > Regards, > > Oliver > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~kicad-developers > > <https://launchpad.net/~kicad-developers> > > Post to : [email protected] > > <mailto:[email protected]> > > Unsubscribe : https://launchpad.net/~kicad-developers > > <https://launchpad.net/~kicad-developers> > > More help : https://help.launchpad.net/ListHelp > > <https://help.launchpad.net/ListHelp> > > > > > > > > > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~kicad-developers > > Post to : [email protected] > > Unsubscribe : https://launchpad.net/~kicad-developers > > More help : https://help.launchpad.net/ListHelp > > > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
