kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #15797
Re: code for 3d model generator
-
To:
kicad-developers@xxxxxxxxxxxxxxxxxxx
-
From:
Wayne Stambaugh <stambaughw@xxxxxxxxxxx>
-
Date:
Sat, 15 Nov 2014 10:19:47 -0500
-
In-reply-to:
<CAHBNN+OnJhm4ecG7vo6ySOdxvAJ0Q=B7irfgp1YV3LozC1QZPw@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
On 11/14/2014 6:38 PM, Cirilo Bernardo wrote:
> For over 2 years I have maintained a project for generating VRML models
> for use with KiCad.
> ( See http://kicad3dmodels.sourceforge.net. ) The code includes basic
> objects or tools
> which can be used to describe parts using parametric models. I think if
> the source can be
> included in KiCad then more people will use it and perhaps even
> contribute to extending
> the code. If this sounds like a good idea, let me know and I will start
> preparing the code for
> inclusion in KiCad. This will take some time since I will have to review
> the coding style and
> modify the CMake files to integrate well with the KiCad source.
>
> I would propose to add these tools to the 'utils' source directory since
> it is an independent tool.
> Initial builds would have to be optional since the code has currently
> only been tested on Linux;
> one of the reasons I would like to move the source into KiCad is to get
> more feedback on
> cross-platform builds. Hopefully the tools will eventually run on all
> supported platforms and can
> become a default enabled tool in KiCad. One advantage of this parametric
> modeling is that
> much less memory is required to produce high quality models when
> compared to the current
> popular technique of manual modeling in Wings3D + conversion to VRML.
> The current tools for
> example have a number of Python scripts which can generate many
> thousands of models.
>
> - Cirilo
>
Cirilo,
I recommend that you push your changes to a separate branch on launchpad
and submit a merger request so other developers can test and comment on
you changes. Once there is enough developer support, the changes can be
merged into the product branch. This is my preferred way of merging
large change sets into the product branch. For small change sets,
patches are preferred.
Thanks,
Wayne
Follow ups
References