florianfesti
Home Design
I was working on creating a home design modeling library, when I ran across this library which I think looks perfect for doing the backend of this project.
My basic idea is to take an ascii text file (see floor1.txt of the layout of a house, and from that plus a table file defining height of walls and windows to generate a SVG file for glowforge to cut out the wall to create a miniature model of the home.
I have forked this repo and I am beginning to refactor my code to fit within this repo's design. Any suggestions would be appreciated.
see https://github.com/SeabornGames/boxes/blob/model_home/boxes/layouts/model_house_library/README.rst for details.
Questions:
- Would it be possible to have an argument of a path to a file within the web UI?
- Is there a reason not to use python virtual environment and to install the require python modules within the virtual environment as well as use the standard ``entry_points`? Would you like me to make a PR for this?
- I do see you need to tell inkscape which version of python to use.
- If you named renamed your package (festi_boxes) you could just include it in pypy? Would you like me to help with this?
- My understanding is that boxes represent one drawing, but I think it probable that I will need to have multiple SVG, because there are so many walls in a home design, and I might want the walls to be large (relative to the glowforge). Are there algorithms for breaking up the walls to different files?
This are a lot of questions, let me see if I can come up with answers:
- Sure. That just need a class similar to ArgparseEdgeType or BoolArg. It will probably be even more involved as it needs to get the file data from different source depending whether it is used on the cli or in the web instance.
- This is basically just because I am much too old school. PRs are welcome. Note that there are some docker file that use the same patterns (In case you want to fix them, too. Switching one thing after the other is also fine).
- Including it in pypy sounds interesting. I am not too keen on
festi_boxes. I need to look into this to find a good name (good names are hard) - Currently there is only one output file. Adding support for multiple files (e.g. basename.svg, basename-part2.svg, ...) should not be too hard. But this will need manual work from the generator. Currently the whole placing of arts is done manually - and typically not very smart. This is kinda on purpose as things change with different sizes and people need to adjust for the size of the material used anyway. Breaking up single parts is a whole topic of its own. Not sure if we want to get into this right now.
You may want to consider placing measurements into your file formats. While I understand you want to have your ASCII plans look to scale, they are hard to edit. Doesn't have to be as ugly as TrayLayout (which is kinda similar). You could put the sizes into the walls.
- Ok I will need help with that, but probably after my first real PR
- Ok I might do this someday, but not sure when.
- I can do the pypy part, but no rush from my side
- This assumes though I could get it all done on one sheet which I am pretty sure is not the case. That being said I was planning on having a --room-filter because I didn't want to have to cut out the whole thing again just because I changed two rooms, so I guess that can work for now.
- so I need to have a 2:1 ratio for characters for it to look right, but I will consider this in later versions.
Are you okay with this concept of layout?
https://github.com/SeabornGames/boxes/tree/model_home