-
Notifications
You must be signed in to change notification settings - Fork 3
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
Specification for templates #22
Comments
Add more informations. |
@SGOrava what I'm getting from this is templates are a way to save certain aspects of a map to save repeating yourself. In his example he uses stairs. Say you build stairs in blender and don't want to have to repeat making the stairs. You save the stairs as a template and then you can import the template so you can reuse it. I think it would be good to have this in the specification as well. |
@Geertiebear actually this function is partially there, you can import map without erasing the current scene, what is missing are only some tweaks as:
PS: stair is the worst example, there are very good stairs generators |
@Geertiebear @SGOrava I think adding the full geometry instead of a reference should be implemented first and is simpler to implement, too since it does not require changes to the client. |
I like the idea of import, but it we can first experiment with the feature and add full geometry first. If it works well we can move onto import. |
@Geertiebear Please be more precise. What do you mean by full geometry ? Is it like support for rotation, position and scale or is there something else what i am missing ? |
For each import we define certain objects. For example with stairs there are a bunch of rectangles. That collection of rectangles is the "full geometry" is what I understand from what @hhirsch said. Hope that clarifies ^^ |
Templates are a way to save an xml for later import to our maps. This is for recurring geometry like e.g. stairs.
Use case:
Design the stairs once in blender
Save the template as a map file in the template directory
While working on a map pull up the templates and insert your stairs as often as you want to
Create spec
Create issues according to spec
If a reference or the full geometry is added when inserting a template is to be decided (both have a use case and maybe both are needed).
In blender it will be beneficial to have all parts of a template grouped.
I think adding the full geometry instead of a reference should be implemented first and is simpler to implement, too since it does not require changes to the client.
The text was updated successfully, but these errors were encountered: