Inkcards - Revision history

KBenoit: /* Summary of an inkcards SVG */

2020-04-10T19:04:47Z

Summary of an inkcards SVG

← Older revision		Revision as of 19:04, 10 April 2020
Line 13:		Line 13:

	==Summary of an inkcards SVG==		==Summary of an inkcards SVG==
	~~Written~~ as ideas ~~are coming to~~ my mind, so ~~will be~~ useful documentation:		I wrote it as ideas where popping in my mind, so is useful documentation:

	<source lang=xml>		<source lang=xml>

KBenoit: Define sections

2020-04-10T19:02:01Z

Define sections

← Older revision		Revision as of 19:02, 10 April 2020
Line 1:		Line 1:
			=Basic description=
	Inkcards is an extension to create cards using layers, I say cards, but could be any tiles, like tokens, origami instructions, etc. The basic idea is you activate only the layers used by a specific card and save the information of which layers are visible for this card. By reusing the layers, it's much easier to customize your deck than copy/paste elements. With it, you can make modifications to the list/deck of cards by adding/removing cards, activating/deactivating the layers to show a specific card, or reordering the card list. ''It could be used to create video games?'', but the main idea is that once your cards are designed, you can tile them on a different document size in order to print them, read this [https://boardgamegeek.com/thread/490643/making-cards-youll-never-use-your-old-method-again thread] to know what I'm talking about. Rachel summarize her learning from the thread in a [https://www.youtube.com/watch?v=K5y3xeMN6Rs&feature=youtu.be video] which was also greatly inspired by this [https://www.youtube.com/watch?v=n_8q4V3TAzc video] from the Dinning Table (probably more pertinent).		Inkcards is an extension to create cards using layers, I say cards, but could be any tiles, like tokens, origami instructions, etc. The basic idea is you activate only the layers used by a specific card and save the information of which layers are visible for this card. By reusing the layers, it's much easier to customize your deck than copy/paste elements. With it, you can make modifications to the list/deck of cards by adding/removing cards, activating/deactivating the layers to show a specific card, or reordering the card list. ''It could be used to create video games?'', but the main idea is that once your cards are designed, you can tile them on a different document size in order to print them, read this [https://boardgamegeek.com/thread/490643/making-cards-youll-never-use-your-old-method-again thread] to know what I'm talking about. Rachel summarize her learning from the thread in a [https://www.youtube.com/watch?v=K5y3xeMN6Rs&feature=youtu.be video] which was also greatly inspired by this [https://www.youtube.com/watch?v=n_8q4V3TAzc video] from the Dinning Table (probably more pertinent).

			=Design evolution=
	For this my design is being updated for 1.0. I think of placing the cards in a card sized <code>rect</code> in which you draw the cards. From an extension, you manage the deck content by adding/removing cards which are using the visible layers perhaps under a "<code>cards</code>" named layer? Adding a card imply adding a <code><g></code> of multiple <code><use></code> of all layers used by this card in <code>defs</code>. Then adding another <code><use></code> of the <code><g></code> (card) entry just made in <code><defs></code>, inside the document's <code>viewBox</code>, more than one <code><use></code> if your deck has more than one instance of a card. This <code><use></code> of the card would be in a "<code>page X</code>" layer (where X is the floor of the card number divided by the number of card that fit in a page).		For this my design is being updated for 1.0. I think of placing the cards in a card sized <code>rect</code> in which you draw the cards. From an extension, you manage the deck content by adding/removing cards which are using the visible layers perhaps under a "<code>cards</code>" named layer? Adding a card imply adding a <code><g></code> of multiple <code><use></code> of all layers used by this card in <code>defs</code>. Then adding another <code><use></code> of the <code><g></code> (card) entry just made in <code><defs></code>, inside the document's <code>viewBox</code>, more than one <code><use></code> if your deck has more than one instance of a card. This <code><use></code> of the card would be in a "<code>page X</code>" layer (where X is the floor of the card number divided by the number of card that fit in a page).

	Extensions needed:		==Extensions needed==

	* For this I think I should use an extension to initialize an Inkcards document by adding a <code>"Inkcards:cards"</code> named <code>rect</code> outside the <code>viewBox</code>. That <code>rect</code> would be the size of a card. Knowing the card size, in this extension I could reserve the place to tile the cards?		* For this I think I should use an extension to initialize an Inkcards document by adding a <code>"Inkcards:cards"</code> named <code>rect</code> outside the <code>viewBox</code>. That <code>rect</code> would be the size of a card. Knowing the card size, in this extension I could reserve the place to tile the cards?
Line 10:		Line 12:
	* An extension should save one SVG for every page layers and convert that into a single PDF using image magick convert.		* An extension should save one SVG for every page layers and convert that into a single PDF using image magick convert.

	~~Here's a summary~~ of an inkcards SVG ~~... written~~ as ideas are coming to my mind, so will be useful documentation:		==Summary of an inkcards SVG==
			Written as ideas are coming to my mind, so will be useful documentation:

	<source lang=xml>		<source lang=xml>
	<svg viewBox="0 0 279.4 215.9" width="11in" height="8.5in">		<svg viewBox="0 0 279.4 215.9" width="11in" height="8.5in">
Line 57:		Line 61:
	</svg>		</svg>
	</source>		</source>
	Questions:
			==Questions==

	* I use the <code>inkscape:groupmode="inkcards:card"</code>, is it something I can do for an inkscape extension or it's reserved for internal use ?		* I use the <code>inkscape:groupmode="inkcards:card"</code>, is it something I can do for an inkscape extension or it's reserved for internal use ?
Line 64:		Line 69:
	* More will be added ...		* More will be added ...

	~~Example~~ of what [https://media.inkscape.org/media/resources/file/smiley-new2.svg inkcards could generate].		==Exemple==
			You can see an svg example of what [https://media.inkscape.org/media/resources/file/smiley-new2.svg inkcards could generate].

KBenoit: Switch inkcards development description / perhaps discussion to the wiki instead of the forum.

2020-04-10T16:38:42Z

Switch inkcards development description / perhaps discussion to the wiki instead of the forum.

New page

Inkcards is an extension to create cards using layers, I say cards, but could be any tiles, like tokens, origami instructions, etc. The basic idea is you activate only the layers used by a specific card and save the information of which layers are visible for this card. By reusing the layers, it's much easier to customize your deck than copy/paste elements. With it, you can make modifications to the list/deck of cards by adding/removing cards, activating/deactivating the layers to show a specific card, or reordering the card list. ''It could be used to create video games?'', but the main idea is that once your cards are designed, you can tile them on a different document size in order to print them, read this [https://boardgamegeek.com/thread/490643/making-cards-youll-never-use-your-old-method-again thread] to know what I'm talking about. Rachel summarize her learning from the thread in a [https://www.youtube.com/watch?v=K5y3xeMN6Rs&feature=youtu.be video] which was also greatly inspired by this [https://www.youtube.com/watch?v=n_8q4V3TAzc video] from the Dinning Table (probably more pertinent).

For this my design is being updated for 1.0. I think of placing the cards in a card sized <code>rect</code> in which you draw the cards. From an extension, you manage the deck content by adding/removing cards which are using the visible layers perhaps under a "<code>cards</code>" named layer? Adding a card imply adding a <code><g></code> of multiple <code><use></code> of all layers used by this card in <code>defs</code>. Then adding another <code><use></code> of the <code><g></code> (card) entry just made in <code><defs></code>, inside the document's <code>viewBox</code>, more than one <code><use></code> if your deck has more than one instance of a card. This <code><use></code> of the card would be in a "<code>page X</code>" layer (where X is the floor of the card number divided by the number of card that fit in a page).

Extensions needed:

* For this I think I should use an extension to initialize an Inkcards document by adding a <code>"Inkcards:cards"</code> named <code>rect</code> outside the <code>viewBox</code>. That <code>rect</code> would be the size of a card. Knowing the card size, in this extension I could reserve the place to tile the cards?
* If the user adjust the size of the card <code>rect</code>, he could use an extension (a second <code>inx</code>) to recalculate the tiles position in the document. Perhaps instead of a <code>rect</code>, it could be a <code>circle</code> and the extension could adjust the tiling to imbricate them with an optimize option, else it would align them.
* One extension to be able to move the card document (set <code>inkscape:groupmode="layer"</code>) and <code>sodipodi:insensitive="false"</code>. It would automatically set it back on the next use of the extension.
* An extension should save one SVG for every page layers and convert that into a single PDF using image magick convert.

Here's a summary of an inkcards SVG ... written as ideas are coming to my mind, so will be useful documentation:
<source lang=xml>
<svg viewBox="0 0 279.4 215.9" width="11in" height="8.5in">
<defs>
<g id="card1" inkscape:groupmode="inkcards:card" inkcards:name="fireball" inkcards:nbCopy="2">
<use xlink:href="#layer1"/>
<use xlink:href="#layer2"/>
<use xlink:href="#layer3"/>
</g>
<g id="card2" inkscape:groupmode="inkcards:card" inkcards:name="dragon">
<use xlink:href="#layer1"/>

</g>

</defs>

<g inkscape:groupmode="layer" inkscape:label="Base card layers">
<g inkscape:groupmode="inkcards:cardFramingSize" sodipodi:insensitive="true">
<rect id="inkcards:cards" x="-100" y="0" width="80" height="80"/>
</g>

<g id="layer1" inkscape:groupmode="layer" inkscape:label="background1">

</g>
<g id="layer2" inkscape:groupmode="layer" inkscape:label="spell">

</g>
<g id="layer3" inkscape:groupmode="layer" inkscape:label="fireball">

</g>

</g>

<g inkscape:groupmode="layer" inkscape:label="pages">
<g inkscape:groupmode="layer" inkscape:label="page1">
<use xlink:href="#card1" x="20" y="20"/>
<use xlink:href="#card1" x="120" y="20"/>
<use xlink:href="#card2" x="220" y="20"/>

</g>
<g inkscape:groupmode="layer" inkscape:label="page2">

</g>

</g>
</svg>
</source>
Questions:

* I use the <code>inkscape:groupmode="inkcards:card"</code>, is it something I can do for an inkscape extension or it's reserved for internal use ?
* The <code>inkscape:groupmode="inkcards:cardFramingSize"</code> is a way I think of having sort a dual document, the user could manage/resize it with an extension, perhaps be able to set it to layer for the resizing and the next time he uses any inkcards extension his <code>inkscape:groupmode</code> get back to <code>inkcards:cardFramingSize</code> so he could not play with it like he want, as it would move the cards. I also thought of using a group so that the cards layers are at origin, just moved by an underlying group.
* Is there a way to add a layer content, but not for other (sub)layers ? The problem is that layers are a tree and if i add a branch, all sub-branches are added. One way I thought to get around this is for a parent layer, have the content in a content sublayer which as all, but the sublayers, so that if I <code><use></code> it, it does not <code><use></code> all the sublayers. Perhaps inkscape could have an optional mode to separate the content from layers in a special layer with <code>inkscape:groupmode="layer-content"</code>?
* More will be added ...

Example of what [https://media.inkscape.org/media/resources/file/smiley-new2.svg inkcards could generate].