Jack.Lion

I feel that we could improve jitter by making it even easier to include external libraries and all their functions such as the Lygia library.

A couple of months ago I posted in the discord about porting a repository of glsl functions from the Lygia library into max jitter. Here is a link to that post for context, it includes a link to the lygia library. https://discord.com/channels/289378508247924738/289379337528934401/1034508710015422514

Some basic examples worked but the whole thing soon got a little complicated. @robtherich stated something to the effect of "there's a reasonable feature request here in supporting glsl #include syntax jxs shaders, feel free to drop a note to support" and while I don't fully understand the reason some functions work and others do not I get the sense that something could be done to make this whole process easier. It goes deeper too. I consulted chat GPT for help just to see if there may be another solution and it made an interesting attempt at helping me solve the problem. At the very least, it provides some context on the error codes we got while hacking at it and the structure of the code we collaborated on. When it realized some of these limitations it provided some more complex solutions but I declined to test further. I was satisfied testing the limitations of using this external library in max. I will attach that chat log in a .txt in case it is useful. But all of this is to basically elaborate on why this feature request is important. Being able to use something like the lygia library directly without modifying it would be a game changer in using the slab object and I just felt like drawing some attention to the subject.

Using lygia with jitglslab ChatGPT log.txt

A couple of months ago I posted in the discord about porting a repository of glsl functions from the Lygia library into max jitter. Here is a link to that post for context, it includes a link to the lygia library. https://discord.com/channels/289378508247924738/289379337528934401/1034508710015422514
Some basic examples worked but the whole thing soon got a little complicated. @robtherich stated something to the effect of "there's a reasonable feature request here in supporting glsl #include syntax jxs shaders, feel free to drop a note to support" and while I don't fully understand the reason some functions work and others do not I get the sense that something could be done to make this whole process easier. It goes deeper too. I consulted chat GPT for help just to see if there may be another solution and it made an interesting attempt at helping me solve the problem. At the very least, it provides some context on the error codes we got while hacking at it and the structure of the code we collaborated on. When it realized some of these limitations it provided some more complex solutions but I declined to test further. I was satisfied testing the limitations of using this external library in max. I will attach that chat log in a .txt in case it is useful. But all of this is to basically elaborate on why this feature request is important. Being able to use something like the lygia library directly without modifying it would be a game changer in using the slab object and I just felt like drawing some attention to the subject. 

I feel that we could improve jitter by making it even easier to include external libraries and all their functions such as the Lygia ... 

Using the Lygia library in jit.gl.slab