adding sample script generated SSOP, TSSOP, MSOP w/ STEP & WRL parametric model

[easyw]

models are generated by parametric scripts, WRL with KiCAD suggested materials
(for the full family models only dimension parameters need to be added to the scripts)

https://github.com/easyw/kicad-3d-models-in-freecad/tree/master/cadquery/FCAD_script_generator

discussion related at

https://forum.kicad.info/t/contributing-to-update-of-vrml-librarys-to-step/5049/

[SchrodingersGat]

I'd like to ensure that all the footprints currently in the SSOP library are encoded here before we merge.

[easyw]

@SchrodingersGat I would be very pleased to have all SSOP library encoded, but I have no time to do it now...
Moreover there are footprint without 3D models already in kicad-library, so I don't see the point...
Let me explain why I just wanted to merge some sample; having some model ready, the users will have the knowledge that for mechanical model for SSOP family it is already available a script to produce the model in a parametric way...
If someone would need a specific SSOP model of a kicad_mod, now he/she can just look at the DS and create the model simply filling the case parameters... and then merge the new model, giving something back to the community.
Something is much better than nothing IMO

[poeschlr]

the users will have the knowledge that for mechanical model for SSOP family it is already available a script to produce the model in a parametric way...

For that to work there needs to be some information within the library. Example a readme file that explains this. (But i fear nobody will read this. Most people just use the files provided by kicad and never notice that they are from github.)

As for time: I think i'm also booked until end of march (date of shell eco marthon). Maybe i will find some time to cleanup the script repo. But i fear it will be on a script by script basis starting with my own scripts. (Maybe if i reduce my time spent on the forum i will have more time for stuff like that but the instant gratification monkey doesn't understand that.)

[easyw]

For that to work there needs to be some information within the library. Example a readme file that explains this.

In the PR there is already the reference to the script location....
Anyway I really don't see why we cannot start adding some 3d models and later add other models... STEP by step 😉
is the footprint library complete of all footprint around?

[poeschlr]

Anyway I really don't see why we cannot start adding some 3d models and later add other models... STEP by step

I agree with this statement. And i am in favor of merging it.

In the PR there is already the reference to the script location.

Do you really think anybody will search in (closed) pull requests for information.

But to be honest my best solution would be a note in some sort of readme file. But i think this will not be read either. (So ... ideas?)

[SchrodingersGat]

The solution is to have clear links to the source files in the Wiki. I'll merge this one but we need to consider how users are made aware of the source files.

We also need (at some stage) to start building up the sources repo.

[easyw]

@SchrodingersGat

The solution is to have clear links to the source files in the Wiki.

that is good to have...

@poeschlr

my best solution would be a note in some sort of readme file

probably something like a credits.md file placed in each 3D folder, including authors and a link to script generator when used could be useful too and easy to maintain

[SchrodingersGat]

https://github.com/KiCad/packages3D/blob/master/CREDITS.md I think a top-level file should be enough

[SchrodingersGat]

Please add to that file when new 3D models are added

[easyw]

I think a top-level file should be enough

It may risk to became a huge monster file difficult to manage...
Anyway, I'm going to fill it for the models I added