patriciogonzalezvivo/PixelSpiritDeck

Structure of graphical dependencies vs. Symbolic relationships in the tarot

Opened this issue · 4 comments

I like the overall 'cyber' redefinition of the cards, and the design.

Would you please speak a bit to the major arcana not being in the numerical order of the tarot?

Even if this is just 'in code' or 'on disk' I think that it is a bit of a violation of the principle. A renovation should be a further revelation of light, not shards of psyche.

The mathematical dependencies between the major arcana does not seem similar to the actual relationships in the tarot, astrological nor within the classic tree nor the cubic/fractal tree?

Had you put thought toward making the geometric relationships (card art) more-directly bear upon the mathematical structure of the symbolic relationships? What challenges were there? Have you aimed for a more-subtle order of some form?


Thanks. I hope that text does not lose the sincerity of my consideration

Hi! First of all, thanks for this questions. Tarot and astrology studies are both very close to my heart, so I appreciate your time thinking on them.

“Would you please speak a bit to the major arcana not being in the numerical order of the tarot?”

I believe deeply in the original order of the mayor arcana. Preserving their natural order at the same time I can present a progresion of the code so can be use as an educational tool, was one of the biggest challenges. Probably there is not a unique or perfect approach to do that, but I end up settling on leaving the origins mayor arcana number in the front of the card (only mayor arcana have a big roman number at the front top of the card), while the number of the back (small and in the coroners) is simply the progresion of the function and techniques to render the always more complex shapes on the front. After all the cards are intended to be a library and an educational tool as much as a medium for instrospection.

In the same way, the dependencies in the back don’t relate to the symbolic universe of the front but to code dependencies on the back. The dependencies resolve the problem of not needing to duplicate code, allowing tu build up a library of functions.

On other words everything on the front of the card respond to a symbolic universe while the back is strictly technical. This consesion allow the ambitious endeavor of finding a new perspective on an old symbolic struct shaped over centuries.

Hope this answers help to illuminate more the project. I personally like the fact that we can be having this conversation over github/issues, fulfills some personal goals as an artist.

Thanks again and let’s keep talking about it.