I was thinking of simply moving the actual files in the .pretty repositories, and keep them separate from the .kicad_mod files. They could then get retrieved only when the user asks for the board's 3D representation, and as such, not put an extra burden on the retrieval of the footprints.
On Mon, Sep 22, 2014 at 2:11 PM, Jean-Paul Louis <[email protected]> wrote: > Carl, > > I agree 100% with you. The 3D model of the package should be tied to the > shape library. > The only concern is the size of the 3D model file, and the fact that some > users will never use the 3D capability. > I have no idea on what mechanism will allow to include the 3D shape unless > the format used is text based, so it could be then part of the part itself. > I know IGES is text based, but I do not know what is the format of the > current files (wings?) > > Just my $0.02 > > Jean-Paul > AC9GH > > On Sep 22, 2014, at 2:03 PM, Carl Poirier <[email protected]> > wrote: > > > Hi folks, > > > > Is there any reason to have the 3d models in the kicad-library > repository? They are tied to footprints actuall > >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
