modularized root cups
benzvan opened this issue · 6 comments
I'd love for the root objects like gridfinity_basic_cup to be useable as modules in other projects. This would mean moving some of the variables like height, length, width, withLabel, etc. into parameters in the basic_cup module. The existing variables could be changed to default_length, etc. and used as default values.
I'm happy to open a PR if this seems worthwhile to you.
I guess as I look at this a little more, it would just be basic_cup and baseplate that would make sense. The others are purpose built objects.
I do generally prefer the approach of using parameters instead of global variables because it's more reusable that way. I think this is a positive direction and I would be interested to see the specifics in a PR.
Cool. I'll get something going.
Here's my idea: #11
I also locally created options for a shorter label tab and to truncate the cups for printing larger than the available print area that I could submit.
Thank you for the PR. I agree with propagating the parameters instead of using global variables, but there are some aspects that I'm not sure about. The variables are called defaults, but they are really overrides and the defaults (values used if the model were imported with a use statement) are still magic numbers in the module definition.
I took your idea and went for a deeper change, where the cup is promoted to its own file in the modules folder, and the basic gridfinity_basic_cup still exists and references it. The defaults live in the module file, and the overrides are in the client file. Having the cup as a module that can be used is also perhaps more inviting for modified versions.
I haven't made this official yet. I committed 755f032 to a branch and I'm interested in your opinion.