kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

On 6/16/2015 11:58 AM, Tomasz Wlostowski wrote:
> On 16.06.2015 17:35, Mário Luzeiro wrote:
>>
>> ________________________________________
>> From: Kicad-developers [kicad-developers-bounces+mrluzeiro=ua.pt@xxxxxxxxxxxxxxxxxxx] on behalf of Tomasz Wlostowski [tomasz.wlostowski@xxxxxxx]
>> Sent: 16 June 2015 17:13
>> To: Wayne Stambaugh; kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Subject: Re: [Kicad-developers] Plugin plans (post-stable release)
>>
>>>> Also, I know to some of you I sound like a broken record but none of
>>>> this can happen until the underlying 3D model library code is fixed.
>>
>>> Fully agree. AFAIK Mario was volunteering to work on the 3D models?
>>
>>> Tom
>>
>>
>> Is Mario == Me ?
> 
> Hi Mario,
> 
> Yes, I meant you.
> 
>> I am following this discussion but I am having difficult to understand some parts here and the relation with 3d-viewer.
> 
> Basically, we need (just a brain dump below):
> - a cleanup of the 3D model loading/storage code: a clean mesh class
> (holding the geometry/assembly info) and refactoring of the 3d-viewer
> (and further on, exporter code) to use it. I see you made the S3D_MESH
> class, which is already quite clean and could be easily integrated with
> the STEP mesher. One thing that might be needed is storing same
> sub-meshes with different transforms (imagine a BGA footprint with 1000
> identical balls - the current design of the class requires copying the
> mesh data 1000 times, correct me if I'm wrong please).
> - improved way to associate a STEP/IGES/VRML/whatever with the PCB
> footprints.
> - @Wayne - anything else?

I'm certain I've mentioned this before but I expect a sane I/O manager
design something like PCB_IO and IO_MGR used in Pcbnew.  I want to see
this design use either the base classes in richio.h, streams, or
wxStreams for I/O and not be tied directly to reading and writing files.
 There also needs to be an intelligent way to handle different model
library types (VRML, STEP, IGES, etc.) and abstract away platform path
differences like the footprint library table used in Pcbnew.  Once this
is in place, we can port the current VRML I/O over to the new I/O code
and begin adding new model types.

> 
> Regards,
> Tom
> 
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>