date:20171106

I think we discussed this many times and it all came down to "someone
needs to implement it".
If I'm not imagining things the consensus back then was that the units
should be the user's
design units, so if the user had Imperial measures it would remain
0,1-inch but if the user had
Metric measures then it would be mm. To avoid confusion, the GUI would
need to indicate the
units used. There was also some discussion about a Field Validator
which would take units
so people could simply specify the type of unit as they please and it
would magically be
converted to the design units.  However, regardless of what the GUI
does, the files must have
measurements in mm.

- Cirilo


On Mon, Nov 6, 2017 at 1:01 PM, Simon Wells  wrote:
> at some point changing the models to be mm rather than 0.1" or whatever it is 
> now needs to be seriously looked at
>
>
>> On 7/11/2017, at 01:59, Wayne Stambaugh  wrote:
>>
>> Be careful here.  If the 3d model offset is currently in some units
>> other than mm and you change this, all existing 3d model offsets will be
>> broken.
>>
>> On 11/6/2017 7:56 AM, Oliver Walters wrote:
>>> That's what I expected. It then appears that there is a bug in the 3D
>>> code with regard to model offset. I'm working on a related patch set
>>> that will fix this, I just wanted to be sure. Thanks Wayne
>>>
>>> On Mon, Nov 6, 2017 at 11:53 PM, Wayne Stambaugh >> > wrote:
>>>
>>>It should be mm like all of the other coordinates.
>>>
>>>On 11/6/2017 7:32 AM, Oliver Walters wrote:
 With regard to the 3D model offset paramater

 e.g.

 (at (xyz a b c))

 Are the units stored in the file inches or mm?

 Cheers,
 Oliver


 ___
 Mailing list: https://launchpad.net/~kicad-developers
>>>
 Post to : kicad-developers@lists.launchpad.net
>>>
 Unsubscribe : https://launchpad.net/~kicad-developers
>>>
 More help   : https://help.launchpad.net/ListHelp
>>>

>>>
>>>___
>>>Mailing list: https://launchpad.net/~kicad-developers
>>>
>>>Post to : kicad-developers@lists.launchpad.net
>>>
>>>Unsubscribe : https://launchpad.net/~kicad-developers
>>>
>>>More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] [PATCH] wxWidgets macOS 10.13 Patch

2017-11-06 Thread Adam Wolf

Hi folks,

Attached is a patch that adds a patch that helps wxWidgets build on
the latest macOS 10.13 High Sierra.

Additionally, when folks build wxWidgets, they'll need to set the
CPPFLAG of D__ASSERT_MACROS_DEFINE_VERSIONS_WITHOUT_UNDERSCORES=1.

I'm working on updating the packaging scripts so folks can use those
as a reference.

Adam Wolf


0001-Added-patch-for-wxwidgets-for-macOS-High-Sierra-10.1.patch
Description: Binary data
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Replace .wrl files with .step on export (fixes lp:1710796)

Nick,

Good point. I'll raise a small patch later on that looks for IGES if no
STEP is found

On Tue, Nov 7, 2017 at 10:41 AM, Nick Østergaard  wrote:

> What about iges files? Should't it try to export iges files if no step is
> found?
>
> 2017-11-07 0:32 GMT+01:00 Wayne Stambaugh :
>
>> Hey Orson,
>>
>> I've got it now.  Go ahead and commit it if you have it ready to go.  If
>> not, I will do it in the next day or so.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 11/6/2017 6:02 PM, Maciej Suminski wrote:
>> > Hi Wayne,
>> >
>> > I think it only affects the STEP exporter (kicad2step executable), which
>> > cannot handle WRL models at all. With the patch applied, the exporter
>> > looks for a model with the same file name, but .step extension. In case
>> > there one is found - it is during the STEP export. I believe there is
>> > only an extra feature, no functionality removed/broken.
>> >
>> > Regards,
>> > Orson
>> >
>> > On 11/06/2017 05:07 PM, Wayne Stambaugh wrote:
>> >> If I'm reading this patch correctly, exported wrl files will always
>> have
>> >> step file references in them even when they are found.  If that is the
>> >> case, then I am opposed to this change.  AFAIK, opening the wrl board
>> >> file will fail with the embedded step file links.  It would make more
>> >> sense to me that kicad2step would attempt to substitute the wrl file
>> >> links withe step files when converting wrl to step.
>> >>
>> >> On 11/4/2017 8:47 AM, Oliver Walters wrote:
>> >>> The attached patch implements the feature suggested here
>> >>> : https://bugs.launchpad.net/kicad/+bug/1710796
>> >>>
>> >>> Problem:
>> >>>
>> >>> .wrl files are specified as default but these don't export to MCAD.
>> >>>
>> >>> Solution:
>> >>>
>> >>> On STEP export, wrl files are replaced with their step counterparts
>> (if
>> >>> such models exist).
>> >>>
>> >>> This is essentially what Maurice's famous StepUP tool does.
>> >>>
>> >>> Turns out it was a pretty simple fix :)
>> >>>
>> >>> Regards,
>> >>> Oliver
>> >>>
>> >>>
>> >>> ___
>> >>> Mailing list: https://launchpad.net/~kicad-developers
>> >>> Post to : kicad-developers@lists.launchpad.net
>> >>> Unsubscribe : https://launchpad.net/~kicad-developers
>> >>> More help   : https://help.launchpad.net/ListHelp
>> >>>
>> >>
>> >> ___
>> >> Mailing list: https://launchpad.net/~kicad-developers
>> >> Post to : kicad-developers@lists.launchpad.net
>> >> Unsubscribe : https://launchpad.net/~kicad-developers
>> >> More help   : https://help.launchpad.net/ListHelp
>> >>
>> >
>> > ___
>> > Mailing list: https://launchpad.net/~kicad-developers
>> > Post to : kicad-developers@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~kicad-developers
>> > More help   : https://help.launchpad.net/ListHelp
>> >
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH 00/12] Minor cleanups and improvements

On 11/3/2017 9:08 AM, Maciej Sumiński wrote:
> On 11/03/2017 01:38 PM, Carsten Schoenert wrote:
>> Hello Marvin,
>>
>> Am 02.11.2017 um 21:58 schrieb Marvin Schmidt:
>>> Just a set of small code cleanups to fix a bunch of warnings
>>> and remove dead code.
>>> Other than that the 'build:' commits avoid/remove/fix the
>>> installation of certain files:
>>>  - it doesn't make much sense to install the INSTALL.txt
>>>  - *.bat scripts shouldn't be installed on UNIX systems
>>>  - use CMAKE_INSTALL_* consistently to install files in the
>>>correct places
>> wouldn't it make more sense to write the specific reason for the commits
>> *into* the specific commit?
>> This email with your explanation why you have done all that work will go
>> down under in the typical noise of the mailing list and nobody but you
>> will later know why the single commit was made.
> 
> I think the e-mail subject contains the first line of commit message
> that explains the changes and most likely is handled correctly by
> git-am. Personally, I prefer patches sent as attachments as I do not use
> a client that is compatible with git-am. I also wonder whether git-am
> chokes on the lines add by launchpad in every message.
> 
> Apart from that, I think the proposed changes are reasonable and could
> be merged.
> 
> Regards,
> Orson
> 

There is nothing earth shattering here so I'm OK with merging these
patches.  Are you going to take care of this Orson?

Cheers,

Wayne


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

STEP simply has no provision for entities required for photo-realistic
rendering.
Even VRML is somewhat limited in that respect but it's leagues ahead of STEP.

- Cirilo


On Mon, Nov 6, 2017 at 9:27 PM, David Novak  wrote:
> Please enlighten me. I've always thought of STEP as the best end game, but
> haven't had much time to investigate advantages and disadvantages. What
> prevents STEP models from looking just as good as VRML models?
>
> Best Regards,
> David
>
>
> On 11/6/2017 4:17 PM, Cirilo Bernardo wrote:
>
> I wouldn't worry about the STEP file having numerous small parts;
> this happens all the time anyway unless the model can be fused.
> I don't see us abandoning VRML. I wrote the new parser but never
> use VRML except when testing the VRML parser. However, many
> people out there like to have VRML to make shiny models to show
> people.  I suspect there are more users who want VRML rather
> than STEP and that the STEP models are used mostly by
> professional users and hobbyists who happen to have an MCAD
> package. VRML is also used by some professionals for brochures
> or web page images; there is no disputing that STEP models look
> terribly ugly.
>
> On Mon, Nov 6, 2017 at 4:17 PM, José Ignacio  wrote:
>
> The only thing i really have against this is that it would make a pretty
> messy step file because the component would be broken up in tiny parts.
> Wouldn't there be a space saving with just ditching wrl altogether? the next
> stable won't need them
>
> On Mon, Nov 6, 2017 at 9:53 AM, Kristoffer Ödmark
>  wrote:
>
> To be fair, as it stands now, even if it is "only" for the pin headers,
> this is close to half of the 3d library size as of now.
>
> The pin headers can now be of an arbitrary size as well. Someone can now
> create a 4x6 pin header for example, and the current footprints can be
> converted to this array system, thus reducing the size.
>
> Arbitrary pin headers are a step up anyway.
>
> This being said, I have not tested the patch yet, but even if it is "only"
> for pin headers, the idea is sound to me.
>
>
>
> On 11/06/2017 04:22 PM, easyw wrote:
>
> Hi Oliver,
>
> I'm sorry not to be on your side for this option...
>
> 1) for which kind of modules this array is applicable?
> I see only pin-headers straight and angled...
> for example box headers are not easily done unless you consider to manage
> by the code the box for each model
> 2) the problem related to the big 3D library dimension will not be
> covered unless for some little family that can be managed by this on the fly
> generator
>
> As I already suggested, the issue with the huge 3D github library can be
> managed in a different way:
> 1) give the kicad users only a basic 3D library (i.e. most used smd and
> th families)
> 2) give an option to pcbnew to automatically create a list of the missing
> models needed for a project and collecting only them through a wget
> process...
>
> This will give a very low downloading band need and will not increase the
> need of disk space for having all the 3D library locally, full of unwanted
> models.
>
> Here a conversation of this issue:
> https://github.com/KiCad/kicad-library/issues/1532#issuecomment-341707706
>
> my two-cents
> Maurice
>
> On 11/06/2017 3:01 PM, Oliver Walters wrote:
>
> To provide an option to reduce the size of the 3D model library, I have
> implemented an "array" feature for 3D models. A module (footprint) can
> reference a single model multiple times, with a dimensional offset between
> each copy.
>
> (Note - just the PinHeader models are currently over 1GB! This feature
> lets you use a single 3D model for all pin headers or similar repetitive
> footprints within a certain series).
>
> Features:
>
> 1. Specify repeat count and repeat step in x/y/z axes
> 2. Save / load implemented. (If no repeat option used, no extra output
> is generated - old files are not touched)
> 3. Render in 3D viewer
> 4. Render in raytracing viewer
> 5. Export to VRML (multiple references to single file)
> 6. Export to STEP
>
> Notes:
>
> a. An exported STEP file will now be (possibly) much smaller as it
> references a single small object multiple times
> b. There were a couple of bugs I found where model offset units were
> incorrectly translated between INCHES and MM
>
> A couple of screenshots:
>
> https://imgur.com/a/EOwPh
>
>
> Testing:
>
> Wayne verified that the file units for 3D model data are in mm - I
> *think* this means that there was previously a bug regarding 3D model
> offset, where the scaling factor in the file was interpreted as inches when
> exporting (e.g. to STEP)
>
> I believe I have fixed this bug - confirmation would be great.
>
> Cheers,
> Oliver
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   :

Re: [Kicad-developers] [PATCH] Replace .wrl files with .step on export (fixes lp:1710796)

Oliver,

I merged your patch with Orson's suggestion along with fixing the commit
message to include the launchpad bug number.  Thank you for your
contribution to KiCad.

Cheers,

Wayne


On 11/4/2017 8:47 AM, Oliver Walters wrote:
> The attached patch implements the feature suggested here
> : https://bugs.launchpad.net/kicad/+bug/1710796
> 
> Problem:
> 
> .wrl files are specified as default but these don't export to MCAD. 
> 
> Solution:
> 
> On STEP export, wrl files are replaced with their step counterparts (if
> such models exist).
> 
> This is essentially what Maurice's famous StepUP tool does.
> 
> Turns out it was a pretty simple fix :)
> 
> Regards,
> Oliver
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Draw junctions last

2017-11-06 Thread Nick Østergaard

Ohh, I have never seen that. I guess this is because I always use the
default colors for wires which is the same green as the junction dot. Thank
you for the clarificaiton :)

2017-11-06 19:01 GMT+01:00 Seth Hillbrand :

> Hi Nick-
>
> Attached are two images, showing the issue and the resolution.  The
> attached schematic should also show it on your machine.  Note that this is
> captured in Eldar's bug report as well.
>
> -Seth
>
> On Mon, Nov 6, 2017 at 4:37 AM, Nick Østergaard  wrote:
>
>> What does the issue look like visually? Do you have a demo file to verify
>> this patch? This is nice to know if someone reports this issue in stable.
>>
>> 2017-11-03 21:08 GMT+01:00 Kevin Cozens :
>>
>>> On 2017-11-03 02:00 PM, Seth Hillbrand wrote:
>>>
 â€‹Kevin made a â€‹request to have junctions draw last on schematics to
 avoid a visual negative.

 This patch provides that functionality.

>>>
>>> tyvm, Seth. I applied your patch to the latest code from git master and
>>> it worked.
>>>
>>> --
>>> Cheers!
>>>
>>> Kevin.
>>>
>>> http://www.ve3syb.ca/   |"Nerds make the shiny things that
>>> distract
>>> Owner of Elecraft K2 #2172  | the mouth-breathers, and that's why
>>> we're
>>> | powerful!"
>>> #include  | --Chris Hardwick
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Replace .wrl files with .step on export (fixes lp:1710796)

2017-11-06 Thread Nick Østergaard

What about iges files? Should't it try to export iges files if no step is
found?

2017-11-07 0:32 GMT+01:00 Wayne Stambaugh :

> Hey Orson,
>
> I've got it now.  Go ahead and commit it if you have it ready to go.  If
> not, I will do it in the next day or so.
>
> Cheers,
>
> Wayne
>
> On 11/6/2017 6:02 PM, Maciej Suminski wrote:
> > Hi Wayne,
> >
> > I think it only affects the STEP exporter (kicad2step executable), which
> > cannot handle WRL models at all. With the patch applied, the exporter
> > looks for a model with the same file name, but .step extension. In case
> > there one is found - it is during the STEP export. I believe there is
> > only an extra feature, no functionality removed/broken.
> >
> > Regards,
> > Orson
> >
> > On 11/06/2017 05:07 PM, Wayne Stambaugh wrote:
> >> If I'm reading this patch correctly, exported wrl files will always have
> >> step file references in them even when they are found.  If that is the
> >> case, then I am opposed to this change.  AFAIK, opening the wrl board
> >> file will fail with the embedded step file links.  It would make more
> >> sense to me that kicad2step would attempt to substitute the wrl file
> >> links withe step files when converting wrl to step.
> >>
> >> On 11/4/2017 8:47 AM, Oliver Walters wrote:
> >>> The attached patch implements the feature suggested here
> >>> : https://bugs.launchpad.net/kicad/+bug/1710796
> >>>
> >>> Problem:
> >>>
> >>> .wrl files are specified as default but these don't export to MCAD.
> >>>
> >>> Solution:
> >>>
> >>> On STEP export, wrl files are replaced with their step counterparts (if
> >>> such models exist).
> >>>
> >>> This is essentially what Maurice's famous StepUP tool does.
> >>>
> >>> Turns out it was a pretty simple fix :)
> >>>
> >>> Regards,
> >>> Oliver
> >>>
> >>>
> >>> ___
> >>> Mailing list: https://launchpad.net/~kicad-developers
> >>> Post to : kicad-developers@lists.launchpad.net
> >>> Unsubscribe : https://launchpad.net/~kicad-developers
> >>> More help   : https://help.launchpad.net/ListHelp
> >>>
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >>
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Replace .wrl files with .step on export (fixes lp:1710796)

Hey Orson,

I've got it now.  Go ahead and commit it if you have it ready to go.  If
not, I will do it in the next day or so.

Cheers,

Wayne

On 11/6/2017 6:02 PM, Maciej Suminski wrote:
> Hi Wayne,
> 
> I think it only affects the STEP exporter (kicad2step executable), which
> cannot handle WRL models at all. With the patch applied, the exporter
> looks for a model with the same file name, but .step extension. In case
> there one is found - it is during the STEP export. I believe there is
> only an extra feature, no functionality removed/broken.
> 
> Regards,
> Orson
> 
> On 11/06/2017 05:07 PM, Wayne Stambaugh wrote:
>> If I'm reading this patch correctly, exported wrl files will always have
>> step file references in them even when they are found.  If that is the
>> case, then I am opposed to this change.  AFAIK, opening the wrl board
>> file will fail with the embedded step file links.  It would make more
>> sense to me that kicad2step would attempt to substitute the wrl file
>> links withe step files when converting wrl to step.
>>
>> On 11/4/2017 8:47 AM, Oliver Walters wrote:
>>> The attached patch implements the feature suggested here
>>> : https://bugs.launchpad.net/kicad/+bug/1710796
>>>
>>> Problem:
>>>
>>> .wrl files are specified as default but these don't export to MCAD. 
>>>
>>> Solution:
>>>
>>> On STEP export, wrl files are replaced with their step counterparts (if
>>> such models exist).
>>>
>>> This is essentially what Maurice's famous StepUP tool does.
>>>
>>> Turns out it was a pretty simple fix :)
>>>
>>> Regards,
>>> Oliver
>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Replace .wrl files with .step on export (fixes lp:1710796)

Apparently I did not read the patch correctly.

On 11/6/2017 3:30 PM, Oliver Walters wrote:
> Wayne,
> 
> 
>  /It would make more//
> sense to me that kicad2step would attempt to substitute the wrl file
> links withe step files when converting wrl to step./
> 
> This is exactly what it does. I'm not sure what you mean with embedded
> step file references. 
> 
> On 7 Nov 2017 03:07, "Wayne Stambaugh"  > wrote:
> 
> If I'm reading this patch correctly, exported wrl files will always have
> step file references in them even when they are found.  If that is the
> case, then I am opposed to this change.  AFAIK, opening the wrl board
> file will fail with the embedded step file links.  It would make more
> sense to me that kicad2step would attempt to substitute the wrl file
> links withe step files when converting wrl to step.
> 
> On 11/4/2017 8:47 AM, Oliver Walters wrote:
> > The attached patch implements the feature suggested here
> > : https://bugs.launchpad.net/kicad/+bug/1710796
> 
> >
> > Problem:
> >
> > .wrl files are specified as default but these don't export to MCAD. 
> >
> > Solution:
> >
> > On STEP export, wrl files are replaced with their step
> counterparts (if
> > such models exist).
> >
> > This is essentially what Maurice's famous StepUP tool does.
> >
> > Turns out it was a pretty simple fix :)
> >
> > Regards,
> > Oliver
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> 
> > Post to     : kicad-developers@lists.launchpad.net
> 
> > Unsubscribe : https://launchpad.net/~kicad-developers
> 
> > More help   : https://help.launchpad.net/ListHelp
> 
> >
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> 
> Post to     : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> 
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models


Oliver,
if you create by script or code or manually an array of single STEP 
models, the resulting array could be not fine in geometric terms also if 
the single model is good...
Please have some deep insight to FreeCAD forum or even OCC forum to see 
how mechanical boolean operation can be insidious ...


So yes, you need to validate all your models if you want to build a 
single part or you will need to build an array of models instead of a 
single STEP models...
Both solutions are not suitable in my opinion and experience in 
mechanical cad.


Maurice

On 11/6/2017 11:54 PM, Oliver Walters wrote:
This patch does *not* generate any models on the fly. It provides the 
ability for users to re-use existing model data (which they are NOT 
forced to use by any means). In the example of pin headers or terminal 
blocks, where each unit is identical, there is no need to re-validate 
each model. It is simply another means of achieving a goal.


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Replace .wrl files with .step on export (fixes lp:1710796)

2017-11-06 Thread Maciej Suminski

Hi Wayne,

I think it only affects the STEP exporter (kicad2step executable), which
cannot handle WRL models at all. With the patch applied, the exporter
looks for a model with the same file name, but .step extension. In case
there one is found - it is during the STEP export. I believe there is
only an extra feature, no functionality removed/broken.

Regards,
Orson

On 11/06/2017 05:07 PM, Wayne Stambaugh wrote:
> If I'm reading this patch correctly, exported wrl files will always have
> step file references in them even when they are found.  If that is the
> case, then I am opposed to this change.  AFAIK, opening the wrl board
> file will fail with the embedded step file links.  It would make more
> sense to me that kicad2step would attempt to substitute the wrl file
> links withe step files when converting wrl to step.
> 
> On 11/4/2017 8:47 AM, Oliver Walters wrote:
>> The attached patch implements the feature suggested here
>> : https://bugs.launchpad.net/kicad/+bug/1710796
>>
>> Problem:
>>
>> .wrl files are specified as default but these don't export to MCAD. 
>>
>> Solution:
>>
>> On STEP export, wrl files are replaced with their step counterparts (if
>> such models exist).
>>
>> This is essentially what Maurice's famous StepUP tool does.
>>
>> Turns out it was a pretty simple fix :)
>>
>> Regards,
>> Oliver
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

Orson,

Yes a decompression plugin would be a good addition to the
"download-as-needed" that Maurice mentions above.

On Tue, Nov 7, 2017 at 9:54 AM, Maciej Suminski 
wrote:

> On 11/06/2017 11:43 PM, Oliver Walters wrote:
> > Orson,
> >
> > That's a good idea, and I am actively investigating that. Check out
> > https://kicad.github.io - currently only symbols and footprints are
> there
> > but models are on their way. The scripts that generate that data use a
> very
> > heavy 7z compression.
>
> Great, just by browsing the site I got the impression the idea is worth
> pursuing.
>
> > However, is this a reason to *not* add the array functionality provided
> in
> > this patch? I still think it is a useful feature.
>
> I do not have a strong opinion here. If it has not been developed yet, I
> would advise to implement a decompressing plugin (a wrapper around
> another plugin to make it universal?) as it helps for the general case,
> not only for models that can be divided into arrays.
>
> Looking at the patches, there is a lot of new code that may need to be
> maintained in the future in exchange for hard to estimate gain. On the
> other hand, it would be a pity to drop the code clean-up and bug fixes
> you mentioned.
>
> Cheers,
> Orson
>
> > On Tue, Nov 7, 2017 at 9:40 AM, Maciej Suminski  >
> > wrote:
> >
> >> Hi Oliver,
> >>
> >> What do you think about providing the models as compressed files? As any
> >> text format, one can expect quite high compression ratio. Perhaps that
> >> would be sufficient to solve the huge libraries problem.
> >>
> >> Cheers,
> >> Orson
> >>
> >> On 11/06/2017 03:01 PM, Oliver Walters wrote:
> >>> To provide an option to reduce the size of the 3D model library, I have
> >>> implemented an "array" feature for 3D models. A module (footprint) can
> >>> reference a single model multiple times, with a dimensional offset
> >> between
> >>> each copy.
> >>>
> >>> (Note - just the PinHeader models are currently over 1GB! This feature
> >> lets
> >>> you use a single 3D model for all pin headers or similar repetitive
> >>> footprints within a certain series).
> >>>
> >>> Features:
> >>>
> >>> 1. Specify repeat count and repeat step in x/y/z axes
> >>> 2. Save / load implemented. (If no repeat option used, no extra output
> is
> >>> generated - old files are not touched)
> >>> 3. Render in 3D viewer
> >>> 4. Render in raytracing viewer
> >>> 5. Export to VRML (multiple references to single file)
> >>> 6. Export to STEP
> >>>
> >>> Notes:
> >>>
> >>> a. An exported STEP file will now be (possibly) much smaller as it
> >>> references a single small object multiple times
> >>> b. There were a couple of bugs I found where model offset units were
> >>> incorrectly translated between INCHES and MM
> >>>
> >>> A couple of screenshots:
> >>>
> >>> https://imgur.com/a/EOwPh
> >>>
> >>>
> >>> Testing:
> >>>
> >>> Wayne verified that the file units for 3D model data are in mm - I
> >> *think*
> >>> this means that there was previously a bug regarding 3D model offset,
> >> where
> >>> the scaling factor in the file was interpreted as inches when exporting
> >>> (e.g. to STEP)
> >>>
> >>> I believe I have fixed this bug - confirmation would be great.
> >>>
> >>> Cheers,
> >>> Oliver
> >>>
> >>>
> >>>
> >>> ___
> >>> Mailing list: https://launchpad.net/~kicad-developers
> >>> Post to : kicad-developers@lists.launchpad.net
> >>> Unsubscribe : https://launchpad.net/~kicad-developers
> >>> More help   : https://help.launchpad.net/ListHelp
> >>>
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >>
> >
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

Maurice,

This patch does *not* generate any models on the fly. It provides the
ability for users to re-use existing model data (which they are NOT forced
to use by any means). In the example of pin headers or terminal blocks,
where each unit is identical, there is no need to re-validate each model.
It is simply another means of achieving a goal.

On Tue, Nov 7, 2017 at 9:52 AM, easyw  wrote:

> Oliver,
>
> just an other point against it IMO:
>
> If you develop a build on the fly 3D library, in case of update on OCE
> release, you would need to check and probably review all the models
> generated by your scripts...
> As I already pointed out on GitHub discussion, STEP are not just rendering
> models... they need to be done with a geometry check to guarantee a fine
> mechanical result.
>
> A static library is just as is... good a and reliable without any need to
> be re-checked or rebuilt once approved...
>
> Why just rework what is done till now and for which kind of advantage or
> optimization?
>
> Still my best option is to decide what to deploy with the Kicad installer
> and a dynamic downloader that will fetch and download only what is needed
> for the project.
>
>
> Maurice
>
>
> On 11/6/2017 11:34 PM, Oliver Walters wrote:
>
>> Seth, for the STEP export that would be a better idea, I can look into
>> how to implement that in the kicad2step tool.
>>
>> Wayne, if you are completely against this as a feature, then I shan't
>> spend any more time on it, but:
>>
>> 1. I think it is a useful feature to have even if it is not the "right"
>> way to solve the current 3D library issues. That was only one motivating
>> factor. I still think it is useful.
>> 2. In terms of "code clarity" - take a look at the patch set, I don't
>> think it will cause any issues for readability.
>> 3. There are some bug fixes and code cleanup that I have performed as
>> part of this patch set.
>> 4. If I can use the STEP format array_placement as Seth suggests, then
>> the internal representation of the exported STEP file will be improved
>>
>> Regarding STEP / WRL comparisons - That's a separate issue to what is
>> being discussed here. This patch works just as well for .wrl or .step
>> models.
>>
>>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

2017-11-06 Thread Maciej Suminski

On 11/06/2017 11:43 PM, Oliver Walters wrote:
> Orson,
> 
> That's a good idea, and I am actively investigating that. Check out
> https://kicad.github.io - currently only symbols and footprints are there
> but models are on their way. The scripts that generate that data use a very
> heavy 7z compression.

Great, just by browsing the site I got the impression the idea is worth
pursuing.

> However, is this a reason to *not* add the array functionality provided in
> this patch? I still think it is a useful feature.

I do not have a strong opinion here. If it has not been developed yet, I
would advise to implement a decompressing plugin (a wrapper around
another plugin to make it universal?) as it helps for the general case,
not only for models that can be divided into arrays.

Looking at the patches, there is a lot of new code that may need to be
maintained in the future in exchange for hard to estimate gain. On the
other hand, it would be a pity to drop the code clean-up and bug fixes
you mentioned.

Cheers,
Orson

> On Tue, Nov 7, 2017 at 9:40 AM, Maciej Suminski 
> wrote:
> 
>> Hi Oliver,
>>
>> What do you think about providing the models as compressed files? As any
>> text format, one can expect quite high compression ratio. Perhaps that
>> would be sufficient to solve the huge libraries problem.
>>
>> Cheers,
>> Orson
>>
>> On 11/06/2017 03:01 PM, Oliver Walters wrote:
>>> To provide an option to reduce the size of the 3D model library, I have
>>> implemented an "array" feature for 3D models. A module (footprint) can
>>> reference a single model multiple times, with a dimensional offset
>> between
>>> each copy.
>>>
>>> (Note - just the PinHeader models are currently over 1GB! This feature
>> lets
>>> you use a single 3D model for all pin headers or similar repetitive
>>> footprints within a certain series).
>>>
>>> Features:
>>>
>>> 1. Specify repeat count and repeat step in x/y/z axes
>>> 2. Save / load implemented. (If no repeat option used, no extra output is
>>> generated - old files are not touched)
>>> 3. Render in 3D viewer
>>> 4. Render in raytracing viewer
>>> 5. Export to VRML (multiple references to single file)
>>> 6. Export to STEP
>>>
>>> Notes:
>>>
>>> a. An exported STEP file will now be (possibly) much smaller as it
>>> references a single small object multiple times
>>> b. There were a couple of bugs I found where model offset units were
>>> incorrectly translated between INCHES and MM
>>>
>>> A couple of screenshots:
>>>
>>> https://imgur.com/a/EOwPh
>>>
>>>
>>> Testing:
>>>
>>> Wayne verified that the file units for 3D model data are in mm - I
>> *think*
>>> this means that there was previously a bug regarding 3D model offset,
>> where
>>> the scaling factor in the file was interpreted as inches when exporting
>>> (e.g. to STEP)
>>>
>>> I believe I have fixed this bug - confirmation would be great.
>>>
>>> Cheers,
>>> Oliver
>>>
>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models


Oliver,

just an other point against it IMO:

If you develop a build on the fly 3D library, in case of update on OCE 
release, you would need to check and probably review all the models 
generated by your scripts...
As I already pointed out on GitHub discussion, STEP are not just 
rendering models... they need to be done with a geometry check to 
guarantee a fine mechanical result.


A static library is just as is... good a and reliable without any need 
to be re-checked or rebuilt once approved...


Why just rework what is done till now and for which kind of advantage or 
optimization?


Still my best option is to decide what to deploy with the Kicad 
installer and a dynamic downloader that will fetch and download only 
what is needed for the project.



Maurice

On 11/6/2017 11:34 PM, Oliver Walters wrote:
Seth, for the STEP export that would be a better idea, I can look into 
how to implement that in the kicad2step tool.


Wayne, if you are completely against this as a feature, then I shan't 
spend any more time on it, but:


1. I think it is a useful feature to have even if it is not the "right" 
way to solve the current 3D library issues. That was only one motivating 
factor. I still think it is useful.
2. In terms of "code clarity" - take a look at the patch set, I don't 
think it will cause any issues for readability.
3. There are some bug fixes and code cleanup that I have performed as 
part of this patch set.
4. If I can use the STEP format array_placement as Seth suggests, then 
the internal representation of the exported STEP file will be improved


Regarding STEP / WRL comparisons - That's a separate issue to what is 
being discussed here. This patch works just as well for .wrl or .step 
models.




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

Maurice,

I really like the idea of downloading models on an as-needed basis. This
will be a lot of work to implement (but I think it could be done).

This patch is not intended to be the final solution for the libraries
issue. I would still support a move to download models as needed

On Tue, Nov 7, 2017 at 2:22 AM, easyw  wrote:

> Hi Oliver,
>
> I'm sorry not to be on your side for this option...
>
> 1) for which kind of modules this array is applicable?
> I see only pin-headers straight and angled...
> for example box headers are not easily done unless you consider to manage
> by the code the box for each model
> 2) the problem related to the big 3D library dimension will not be covered
> unless for some little family that can be managed by this on the fly
> generator
>
> As I already suggested, the issue with the huge 3D github library can be
> managed in a different way:
> 1) give the kicad users only a basic 3D library (i.e. most used smd and th
> families)
> 2) give an option to pcbnew to automatically create a list of the missing
> models needed for a project and collecting only them through a wget
> process...
>
> This will give a very low downloading band need and will not increase the
> need of disk space for having all the 3D library locally, full of unwanted
> models.
>
> Here a conversation of this issue:
> https://github.com/KiCad/kicad-library/issues/1532#issuecomment-341707706
>
> my two-cents
> Maurice
>
>
> On 11/06/2017 3:01 PM, Oliver Walters wrote:
>
>> To provide an option to reduce the size of the 3D model library, I have
>> implemented an "array" feature for 3D models. A module (footprint) can
>> reference a single model multiple times, with a dimensional offset between
>> each copy.
>>
>> (Note - just the PinHeader models are currently over 1GB! This feature
>> lets you use a single 3D model for all pin headers or similar repetitive
>> footprints within a certain series).
>>
>> Features:
>>
>> 1. Specify repeat count and repeat step in x/y/z axes
>> 2. Save / load implemented. (If no repeat option used, no extra output is
>> generated - old files are not touched)
>> 3. Render in 3D viewer
>> 4. Render in raytracing viewer
>> 5. Export to VRML (multiple references to single file)
>> 6. Export to STEP
>>
>> Notes:
>>
>> a. An exported STEP file will now be (possibly) much smaller as it
>> references a single small object multiple times
>> b. There were a couple of bugs I found where model offset units were
>> incorrectly translated between INCHES and MM
>>
>> A couple of screenshots:
>>
>> https://imgur.com/a/EOwPh
>>
>>
>> Testing:
>>
>> Wayne verified that the file units for 3D model data are in mm - I
>> *think* this means that there was previously a bug regarding 3D model
>> offset, where the scaling factor in the file was interpreted as inches when
>> exporting (e.g. to STEP)
>>
>> I believe I have fixed this bug - confirmation would be great.
>>
>> Cheers,
>> Oliver
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

Orson,

That's a good idea, and I am actively investigating that. Check out
https://kicad.github.io - currently only symbols and footprints are there
but models are on their way. The scripts that generate that data use a very
heavy 7z compression.

However, is this a reason to *not* add the array functionality provided in
this patch? I still think it is a useful feature.

On Tue, Nov 7, 2017 at 9:40 AM, Maciej Suminski 
wrote:

> Hi Oliver,
>
> What do you think about providing the models as compressed files? As any
> text format, one can expect quite high compression ratio. Perhaps that
> would be sufficient to solve the huge libraries problem.
>
> Cheers,
> Orson
>
> On 11/06/2017 03:01 PM, Oliver Walters wrote:
> > To provide an option to reduce the size of the 3D model library, I have
> > implemented an "array" feature for 3D models. A module (footprint) can
> > reference a single model multiple times, with a dimensional offset
> between
> > each copy.
> >
> > (Note - just the PinHeader models are currently over 1GB! This feature
> lets
> > you use a single 3D model for all pin headers or similar repetitive
> > footprints within a certain series).
> >
> > Features:
> >
> > 1. Specify repeat count and repeat step in x/y/z axes
> > 2. Save / load implemented. (If no repeat option used, no extra output is
> > generated - old files are not touched)
> > 3. Render in 3D viewer
> > 4. Render in raytracing viewer
> > 5. Export to VRML (multiple references to single file)
> > 6. Export to STEP
> >
> > Notes:
> >
> > a. An exported STEP file will now be (possibly) much smaller as it
> > references a single small object multiple times
> > b. There were a couple of bugs I found where model offset units were
> > incorrectly translated between INCHES and MM
> >
> > A couple of screenshots:
> >
> > https://imgur.com/a/EOwPh
> >
> >
> > Testing:
> >
> > Wayne verified that the file units for 3D model data are in mm - I
> *think*
> > this means that there was previously a bug regarding 3D model offset,
> where
> > the scaling factor in the file was interpreted as inches when exporting
> > (e.g. to STEP)
> >
> > I believe I have fixed this bug - confirmation would be great.
> >
> > Cheers,
> > Oliver
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Replace .wrl files with .step on export (fixes lp:1710796)

>
> I do like to use VRML models in the 3D viewer of pcbnew as I can use
> textures and materials with them so they look good when I take a screen
> shot for use on a web page. The CAD software I use can import many model
> file formats including VRML and STEP. It doesn't matter to me which type is
> used when it comes time for me to load the file up to do mechanical design.


It does matter because .wrl is not a valid MCAD format. This change is
*only* for the STEP exporter which requires MCAD models - wrl models are
currently ignored anyway.

This patch only adds functionality, it does not remove it.

On Tue, Nov 7, 2017 at 8:38 AM, Kevin Cozens  wrote:

> On 2017-11-06 03:30 PM, Oliver Walters wrote:
>
>> Wayne,
>>
>>
>> Â /It would make more//
>> sense to me that kicad2step would attempt to substitute the wrl file
>> links withe step files when converting wrl to step./
>>
>> This is exactly what it does. I'm not sure what you mean with embedded
>> step file references.Â
>>
>
> I have also been wondering about the mention of substituting WRL files
> with STEP files on export. I would want to stick with the model files I
> specified in pcbnew and not have them automatically(?) changed in to some
> other format.
>
> I do like to use VRML models in the 3D viewer of pcbnew as I can use
> textures and materials with them so they look good when I take a screen
> shot for use on a web page. The CAD software I use can import many model
> file formats including VRML and STEP. It doesn't matter to me which type is
> used when it comes time for me to load the file up to do mechanical design.
>
> --
> Cheers!
>
> Kevin.
>
> http://www.ve3syb.ca/   |"Nerds make the shiny things that
> distract
> Owner of Elecraft K2 #2172  | the mouth-breathers, and that's why we're
> | powerful!"
> #include  | --Chris Hardwick
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

2017-11-06 Thread Maciej Suminski

Hi Oliver,

What do you think about providing the models as compressed files? As any
text format, one can expect quite high compression ratio. Perhaps that
would be sufficient to solve the huge libraries problem.

Cheers,
Orson

On 11/06/2017 03:01 PM, Oliver Walters wrote:
> To provide an option to reduce the size of the 3D model library, I have
> implemented an "array" feature for 3D models. A module (footprint) can
> reference a single model multiple times, with a dimensional offset between
> each copy.
> 
> (Note - just the PinHeader models are currently over 1GB! This feature lets
> you use a single 3D model for all pin headers or similar repetitive
> footprints within a certain series).
> 
> Features:
> 
> 1. Specify repeat count and repeat step in x/y/z axes
> 2. Save / load implemented. (If no repeat option used, no extra output is
> generated - old files are not touched)
> 3. Render in 3D viewer
> 4. Render in raytracing viewer
> 5. Export to VRML (multiple references to single file)
> 6. Export to STEP
> 
> Notes:
> 
> a. An exported STEP file will now be (possibly) much smaller as it
> references a single small object multiple times
> b. There were a couple of bugs I found where model offset units were
> incorrectly translated between INCHES and MM
> 
> A couple of screenshots:
> 
> https://imgur.com/a/EOwPh
> 
> 
> Testing:
> 
> Wayne verified that the file units for 3D model data are in mm - I *think*
> this means that there was previously a bug regarding 3D model offset, where
> the scaling factor in the file was interpreted as inches when exporting
> (e.g. to STEP)
> 
> I believe I have fixed this bug - confirmation would be great.
> 
> Cheers,
> Oliver
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

Seth, for the STEP export that would be a better idea, I can look into how
to implement that in the kicad2step tool.

Wayne, if you are completely against this as a feature, then I shan't spend
any more time on it, but:

1. I think it is a useful feature to have even if it is not the "right" way
to solve the current 3D library issues. That was only one motivating
factor. I still think it is useful.
2. In terms of "code clarity" - take a look at the patch set, I don't think
it will cause any issues for readability.
3. There are some bug fixes and code cleanup that I have performed as part
of this patch set.
4. If I can use the STEP format array_placement as Seth suggests, then the
internal representation of the exported STEP file will be improved

Regarding STEP / WRL comparisons - That's a separate issue to what is being
discussed here. This patch works just as well for .wrl or .step models.

On Tue, Nov 7, 2017 at 8:22 AM, Seth Hillbrand 
wrote:

> I think it may be preferable to utilize the STEP file's inherent
> array_placement_group function to generate an array of the underlying
> structure.
>
> -S
>
> On Mon, Nov 6, 2017 at 1:01 PM, Kevin Cozens  wrote:
>
>> On 2017-11-06 09:01 AM, Oliver Walters wrote:
>>
>>> To provide an option to reduce the size of the 3D model library, I have
>>> implemented an "array" feature for 3D models. A module (footprint) can
>>> reference a single model multiple times, with a dimensional offset between
>>> each copy.
>>>
>>
>> Sounds interesting. This would be quite useful for IC packages (both
>> through hole and surface mount) in addition to male and female headers.
>>
>> And I forgot to add in my previous message it is also good for IC sockets.
>>
>>
>> --
>> Cheers!
>>
>> Kevin.
>>
>> http://www.ve3syb.ca/   |"Nerds make the shiny things that
>> distract
>> Owner of Elecraft K2 #2172  | the mouth-breathers, and that's why
>> we're
>> | powerful!"
>> #include  | --Chris Hardwick
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

2017-11-06 Thread Seth Hillbrand

I think it may be preferable to utilize the STEP file's inherent
array_placement_group function to generate an array of the underlying
structure.

-S

On Mon, Nov 6, 2017 at 1:01 PM, Kevin Cozens  wrote:

> On 2017-11-06 09:01 AM, Oliver Walters wrote:
>
>> To provide an option to reduce the size of the 3D model library, I have
>> implemented an "array" feature for 3D models. A module (footprint) can
>> reference a single model multiple times, with a dimensional offset between
>> each copy.
>>
>
> Sounds interesting. This would be quite useful for IC packages (both
> through hole and surface mount) in addition to male and female headers.
>
> And I forgot to add in my previous message it is also good for IC sockets.
>
>
> --
> Cheers!
>
> Kevin.
>
> http://www.ve3syb.ca/   |"Nerds make the shiny things that
> distract
> Owner of Elecraft K2 #2172  | the mouth-breathers, and that's why we're
> | powerful!"
> #include  | --Chris Hardwick
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

2017-11-06 Thread David Novak

Please enlighten me. I've always thought of STEP as the best end game, 
but haven't had much time to investigate advantages and disadvantages. 
What prevents STEP models from looking just as good as VRML models?


Best Regards,
David


On 11/6/2017 4:17 PM, Cirilo Bernardo wrote:

I wouldn't worry about the STEP file having numerous small parts;
this happens all the time anyway unless the model can be fused.
I don't see us abandoning VRML. I wrote the new parser but never
use VRML except when testing the VRML parser. However, many
people out there like to have VRML to make shiny models to show
people.  I suspect there are more users who want VRML rather
than STEP and that the STEP models are used mostly by
professional users and hobbyists who happen to have an MCAD
package. VRML is also used by some professionals for brochures
or web page images; there is no disputing that STEP models look
terribly ugly.

On Mon, Nov 6, 2017 at 4:17 PM, José Ignacio  wrote:

The only thing i really have against this is that it would make a pretty
messy step file because the component would be broken up in tiny parts.
Wouldn't there be a space saving with just ditching wrl altogether? the next
stable won't need them

On Mon, Nov 6, 2017 at 9:53 AM, Kristoffer Ödmark
 wrote:

To be fair, as it stands now, even if it is "only" for the pin headers,
this is close to half of the 3d library size as of now.

The pin headers can now be of an arbitrary size as well. Someone can now
create a 4x6 pin header for example, and the current footprints can be
converted to this array system, thus reducing the size.

Arbitrary pin headers are a step up anyway.

This being said, I have not tested the patch yet, but even if it is "only"
for pin headers, the idea is sound to me.



On 11/06/2017 04:22 PM, easyw wrote:

Hi Oliver,

I'm sorry not to be on your side for this option...

1) for which kind of modules this array is applicable?
I see only pin-headers straight and angled...
for example box headers are not easily done unless you consider to manage
by the code the box for each model
2) the problem related to the big 3D library dimension will not be
covered unless for some little family that can be managed by this on the fly
generator

As I already suggested, the issue with the huge 3D github library can be
managed in a different way:
1) give the kicad users only a basic 3D library (i.e. most used smd and
th families)
2) give an option to pcbnew to automatically create a list of the missing
models needed for a project and collecting only them through a wget
process...

This will give a very low downloading band need and will not increase the
need of disk space for having all the 3D library locally, full of unwanted
models.

Here a conversation of this issue:
https://github.com/KiCad/kicad-library/issues/1532#issuecomment-341707706

my two-cents
Maurice

On 11/06/2017 3:01 PM, Oliver Walters wrote:

To provide an option to reduce the size of the 3D model library, I have
implemented an "array" feature for 3D models. A module (footprint) can
reference a single model multiple times, with a dimensional offset between
each copy.

(Note - just the PinHeader models are currently over 1GB! This feature
lets you use a single 3D model for all pin headers or similar repetitive
footprints within a certain series).

Features:

1. Specify repeat count and repeat step in x/y/z axes
2. Save / load implemented. (If no repeat option used, no extra output
is generated - old files are not touched)
3. Render in 3D viewer
4. Render in raytracing viewer
5. Export to VRML (multiple references to single file)
6. Export to STEP

Notes:

a. An exported STEP file will now be (possibly) much smaller as it
references a single small object multiple times
b. There were a couple of bugs I found where model offset units were
incorrectly translated between INCHES and MM

A couple of screenshots:

https://imgur.com/a/EOwPh


Testing:

Wayne verified that the file units for 3D model data are in mm - I
*think* this means that there was previously a bug regarding 3D model
offset, where the scaling factor in the file was interpreted as inches when
exporting (e.g. to STEP)

I believe I have fixed this bug - confirmation would be great.

Cheers,
Oliver


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


--
  -Kristoffer


___
Mailing list: https://launchpad.net/~kicad-developers
Post to :

Re: [Kicad-developers] [FEATURE] Array 3D models

2017-11-06 Thread José Ignacio

STEPs don't need to look ugly, a "simple" extension of the step format
could be a mtl file that indexes vrml materials to STEP colors, it would be
ignored by MCAD, but kicad could pick that up to significantly prettify the
step files in the 3d viewer without having to generate a redundant WRL file
(it wouldnt support fancier stuff like mapped textures but if you're
autogenerating models from the STEP anyway, how much better are you gonna
get?). Even when exporting a board to WRL in kicad it would use the 3d
cache data, so WRL models don't need to exist for wrl output for blender,
etc.

my $0.02

On Mon, Nov 6, 2017 at 3:17 PM, Cirilo Bernardo 
wrote:

> I wouldn't worry about the STEP file having numerous small parts;
> this happens all the time anyway unless the model can be fused.
> I don't see us abandoning VRML. I wrote the new parser but never
> use VRML except when testing the VRML parser. However, many
> people out there like to have VRML to make shiny models to show
> people.  I suspect there are more users who want VRML rather
> than STEP and that the STEP models are used mostly by
> professional users and hobbyists who happen to have an MCAD
> package. VRML is also used by some professionals for brochures
> or web page images; there is no disputing that STEP models look
> terribly ugly.
>
> On Mon, Nov 6, 2017 at 4:17 PM, José Ignacio 
> wrote:
> > The only thing i really have against this is that it would make a pretty
> > messy step file because the component would be broken up in tiny parts.
> > Wouldn't there be a space saving with just ditching wrl altogether? the
> next
> > stable won't need them
> >
> > On Mon, Nov 6, 2017 at 9:53 AM, Kristoffer Ödmark
> >  wrote:
> >>
> >> To be fair, as it stands now, even if it is "only" for the pin headers,
> >> this is close to half of the 3d library size as of now.
> >>
> >> The pin headers can now be of an arbitrary size as well. Someone can now
> >> create a 4x6 pin header for example, and the current footprints can be
> >> converted to this array system, thus reducing the size.
> >>
> >> Arbitrary pin headers are a step up anyway.
> >>
> >> This being said, I have not tested the patch yet, but even if it is
> "only"
> >> for pin headers, the idea is sound to me.
> >>
> >>
> >>
> >> On 11/06/2017 04:22 PM, easyw wrote:
> >>>
> >>> Hi Oliver,
> >>>
> >>> I'm sorry not to be on your side for this option...
> >>>
> >>> 1) for which kind of modules this array is applicable?
> >>> I see only pin-headers straight and angled...
> >>> for example box headers are not easily done unless you consider to
> manage
> >>> by the code the box for each model
> >>> 2) the problem related to the big 3D library dimension will not be
> >>> covered unless for some little family that can be managed by this on
> the fly
> >>> generator
> >>>
> >>> As I already suggested, the issue with the huge 3D github library can
> be
> >>> managed in a different way:
> >>> 1) give the kicad users only a basic 3D library (i.e. most used smd and
> >>> th families)
> >>> 2) give an option to pcbnew to automatically create a list of the
> missing
> >>> models needed for a project and collecting only them through a wget
> >>> process...
> >>>
> >>> This will give a very low downloading band need and will not increase
> the
> >>> need of disk space for having all the 3D library locally, full of
> unwanted
> >>> models.
> >>>
> >>> Here a conversation of this issue:
> >>> https://github.com/KiCad/kicad-library/issues/1532#
> issuecomment-341707706
> >>>
> >>> my two-cents
> >>> Maurice
> >>>
> >>> On 11/06/2017 3:01 PM, Oliver Walters wrote:
> 
>  To provide an option to reduce the size of the 3D model library, I
> have
>  implemented an "array" feature for 3D models. A module (footprint) can
>  reference a single model multiple times, with a dimensional offset
> between
>  each copy.
> 
>  (Note - just the PinHeader models are currently over 1GB! This feature
>  lets you use a single 3D model for all pin headers or similar
> repetitive
>  footprints within a certain series).
> 
>  Features:
> 
>  1. Specify repeat count and repeat step in x/y/z axes
>  2. Save / load implemented. (If no repeat option used, no extra output
>  is generated - old files are not touched)
>  3. Render in 3D viewer
>  4. Render in raytracing viewer
>  5. Export to VRML (multiple references to single file)
>  6. Export to STEP
> 
>  Notes:
> 
>  a. An exported STEP file will now be (possibly) much smaller as it
>  references a single small object multiple times
>  b. There were a couple of bugs I found where model offset units were
>  incorrectly translated between INCHES and MM
> 
>  A couple of screenshots:
> 
>  https://imgur.com/a/EOwPh
> 
> 
>  Testing:
> 
>  Wayne verified that the file units

Re: [Kicad-developers] [FEATURE] Array 3D models


On 2017-11-06 01:03 PM, Wayne Stambaugh wrote:

The second issue is that I imagine most users who export to step files
don't want to deal with a large array of single pin 3D models when they
are using the board 3D model for mechanical layout inside a 3D modeling
application such as FreeCAD.


That is a good point. I haven't exported a board in a while. Last time I did 
I only got the board without any of the 3D models I had added and could see 
in the 3D viewer. One option here would be to convert the array based models 
to a single 3D model on the fly during the export process.


--
Cheers!

Kevin.

http://www.ve3syb.ca/   |"Nerds make the shiny things that distract
Owner of Elecraft K2 #2172  | the mouth-breathers, and that's why we're
| powerful!"
#include  | --Chris Hardwick

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Replace .wrl files with .step on export (fixes lp:1710796)


On 2017-11-06 03:30 PM, Oliver Walters wrote:

Wayne,


Â /It would make more//
sense to me that kicad2step would attempt to substitute the wrl file
links withe step files when converting wrl to step./

This is exactly what it does. I'm not sure what you mean with embedded step 
file references.Â


I have also been wondering about the mention of substituting WRL files with 
STEP files on export. I would want to stick with the model files I specified 
in pcbnew and not have them automatically(?) changed in to some other format.


I do like to use VRML models in the 3D viewer of pcbnew as I can use 
textures and materials with them so they look good when I take a screen shot 
for use on a web page. The CAD software I use can import many model file 
formats including VRML and STEP. It doesn't matter to me which type is used 
when it comes time for me to load the file up to do mechanical design.


--
Cheers!

Kevin.

http://www.ve3syb.ca/   |"Nerds make the shiny things that distract
Owner of Elecraft K2 #2172  | the mouth-breathers, and that's why we're
| powerful!"
#include  | --Chris Hardwick

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

I wouldn't worry about the STEP file having numerous small parts;
this happens all the time anyway unless the model can be fused.
I don't see us abandoning VRML. I wrote the new parser but never
use VRML except when testing the VRML parser. However, many
people out there like to have VRML to make shiny models to show
people.  I suspect there are more users who want VRML rather
than STEP and that the STEP models are used mostly by
professional users and hobbyists who happen to have an MCAD
package. VRML is also used by some professionals for brochures
or web page images; there is no disputing that STEP models look
terribly ugly.

On Mon, Nov 6, 2017 at 4:17 PM, José Ignacio  wrote:
> The only thing i really have against this is that it would make a pretty
> messy step file because the component would be broken up in tiny parts.
> Wouldn't there be a space saving with just ditching wrl altogether? the next
> stable won't need them
>
> On Mon, Nov 6, 2017 at 9:53 AM, Kristoffer Ödmark
>  wrote:
>>
>> To be fair, as it stands now, even if it is "only" for the pin headers,
>> this is close to half of the 3d library size as of now.
>>
>> The pin headers can now be of an arbitrary size as well. Someone can now
>> create a 4x6 pin header for example, and the current footprints can be
>> converted to this array system, thus reducing the size.
>>
>> Arbitrary pin headers are a step up anyway.
>>
>> This being said, I have not tested the patch yet, but even if it is "only"
>> for pin headers, the idea is sound to me.
>>
>>
>>
>> On 11/06/2017 04:22 PM, easyw wrote:
>>>
>>> Hi Oliver,
>>>
>>> I'm sorry not to be on your side for this option...
>>>
>>> 1) for which kind of modules this array is applicable?
>>> I see only pin-headers straight and angled...
>>> for example box headers are not easily done unless you consider to manage
>>> by the code the box for each model
>>> 2) the problem related to the big 3D library dimension will not be
>>> covered unless for some little family that can be managed by this on the fly
>>> generator
>>>
>>> As I already suggested, the issue with the huge 3D github library can be
>>> managed in a different way:
>>> 1) give the kicad users only a basic 3D library (i.e. most used smd and
>>> th families)
>>> 2) give an option to pcbnew to automatically create a list of the missing
>>> models needed for a project and collecting only them through a wget
>>> process...
>>>
>>> This will give a very low downloading band need and will not increase the
>>> need of disk space for having all the 3D library locally, full of unwanted
>>> models.
>>>
>>> Here a conversation of this issue:
>>> https://github.com/KiCad/kicad-library/issues/1532#issuecomment-341707706
>>>
>>> my two-cents
>>> Maurice
>>>
>>> On 11/06/2017 3:01 PM, Oliver Walters wrote:

 To provide an option to reduce the size of the 3D model library, I have
 implemented an "array" feature for 3D models. A module (footprint) can
 reference a single model multiple times, with a dimensional offset between
 each copy.

 (Note - just the PinHeader models are currently over 1GB! This feature
 lets you use a single 3D model for all pin headers or similar repetitive
 footprints within a certain series).

 Features:

 1. Specify repeat count and repeat step in x/y/z axes
 2. Save / load implemented. (If no repeat option used, no extra output
 is generated - old files are not touched)
 3. Render in 3D viewer
 4. Render in raytracing viewer
 5. Export to VRML (multiple references to single file)
 6. Export to STEP

 Notes:

 a. An exported STEP file will now be (possibly) much smaller as it
 references a single small object multiple times
 b. There were a couple of bugs I found where model offset units were
 incorrectly translated between INCHES and MM

 A couple of screenshots:

 https://imgur.com/a/EOwPh

 Testing:

 Wayne verified that the file units for 3D model data are in mm - I
 *think* this means that there was previously a bug regarding 3D model
 offset, where the scaling factor in the file was interpreted as inches when
 exporting (e.g. to STEP)

 I believe I have fixed this bug - confirmation would be great.

 Cheers,
 Oliver

 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp

>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>> --
>>

Re: [Kicad-developers] [PATCH] Replace .wrl files with .step on export (fixes lp:1710796)

What is happening is that kicad2step will now take any file name with
*.wrl and attempt to open a similarly named stp/step file instead.
kicad2step will never support importing any actual wrl data since it
is not valid solid model data.

- Cirilo

On Mon, Nov 6, 2017 at 4:07 PM, Wayne Stambaugh  wrote:
> If I'm reading this patch correctly, exported wrl files will always have
> step file references in them even when they are found.  If that is the
> case, then I am opposed to this change.  AFAIK, opening the wrl board
> file will fail with the embedded step file links.  It would make more
> sense to me that kicad2step would attempt to substitute the wrl file
> links withe step files when converting wrl to step.
>
> On 11/4/2017 8:47 AM, Oliver Walters wrote:
>> The attached patch implements the feature suggested here
>> : https://bugs.launchpad.net/kicad/+bug/1710796
>>
>> Problem:
>>
>> .wrl files are specified as default but these don't export to MCAD.
>>
>> Solution:
>>
>> On STEP export, wrl files are replaced with their step counterparts (if
>> such models exist).
>>
>> This is essentially what Maurice's famous StepUP tool does.
>>
>> Turns out it was a pretty simple fix :)
>>
>> Regards,
>> Oliver
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models


On 2017-11-06 09:01 AM, Oliver Walters wrote:
To provide an option to reduce the size of the 3D model library, I have 
implemented an "array" feature for 3D models. A module (footprint) can 
reference a single model multiple times, with a dimensional offset between 
each copy.


Sounds interesting. This would be quite useful for IC packages (both through 
hole and surface mount) in addition to male and female headers.


And I forgot to add in my previous message it is also good for IC sockets.

--
Cheers!

Kevin.

http://www.ve3syb.ca/   |"Nerds make the shiny things that distract
Owner of Elecraft K2 #2172  | the mouth-breathers, and that's why we're
| powerful!"
#include  | --Chris Hardwick

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models


On 2017-11-06 09:01 AM, Oliver Walters wrote:
To provide an option to reduce the size of the 3D model library, I have 
implemented an "array" feature for 3D models. A module (footprint) can 
reference a single model multiple times, with a dimensional offset between 
each copy.


Sounds interesting. This would be quite useful for IC packages (both through 
hole and surface mount) in addition to male and female headers.


--
Cheers!

Kevin.

http://www.ve3syb.ca/   |"Nerds make the shiny things that distract
Owner of Elecraft K2 #2172  | the mouth-breathers, and that's why we're
| powerful!"
#include  | --Chris Hardwick

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Replace .wrl files with .step on export (fixes lp:1710796)

Wayne,


 *It would make more*

*sense to me that kicad2step would attempt to substitute the wrl filelinks
withe step files when converting wrl to step.*

This is exactly what it does. I'm not sure what you mean with embedded step
file references.

On 7 Nov 2017 03:07, "Wayne Stambaugh"  wrote:

If I'm reading this patch correctly, exported wrl files will always have
step file references in them even when they are found.  If that is the
case, then I am opposed to this change.  AFAIK, opening the wrl board
file will fail with the embedded step file links.  It would make more
sense to me that kicad2step would attempt to substitute the wrl file
links withe step files when converting wrl to step.

On 11/4/2017 8:47 AM, Oliver Walters wrote:
> The attached patch implements the feature suggested here
> : https://bugs.launchpad.net/kicad/+bug/1710796
>
> Problem:
>
> .wrl files are specified as default but these don't export to MCAD.
>
> Solution:
>
> On STEP export, wrl files are replaced with their step counterparts (if
> such models exist).
>
> This is essentially what Maurice's famous StepUP tool does.
>
> Turns out it was a pretty simple fix :)
>
> Regards,
> Oliver
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

Hey Oliver,

I don't think this is the way to go.  I see two primary issues.  The
first is the impact on the code clarity.  If this only stopped at your
changes, it might be fine but how many other array or grouping
permutations will happen over time making this code a huge mess?  I just
see this spiraling out of control.  The second issue is that I imagine
most users who export to step files don't want to deal with a large
array of single pin 3D models when they are using the board 3D model for
mechanical layout inside a 3D modeling application such as FreeCAD.  I
know I would rather only deal with a single connector model of a 50 pin
dual row header rather than 50 individual 3D models arranged in an
array.  To be honest, I don't find the library size to be much of an issue.

Cheers,

Wayne

On 11/6/2017 9:01 AM, Oliver Walters wrote:
> To provide an option to reduce the size of the 3D model library, I have
> implemented an "array" feature for 3D models. A module (footprint) can
> reference a single model multiple times, with a dimensional offset
> between each copy.
> 
> (Note - just the PinHeader models are currently over 1GB! This feature
> lets you use a single 3D model for all pin headers or similar repetitive
> footprints within a certain series).
> 
> Features:
> 
> 1. Specify repeat count and repeat step in x/y/z axes
> 2. Save / load implemented. (If no repeat option used, no extra output
> is generated - old files are not touched)
> 3. Render in 3D viewer
> 4. Render in raytracing viewer
> 5. Export to VRML (multiple references to single file)
> 6. Export to STEP
> 
> Notes:
> 
> a. An exported STEP file will now be (possibly) much smaller as it
> references a single small object multiple times
> b. There were a couple of bugs I found where model offset units were
> incorrectly translated between INCHES and MM
> 
> A couple of screenshots:
> 
> https://imgur.com/a/EOwPh
> 
> 
> Testing:
> 
> Wayne verified that the file units for 3D model data are in mm - I
> *think* this means that there was previously a bug regarding 3D model
> offset, where the scaling factor in the file was interpreted as inches
> when exporting (e.g. to STEP)
> 
> I believe I have fixed this bug - confirmation would be great.
> 
> Cheers,
> Oliver
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Draw junctions last

2017-11-06 Thread Seth Hillbrand

Hi Nick-

Attached are two images, showing the issue and the resolution.  The
attached schematic should also show it on your machine.  Note that this is
captured in Eldar's bug report as well.

-Seth

On Mon, Nov 6, 2017 at 4:37 AM, Nick Østergaard  wrote:

> What does the issue look like visually? Do you have a demo file to verify
> this patch? This is nice to know if someone reports this issue in stable.
>
> 2017-11-03 21:08 GMT+01:00 Kevin Cozens :
>
>> On 2017-11-03 02:00 PM, Seth Hillbrand wrote:
>>
>>> â€‹Kevin made a â€‹request to have junctions draw last on schematics to
>>> avoid a visual negative.
>>>
>>> This patch provides that functionality.
>>>
>>
>> tyvm, Seth. I applied your patch to the latest code from git master and
>> it worked.
>>
>> --
>> Cheers!
>>
>> Kevin.
>>
>> http://www.ve3syb.ca/   |"Nerds make the shiny things that
>> distract
>> Owner of Elecraft K2 #2172  | the mouth-breathers, and that's why
>> we're
>> | powerful!"
>> #include  | --Chris Hardwick
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>


test_proj.sch
Description: application/geda-schematic
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

Hi,
referring to:
"even if it is "only" for the pin headers, this is close to half of the
3d library size as of now"
you probably missed the 3d library status...please have a look at recent
PRs of the 3D library

There are contributors of new models that are afraid to contribute
because of their model family big size (1G) ...

https://github.com/easyw/kicad-3d-models-in-freecad/pull/115#issuecomment-341058146

The 3D library is growing day by day and it will became bigger and
bigger I hope... I consider this the best 3D mechanical library
available ATM

This is not an issue on on-line library size IMO... this is an issue on
what has to be bundled with the installer and what has to downloaded
when needed... the all family of models (actual policy) or only the
model that the project is going to use.

Moreover with the suggested patch, if you want to check a model
dimensions in MCAD environment, you will need to create a fake board in
kicad, assign a footprint, generate the step and then open it in
mechanical sw to see dimensions, instead of just download it from github
and check if this is fine for your design...

So my suggestion is not to create some exception case for the library, but:
1) find a way to manage what is going to be deployed to the users
2) create a script/code to download what is needed by the project
itself, if missing...

3) select a 3D library base to be deployed with the main installer

The second point could done by a function to be called inside Kicad or
pcbnew to create a full list of needed 3D parts for the user kicad project.
Then the function could check automatically if those models are already
in the users local 3D library and give an option to retrieve with a
'wget' process the missing models from kicad on-line library.
Finally the downloaded missing models would be placed automatically in
the right local folder by the function itself.

For example if you need:
'Buttons_Switches_SMD.3dshapes/SW_SP3T_PCM13.step'
your wget could point to:
https://github.com/KiCad/kicad-packages3D/raw/master/Buttons_Switches_SMD.3dshapes/SW_SP3T_PCM13.step
and download it directly, placing it to local configured
'KISYS3DMOD'+Buttons_Switches_SMD.3dshapes/
folder.
This could be even done as a python Action Script for Kicad

Maurice

On 11/06/2017 4:53 PM, Kristoffer Ödmark wrote:
To be fair, as it stands now, even if it is "only" for the pin headers,
this is close to half of the 3d library size as of now.

The pin headers can now be of an arbitrary size as well. Someone can now
create a 4x6 pin header for example, and the current footprints can be
converted to this array system, thus reducing the size.

Arbitrary pin headers are a step up anyway.

This being said, I have not tested the patch yet, but even if it is
"only" for pin headers, the idea is sound to me.

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

2017-11-06 Thread José Ignacio

The only thing i really have against this is that it would make a pretty
messy step file because the component would be broken up in tiny parts.
Wouldn't there be a space saving with just ditching wrl altogether? the
next stable won't need them

On Mon, Nov 6, 2017 at 9:53 AM, Kristoffer Ödmark <
kristofferodmar...@gmail.com> wrote:

> To be fair, as it stands now, even if it is "only" for the pin headers,
> this is close to half of the 3d library size as of now.
>
> The pin headers can now be of an arbitrary size as well. Someone can now
> create a 4x6 pin header for example, and the current footprints can be
> converted to this array system, thus reducing the size.
>
> Arbitrary pin headers are a step up anyway.
>
> This being said, I have not tested the patch yet, but even if it is "only"
> for pin headers, the idea is sound to me.
>
>
>
> On 11/06/2017 04:22 PM, easyw wrote:
>
>> Hi Oliver,
>>
>> I'm sorry not to be on your side for this option...
>>
>> 1) for which kind of modules this array is applicable?
>> I see only pin-headers straight and angled...
>> for example box headers are not easily done unless you consider to manage
>> by the code the box for each model
>> 2) the problem related to the big 3D library dimension will not be
>> covered unless for some little family that can be managed by this on the
>> fly generator
>>
>> As I already suggested, the issue with the huge 3D github library can be
>> managed in a different way:
>> 1) give the kicad users only a basic 3D library (i.e. most used smd and
>> th families)
>> 2) give an option to pcbnew to automatically create a list of the missing
>> models needed for a project and collecting only them through a wget
>> process...
>>
>> This will give a very low downloading band need and will not increase the
>> need of disk space for having all the 3D library locally, full of unwanted
>> models.
>>
>> Here a conversation of this issue:
>> https://github.com/KiCad/kicad-library/issues/1532#issuecomment-341707706
>>
>> my two-cents
>> Maurice
>>
>> On 11/06/2017 3:01 PM, Oliver Walters wrote:
>>
>>> To provide an option to reduce the size of the 3D model library, I have
>>> implemented an "array" feature for 3D models. A module (footprint) can
>>> reference a single model multiple times, with a dimensional offset between
>>> each copy.
>>>
>>> (Note - just the PinHeader models are currently over 1GB! This feature
>>> lets you use a single 3D model for all pin headers or similar repetitive
>>> footprints within a certain series).
>>>
>>> Features:
>>>
>>> 1. Specify repeat count and repeat step in x/y/z axes
>>> 2. Save / load implemented. (If no repeat option used, no extra output
>>> is generated - old files are not touched)
>>> 3. Render in 3D viewer
>>> 4. Render in raytracing viewer
>>> 5. Export to VRML (multiple references to single file)
>>> 6. Export to STEP
>>>
>>> Notes:
>>>
>>> a. An exported STEP file will now be (possibly) much smaller as it
>>> references a single small object multiple times
>>> b. There were a couple of bugs I found where model offset units were
>>> incorrectly translated between INCHES and MM
>>>
>>> A couple of screenshots:
>>>
>>> https://imgur.com/a/EOwPh
>>>
>>>
>>> Testing:
>>>
>>> Wayne verified that the file units for 3D model data are in mm - I
>>> *think* this means that there was previously a bug regarding 3D model
>>> offset, where the scaling factor in the file was interpreted as inches when
>>> exporting (e.g. to STEP)
>>>
>>> I believe I have fixed this bug - confirmation would be great.
>>>
>>> Cheers,
>>> Oliver
>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
> --
>  -Kristoffer
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Replace .wrl files with .step on export (fixes lp:1710796)

If I'm reading this patch correctly, exported wrl files will always have
step file references in them even when they are found.  If that is the
case, then I am opposed to this change.  AFAIK, opening the wrl board
file will fail with the embedded step file links.  It would make more
sense to me that kicad2step would attempt to substitute the wrl file
links withe step files when converting wrl to step.

On 11/4/2017 8:47 AM, Oliver Walters wrote:
> The attached patch implements the feature suggested here
> : https://bugs.launchpad.net/kicad/+bug/1710796
> 
> Problem:
> 
> .wrl files are specified as default but these don't export to MCAD. 
> 
> Solution:
> 
> On STEP export, wrl files are replaced with their step counterparts (if
> such models exist).
> 
> This is essentially what Maurice's famous StepUP tool does.
> 
> Turns out it was a pretty simple fix :)
> 
> Regards,
> Oliver
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models

2017-11-06 Thread Kristoffer Ödmark

To be fair, as it stands now, even if it is "only" for the pin headers, 
this is close to half of the 3d library size as of now.


The pin headers can now be of an arbitrary size as well. Someone can now 
create a 4x6 pin header for example, and the current footprints can be 
converted to this array system, thus reducing the size.


Arbitrary pin headers are a step up anyway.

This being said, I have not tested the patch yet, but even if it is 
"only" for pin headers, the idea is sound to me.



On 11/06/2017 04:22 PM, easyw wrote:

Hi Oliver,

I'm sorry not to be on your side for this option...

1) for which kind of modules this array is applicable?
I see only pin-headers straight and angled...
for example box headers are not easily done unless you consider to 
manage by the code the box for each model
2) the problem related to the big 3D library dimension will not be 
covered unless for some little family that can be managed by this on the 
fly generator


As I already suggested, the issue with the huge 3D github library can be 
managed in a different way:
1) give the kicad users only a basic 3D library (i.e. most used smd and 
th families)
2) give an option to pcbnew to automatically create a list of the 
missing models needed for a project and collecting only them through a 
wget process...


This will give a very low downloading band need and will not increase 
the need of disk space for having all the 3D library locally, full of 
unwanted models.


Here a conversation of this issue:
https://github.com/KiCad/kicad-library/issues/1532#issuecomment-341707706

my two-cents
Maurice

On 11/06/2017 3:01 PM, Oliver Walters wrote:
To provide an option to reduce the size of the 3D model library, I 
have implemented an "array" feature for 3D models. A module 
(footprint) can reference a single model multiple times, with a 
dimensional offset between each copy.


(Note - just the PinHeader models are currently over 1GB! This feature 
lets you use a single 3D model for all pin headers or similar 
repetitive footprints within a certain series).


Features:

1. Specify repeat count and repeat step in x/y/z axes
2. Save / load implemented. (If no repeat option used, no extra output 
is generated - old files are not touched)

3. Render in 3D viewer
4. Render in raytracing viewer
5. Export to VRML (multiple references to single file)
6. Export to STEP

Notes:

a. An exported STEP file will now be (possibly) much smaller as it 
references a single small object multiple times
b. There were a couple of bugs I found where model offset units were 
incorrectly translated between INCHES and MM


A couple of screenshots:

https://imgur.com/a/EOwPh


Testing:

Wayne verified that the file units for 3D model data are in mm - I 
*think* this means that there was previously a bug regarding 3D model 
offset, where the scaling factor in the file was interpreted as inches 
when exporting (e.g. to STEP)


I believe I have fixed this bug - confirmation would be great.

Cheers,
Oliver


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


--
 -Kristoffer

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [FEATURE] Array 3D models


Hi Oliver,

I'm sorry not to be on your side for this option...

1) for which kind of modules this array is applicable?
I see only pin-headers straight and angled...
for example box headers are not easily done unless you consider to 
manage by the code the box for each model
2) the problem related to the big 3D library dimension will not be 
covered unless for some little family that can be managed by this on the 
fly generator


As I already suggested, the issue with the huge 3D github library can be 
managed in a different way:
1) give the kicad users only a basic 3D library (i.e. most used smd and 
th families)
2) give an option to pcbnew to automatically create a list of the 
missing models needed for a project and collecting only them through a 
wget process...


This will give a very low downloading band need and will not increase 
the need of disk space for having all the 3D library locally, full of 
unwanted models.


Here a conversation of this issue:
https://github.com/KiCad/kicad-library/issues/1532#issuecomment-341707706

my two-cents
Maurice

On 11/06/2017 3:01 PM, Oliver Walters wrote:
To provide an option to reduce the size of the 3D model library, I have 
implemented an "array" feature for 3D models. A module (footprint) can 
reference a single model multiple times, with a dimensional offset 
between each copy.


(Note - just the PinHeader models are currently over 1GB! This feature 
lets you use a single 3D model for all pin headers or similar repetitive 
footprints within a certain series).


Features:

1. Specify repeat count and repeat step in x/y/z axes
2. Save / load implemented. (If no repeat option used, no extra output 
is generated - old files are not touched)

3. Render in 3D viewer
4. Render in raytracing viewer
5. Export to VRML (multiple references to single file)
6. Export to STEP

Notes:

a. An exported STEP file will now be (possibly) much smaller as it 
references a single small object multiple times
b. There were a couple of bugs I found where model offset units were 
incorrectly translated between INCHES and MM


A couple of screenshots:

https://imgur.com/a/EOwPh


Testing:

Wayne verified that the file units for 3D model data are in mm - I 
*think* this means that there was previously a bug regarding 3D model 
offset, where the scaling factor in the file was interpreted as inches 
when exporting (e.g. to STEP)


I believe I have fixed this bug - confirmation would be great.

Cheers,
Oliver


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Footprint file format question

I think that the bug is only present in the way that the offset is
displayed in the footprint preview window. I will not break compatibility :)

On Mon, Nov 6, 2017 at 11:59 PM, Wayne Stambaugh 
wrote:

> Be careful here.  If the 3d model offset is currently in some units
> other than mm and you change this, all existing 3d model offsets will be
> broken.
>
> On 11/6/2017 7:56 AM, Oliver Walters wrote:
> > That's what I expected. It then appears that there is a bug in the 3D
> > code with regard to model offset. I'm working on a related patch set
> > that will fix this, I just wanted to be sure. Thanks Wayne
> >
> > On Mon, Nov 6, 2017 at 11:53 PM, Wayne Stambaugh  > > wrote:
> >
> > It should be mm like all of the other coordinates.
> >
> > On 11/6/2017 7:32 AM, Oliver Walters wrote:
> > > With regard to the 3D model offset paramater
> > >
> > > e.g.
> > >
> > > (at (xyz a b c))
> > >
> > > Are the units stored in the file inches or mm?
> > >
> > > Cheers,
> > > Oliver
> > >
> > >
> > > ___
> > > Mailing list: https://launchpad.net/~kicad-developers
> > 
> > > Post to : kicad-developers@lists.launchpad.net
> > 
> > > Unsubscribe : https://launchpad.net/~kicad-developers
> > 
> > > More help   : https://help.launchpad.net/ListHelp
> > 
> > >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > 
> > Post to : kicad-developers@lists.launchpad.net
> > 
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > 
> > More help   : https://help.launchpad.net/ListHelp
> > 
> >
> >
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] KiCad Library Download Page

The reason that it is breaking is that I am currently generating a unique
download link for each individual 3D model group. A "group" contains .wrl
and .step pairs.

If I do not go this far, and provide a single archive for each "folder" of
files then the generator still works fine..

For now at least I think I will go with the simpler approach which means we
can still have a front-facing download page that we do not have to serve.

Incidentally the 3d-shapes downloader tool in KiCad needs some love. It
fails on folders with more than 1000 files! This is a github API limitation
I think.

On Mon, Nov 6, 2017 at 11:50 PM, Wayne Stambaugh 
wrote:

> I'm not sure what to do about this.  I'm not opposed adding this to the
> kicad website.  Do we even have enough server space on the kicad website
> to handle this?  Anyone else have any ideas?
>
> Who knew the kicad project would reach these kinds of limits so quickly.
>  Kudos to the library devs for all of their hard work.
>
> On 11/5/2017 7:35 AM, Oliver Walters wrote:
> > Should this be something that is served on kicad-pcb.org/downloads
> >  ? I am concerned that we might run into
> > GitHub TOS issues.
> >
> > I am working on generating the 3D models for download. However this
> > generates lots of data (multiple gigabytes). It also takes over 1hr for
> > Travis to build, which exceeds the allowable Travis script runtime.
> >
> > On Fri, Nov 3, 2017 at 11:31 AM, Oliver Walters
> > >
> > wrote:
> >
> > Hi all,
> >
> > Stage 2 of ? of the library update project is underway.
> >
> > Idea: A downloads page for the libraries that presents individual
> > libraries for download, and users can preview the data available in
> > the libraries.
> >
> > This is auto-built based on the latest library data.
> >
> > Preview: https://kicad.github.io/symbols/
> > 
> >
> > I have wrangled the GitHub pages tool along with Travis CI to
> > auto-build these pages. It provides compressed downloads of symbol
> > libs thus far.
> >
> > To do:
> >
> > 1. Downloads for footprint libs
> > 2. Downloads for 3D models
> > 3. Improve scripts so that data that have not changed are not
> > recompressed (reduce build time and also remove useless git updates)
> >
> > Thoughts?
> >
> > The general idea is that this page will be linked from
> > http://kicad-pcb.org/libraries/download
> > 
> >
> > Cheers,
> > Oliver
> >
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Footprint file format question

2017-11-06 Thread Simon Wells

at some point changing the models to be mm rather than 0.1" or whatever it is 
now needs to be seriously looked at


> On 7/11/2017, at 01:59, Wayne Stambaugh  wrote:
> 
> Be careful here.  If the 3d model offset is currently in some units
> other than mm and you change this, all existing 3d model offsets will be
> broken.
> 
> On 11/6/2017 7:56 AM, Oliver Walters wrote:
>> That's what I expected. It then appears that there is a bug in the 3D
>> code with regard to model offset. I'm working on a related patch set
>> that will fix this, I just wanted to be sure. Thanks Wayne
>> 
>> On Mon, Nov 6, 2017 at 11:53 PM, Wayne Stambaugh > > wrote:
>> 
>>It should be mm like all of the other coordinates.
>> 
>>On 11/6/2017 7:32 AM, Oliver Walters wrote:
>>> With regard to the 3D model offset paramater
>>> 
>>> e.g. 
>>> 
>>> (at (xyz a b c))
>>> 
>>> Are the units stored in the file inches or mm?
>>> 
>>> Cheers,
>>> Oliver
>>> 
>>> 
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>
>>> Post to : kicad-developers@lists.launchpad.net
>>
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>
>>> More help   : https://help.launchpad.net/ListHelp
>>
>>> 
>> 
>>___
>>Mailing list: https://launchpad.net/~kicad-developers
>>
>>Post to : kicad-developers@lists.launchpad.net
>>
>>Unsubscribe : https://launchpad.net/~kicad-developers
>>
>>More help   : https://help.launchpad.net/ListHelp
>>
>> 
>> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Footprint file format question

Be careful here.  If the 3d model offset is currently in some units
other than mm and you change this, all existing 3d model offsets will be
broken.

On 11/6/2017 7:56 AM, Oliver Walters wrote:
> That's what I expected. It then appears that there is a bug in the 3D
> code with regard to model offset. I'm working on a related patch set
> that will fix this, I just wanted to be sure. Thanks Wayne
> 
> On Mon, Nov 6, 2017 at 11:53 PM, Wayne Stambaugh  > wrote:
> 
> It should be mm like all of the other coordinates.
> 
> On 11/6/2017 7:32 AM, Oliver Walters wrote:
> > With regard to the 3D model offset paramater
> >
> > e.g. 
> >
> > (at (xyz a b c))
> >
> > Are the units stored in the file inches or mm?
> >
> > Cheers,
> > Oliver
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> 
> > Post to     : kicad-developers@lists.launchpad.net
> 
> > Unsubscribe : https://launchpad.net/~kicad-developers
> 
> > More help   : https://help.launchpad.net/ListHelp
> 
> >
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> 
> Post to     : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> 
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Footprint file format question

That's what I expected. It then appears that there is a bug in the 3D code
with regard to model offset. I'm working on a related patch set that will
fix this, I just wanted to be sure. Thanks Wayne

On Mon, Nov 6, 2017 at 11:53 PM, Wayne Stambaugh 
wrote:

> It should be mm like all of the other coordinates.
>
> On 11/6/2017 7:32 AM, Oliver Walters wrote:
> > With regard to the 3D model offset paramater
> >
> > e.g.
> >
> > (at (xyz a b c))
> >
> > Are the units stored in the file inches or mm?
> >
> > Cheers,
> > Oliver
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Footprint file format question

It should be mm like all of the other coordinates.

On 11/6/2017 7:32 AM, Oliver Walters wrote:
> With regard to the 3D model offset paramater
> 
> e.g. 
> 
> (at (xyz a b c))
> 
> Are the units stored in the file inches or mm?
> 
> Cheers,
> Oliver
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] KiCad Library Download Page

I'm not sure what to do about this.  I'm not opposed adding this to the
kicad website.  Do we even have enough server space on the kicad website
to handle this?  Anyone else have any ideas?

Who knew the kicad project would reach these kinds of limits so quickly.
 Kudos to the library devs for all of their hard work.

On 11/5/2017 7:35 AM, Oliver Walters wrote:
> Should this be something that is served on kicad-pcb.org/downloads
>  ? I am concerned that we might run into
> GitHub TOS issues.
> 
> I am working on generating the 3D models for download. However this
> generates lots of data (multiple gigabytes). It also takes over 1hr for
> Travis to build, which exceeds the allowable Travis script runtime.
> 
> On Fri, Nov 3, 2017 at 11:31 AM, Oliver Walters
> >
> wrote:
> 
> Hi all,
> 
> Stage 2 of ? of the library update project is underway.
> 
> Idea: A downloads page for the libraries that presents individual
> libraries for download, and users can preview the data available in
> the libraries.
> 
> This is auto-built based on the latest library data.
> 
> Preview: https://kicad.github.io/symbols/
> 
> 
> I have wrangled the GitHub pages tool along with Travis CI to
> auto-build these pages. It provides compressed downloads of symbol
> libs thus far.
> 
> To do:
> 
> 1. Downloads for footprint libs
> 2. Downloads for 3D models
> 3. Improve scripts so that data that have not changed are not
> recompressed (reduce build time and also remove useless git updates)
> 
> Thoughts?
> 
> The general idea is that this page will be linked from
> http://kicad-pcb.org/libraries/download
> 
> 
> Cheers,
> Oliver 
> 
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Draw junctions last

2017-11-06 Thread Nick Østergaard

What does the issue look like visually? Do you have a demo file to verify
this patch? This is nice to know if someone reports this issue in stable.

2017-11-03 21:08 GMT+01:00 Kevin Cozens :

> On 2017-11-03 02:00 PM, Seth Hillbrand wrote:
>
>> â€‹Kevin made a â€‹request to have junctions draw last on schematics to
>> avoid a visual negative.
>>
>> This patch provides that functionality.
>>
>
> tyvm, Seth. I applied your patch to the latest code from git master and it
> worked.
>
> --
> Cheers!
>
> Kevin.
>
> http://www.ve3syb.ca/   |"Nerds make the shiny things that
> distract
> Owner of Elecraft K2 #2172  | the mouth-breathers, and that's why we're
> | powerful!"
> #include  | --Chris Hardwick
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Footprint file format question

With regard to the 3D model offset paramater

e.g.

(at (xyz a b c))

Are the units stored in the file inches or mm?

Cheers,
Oliver
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Replace .wrl files with .step on export (fixes lp:1710796)