Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Floor Library #77

Open
Tracked by #78
ClaudeMetz opened this issue Jul 24, 2023 · 0 comments
Open
Tracked by #78

Floor Library #77

ClaudeMetz opened this issue Jul 24, 2023 · 0 comments

Comments

@ClaudeMetz
Copy link
Owner

The main idea is that users won't have to re-layout the same recipe chain over and over. This could be achieved in a number of different ways, but this seems like the most sensible to me.

Split the side subfactory list into two sections, one as normal and the other being a list of 'subfactories' that can be used elsewhere.

These 'subfactories' need to be based on a recipe, they are basically subfloors. Not quite sure what this would look like, probably a fixed first recipe as on subfloors and unchangeable products.

They can be configured and are reduced to a 'simple' input->output equation for performance, and then used in proper subfactories in place of defining subfloors oneself.

How the interaction will look like is to be determined. One idea is to have the user pick the recipe first and then modifier-click it to pick a floor from the library to use. Another could be a choice built into the recipe picker itself. There are other possibilities too.

These recipes would be linked to the 'canonical' version the library, meaning if it changes, it'll change everywhere it's used. This is a bit problematic since you might want to keep an old plan as it is built, but change the library for future builds. Not sure how to address that. The user could just duplicate the old one and modify it then, but that creates a lot of duplicates over time. One solution could be to duplicate it and bake the previous ones in, meaning it'd remove them from the floor library and insert a 'real' version everywhere it was used.

The input->output equation could potentially be used as a performance boost for normal subfloors as well, although it might not work with the matrix/simplex solver.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant