Feature request: reusable icons / symbols template system

[arturskro]

A card defines a card template; as a proposed extension, an icon would work in the same way, defining templates for symbols that can be used on cards and stored in a separate directory. A single CSV datasheet would be used as a shared data source for cards and icons, which would require new Handlebars helpers to support cross-referencing between them.

A fully native, atomic icon solution would enable a better workflow. Currently, managing parameterized icons is complicated and requires excessive CSS, wrappers, and additional markup.

[hristoiankov]

The way that I think of icons is that they are static images that represent a single resource (with multiple together or a different image to represent a larger quantity of that resource). Icons can be tiny and fit inline with text. If you have a finite number of quantities you want to represent (Ex. 1 -3), you can generate a static image for each one of those and reuse them across templates.

badges on the other hand to me are like icons, but with a larger image (large enough to also cleanly fit text) and a dynamic value (coming in from the card data) in the foreground. These are usually tied to the template of the card and sit in a specific position on the template.

I think I would need to know a bit more details about your use-case to see if I can generalize a solution that will work for others.

Questions:

• Where on your template do these icons/badges sit (in-line w/ text, specific position)?
• Are they reused across different templates?
• Can they be rasterized into static images instead (if they're reused in different places)?
• How many different combinations of unique icon + value do you have?
• How are you defining or how would you like to be able to define the data for these icons/badges in your card data table?

[arturskro]

OK, Examples:

So... currently, preparing this type of icons in Cider is quite complicated (css, wrappers etc.). You can prepare attack1, attack2, attack3 graphics but this is not a good solution. It would be better to define icon in the same way as card and use it in the card template.