The design state is moved into the wiki. It can be discussed here, but the design state will stay in the wiki. Do you think the discussion should be moved into the wiki discussion page as well?
I use the inkscape:groupmode="inkcards:card", is it something I can do for an inkscape extension or it's reserved for internal use ?
The inkscape:groupmode="inkcards:cardFramingSize" 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 inkscape:groupmode get back to inkcards:cardFramingSize 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 <use> it, it does not <use> all the sublayers. Perhaps inkscape could have an optional mode to separate the content from layers in a special layer with inkscape:groupmode="layer-content"?
More will be added ...
@doctormo, you can see why I need my own namespace (inkcards). While working on the namespace I thought of this enhanced way of managing the cards, thought I can get without managing my own namespace, but writing this, It evolved a lot and see that I still need it.
Hi, I finally found out the discussion I started for my extension (inkcards) in 0.97. I got into something else, and am now back into it. I tried other places to talk about it, but this seems the place to keep track and not get lost. The current version is available on github. The idea comes from this thread on BoardGameGeek, hence the NameSpace URL. I got a feedback I should use a URL of which I have a control on ?
The idea is to draw game cards by using and reusing layers in a card sized document. Then tile the cards for printing in a second document. You can see the usual technique/way to tile the cards in this (a little long) video.
The extension works by managing a deck of cards (a card is a list of layers). So that if you make changes to one layer, they will be applied automatically to all the cards using it. The smiley example (in the code) is a good example of reusing layers in multiple cards. You then use a second extension to tile them, separating the cards in pages (layer). You would use a third extension to export all pages to PDF and join them with pdfunite from the poppler project, but that is not really available for windows.
Here are my thoughts on the direction the discussion should take:
It might not be a good thing to add new elements in a custom (inkcards) namespace? To remove this thing, we could use the <use> element. The problem is that it would be hard for a user to manage 2 views of the same layers, where one is not editable.
The tiling and export to PDF could be done in one step, but this does not let the user adjust things before printing, like if the cut marks are hard to see.
Plus, I want to use the tile feature for origami instructions: Resize the cards (instruction steps) individually and remove the cut/fold marks.
pdfunite (the tool to join the PDF) is a freedesktop project, so is not really available for windows. what should we do ?
Depending on a third party format (PDF) is no such good thing, but adding to a layer <g inkscape:groupmode=layer inkscape:page=true> the information that this layer is a page, and the document is a multipage document would be a great way to bring the equivalent of a PDF to SVG. The tools to handle such documents would be much easier to build/maintain.
Creating New Extensions Inkcards
Inkscape.org
The design state is moved into the wiki. It can be discussed here, but the design state will stay in the wiki. Do you think the discussion should be moved into the wiki discussion page as well?
Questions:
inkscape:groupmode="inkcards:card", is it something I can do for an inkscape extension or it's reserved for internal use ?inkscape:groupmode="inkcards:cardFramingSize" 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 tolayerfor the resizing and the next time he uses any inkcards extension hisinkscape:groupmodeget back toinkcards:cardFramingSizeso 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.<use>it, it does not<use>all the sublayers. Perhaps inkscape could have an optional mode to separate the content from layers in a special layer withinkscape:groupmode="layer-content"?@doctormo, you can see why I need my own namespace (
inkcards). While working on the namespace I thought of this enhanced way of managing the cards, thought I can get without managing my own namespace, but writing this, It evolved a lot and see that I still need it.Hi, I finally found out the discussion I started for my extension (inkcards) in 0.97. I got into something else, and am now back into it. I tried other places to talk about it, but this seems the place to keep track and not get lost. The current version is available on github. The idea comes from this thread on BoardGameGeek, hence the NameSpace URL. I got a feedback I should use a URL of which I have a control on ?
The idea is to draw game cards by using and reusing layers in a card sized document. Then tile the cards for printing in a second document. You can see the usual technique/way to tile the cards in this (a little long) video.
The extension works by managing a deck of cards (a card is a list of layers). So that if you make changes to one layer, they will be applied automatically to all the cards using it. The smiley example (in the code) is a good example of reusing layers in multiple cards. You then use a second extension to tile them, separating the cards in pages (layer). You would use a third extension to export all pages to PDF and join them with pdfunite from the poppler project, but that is not really available for windows.
Here are my thoughts on the direction the discussion should take:
<g inkscape:groupmode=layer inkscape:page=true>the information that this layer is a page, and the document is a multipage document would be a great way to bring the equivalent of a PDF to SVG. The tools to handle such documents would be much easier to build/maintain.