Le 01/09/2013 11:40, Jack a écrit :
Le 30/08/2013 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@rybn.org mailto:jack@rybn.org>
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@iem.at mailto:GEM-dev@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
So I create an account on Github where I fork Gem. I don't know if i do it according to the rules. Tell me if I have to change something. git://github.com/Jackovic/Gem.git I put a 'glsl_abstractions' directory in the 'help' and don't know if it is the best place for that.
i think there is 2 options : -consider them as Gem object : putting them on the abstraction folder, making specific help file and changing makefile in order to install them pro : would be like any other Gem object con : need to be maintain
-create a examples/14.pix_glsl folder and put everything inside pro : less work con : harder to find
i'll vote for option 2 : there is already directory 11.obj_exporter and 12.multi_screen_projection that are in the same situation.
cheers c
++
Jack
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev