It'd save a lot of time and also make it easier maintaining a large number of components & their properties if it were possible to apply templates that are updatable from a single location.
I do think there's room for improvement on Articy:Draft, but it's a good example of this sort of setup. Using that sort of template system along with Arcweave's UI/UX design would be great.
Templating the components is a very powerful feature that we will definitely address, since it could prove invaluable when the component database gets big enough and complicated.
Arcweave Development Team
Ok cool, yeah I'm only using Arcweave right now for the basics because if I added all the data I have already, it'd become way too much to handle in Arcweave.
I would love to see this feature as well. One thing that would be a nice extra for that would be to have predefined filed types like „strength“ can only be integernumbers, „class“ can only be chosen between „orc“ „elve“ and „human“ and stuff like that.
I think with the current state, these predefined fields do not make a lot of scence (since you only add them once), but later on i would really love something like that.
Yes, attribute types like string, integer, float for attribute values could prove useful. Moreover, predefined attributes like Strength, Health, Stamina e.t.c. would also be a nice-to-have feature. We are thinking of incorporating these additions into the template mechanism we are designing. My thought is that the default type should probably be "string" in case someone does not need to go into the details of adding types for component attributes.
Panos - Arcweave Development Team