[GEM-dev] pix_write relative path - osx

[IOhannes m zmoelnig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

i agree, but,...

On 2011-12-01 10:17, cyrille henry wrote:
> 
>>  And things like [pix_multiblob] already in effect depend on
>> iemmatrix, since it was designed to work with that library.
> pix_multiblob does not depend on iemmatrix.
> the help file do work perfectly without iemmatrix.

[pix_multiblob] has indeed no dependency on iemmatrix, but outputs data
in a form that is natural to iemmatrix and less natural to the rest of Pd.
in retrospect i think it was a bad idea to output the data in
iemmatrix-like messages, and actually would like to change that
(allowing for a flag to indicate whether one would like iemmatrix
messages or ordinary lists)

however, to be fair, there is one abstraction that ships with Gem that
depends on iemmatrix, and this is [pix_blobtracker].
btw, the help-patch pix_blocktracker-help.pd does not depend on iemmatrix.


fgmasdr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7XWC4ACgkQkX2Xpv6ydvSOBgCg2RyZerhAvqla+M5V8E6+noDb
SM0AoNUyCkMa/3xVsG2TwNZxTExjYJG5
=LC0M
-----END PGP SIGNATURE-----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3636 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20111201/ee03e3d2/attachment-0001.bin>