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
wrote:
> On 7/14/2017 9:31 AM, Oliver Walters wrote:
> > Hi Diego,
> >
> >
> >
> > Thinking of naming, should we use "kicad-packages3d"
Hi,
the original box is repaired, and the rented server is being shut down
soon, so I'm moving the Windows autobuilder again. Nightly build might
be a bit late today.
Simon
signature.asc
Description: OpenPGP digital signature
___
Mailing list: htt
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
>
>
This might be a good idea but there's no point until the .sweet format is
provided. The current format doesn't allow us to add custom fields that
have different valuess per alias.
On 14 Jul 2017 23:36, "Simon Richter" wrote:
> Hi,
>
> On 14.07.2017 03:18, Oliver Walters wrote:
>
> > The major ch
Hi,
On 14.07.2017 03:18, Oliver Walters wrote:
> 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.
Would it make sense to extend the format with extra data field
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)?
>
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 wo
7 matches
Mail list logo
