[GEM-dev] help with glsl abstractions

Nicolas Montgermont nicolas_montgermont at yahoo.fr
Fri Aug 30 10:48:39 CEST 2013


Hello jack,

yes it can be very useful and powerful.
On the abstraction you send I have differents remarks:
- it is not compatible with [pix_chroma_key] and I think this is very 
important. The main usage of that kind of abstractions is to have an 
easy and faster replacement for existing objects.
- I see no reasons to have a default size to 256x256, or even to have a 
size as an argument, texture size of the first texture will be really 
easier as default, and dimen can be used to change that.
- I think it's good if the provided example of the usage is easily 
transposable, beginners tends to copy directly from the help patch. I 
think here for example the main gemhead could be to default and the 
gemhead before the gemframebuffer to 49
- for the help line : "inlet 1 all messages accepted by gemframebuffer", 
I think it's good to have a subpatch [pd framebuffer_messages] with a 
listing that can be tested. You may then copy it inside the other help 
patchs.
- maybe the object can print a specific error message when it doesn't 
know the input:
glsl_chroma_key : no method for 'toto'
instead of:
gemframebuffer: no method for 'toto'

best,
n


Le 30/08/13 01:51, Antoine Villeret a écrit :
> good job !
> could be very useful !
> I have some too (to replace pix_movement for example)
> what is your working repo ?
>
> +
> a
>
> --
> do it yourself
> http://antoine.villeret.free.fr
>
>
> 2013/8/28 Jack <jack at rybn.org <mailto:jack at rybn.org>>
>
>
>     -----BEGIN PGP SIGNED MESSAGE-----
>     Hash: SHA1
>
>     Le 26/07/2013 14:03, IOhannes m zmölnig a écrit :
>     > On 07/26/13 11:44, Jack wrote:
>     >> Hello,
>     >>
>     >> I would like to create GLSL abstractions in the help directory,
>     which
>     >> would replace pix_ objects when possible. The name would start with
>     >> glsl_ instead of pix_.
>     >
>     > sound good.
>     >
>     >> Is there any objection against this ?
>     >
>     > no.
>     >
>     >> If not, i would like to have acces to the git repository with write
>     >> access. Is that possible ?
>     >
>     > wouldn't it be easier if you just forked the repository, and made a
>     > pull-request via github?
>     > i really love the decentralized aspect of git.
>     >
>     >
>     > mgfd.gasda
>     > IOhannes
>     >
>     >
>     >
>     >
>     > _______________________________________________
>     > GEM-dev mailing list
>     > GEM-dev at iem.at <mailto:GEM-dev at iem.at>
>     > http://lists.puredata.info/listinfo/gem-dev
>
>
>     I started to make seven abstractions glsl_*.
>     I would like to be sure, with the example attached, if i am on the
>     right path.
>     Comments are welcome.
>     ++
>
>     Jack
>
>
>     -----BEGIN PGP SIGNATURE-----
>     Version: GnuPG v1.4.12 (GNU/Linux)
>     Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
>     iQEcBAEBAgAGBQJSHfd8AAoJEOuluecjw8GUNhIH/1pvebiP2CRZNArDCS3anJO0
>     9U34Wc2ENOsEGyivRF/aAIT6RAoJmZgAor8xj7Ny1hTk7cKlnRT+yEh/5KBaUg0g
>     gPd6ZjQygqinkg6kPXZ7AsgLpv6BDn33vMnQbW/d1aMmTiC3KRNtwSc9T3awoPNq
>     iMW+yV+Ir+WjXLO8hsSV96rW5hEUGioN3iRjbat6++mw4hqC9T6yCQngWSPR7+xB
>     46+3VXrXpjHiZblUxYYWHvAypXlOqvYfwd4+92mFojardK6imfYsw3ZyJ45Bf0m2
>     +o68hovxFYP961YwPtvF729ZyRGYryQGnLDXTc4nDDaBdOmW/zCatpLHBWmu+PE=
>     =E+az
>     -----END PGP SIGNATURE-----
>
>
>     _______________________________________________
>     GEM-dev mailing list
>     GEM-dev at iem.at <mailto:GEM-dev at iem.at>
>     http://lists.puredata.info/listinfo/gem-dev
>
>
>
>
> _______________________________________________
> GEM-dev mailing list
> GEM-dev at iem.at
> http://lists.puredata.info/listinfo/gem-dev

-- 
http://www.nimon.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20130830/c56e58bf/attachment.htm>


More information about the GEM-dev mailing list