support for texture arrays, MRT, integer textures, image load/store? about shader-toy HOT 10 CLOSED

On Fri, Jun 28, 2019 at 7:05 AM Adam Stevenson ***@***.***> wrote: @bernief1 <https://github.com/bernief1> Is your project public and/or open-source? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#62?email_source=notifications&email_token=AIAYGYJZPJS72YPW76F4FIDP4YLBNA5CNFSM4H37X7IKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY2FLXQ#issuecomment-506746334>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIAYGYKNPGZ2D44RRWIK4PDP4YLBNANCNFSM4H37X7IA> .

On Sat, Jun 29, 2019 at 4:47 AM Malacath-92 ***@***.***> wrote: You're missing some libraries in your repo, so I can't actually build it without searching for the right versions myself. Regardless of that, it sounds like you have a set of really nice features. However I don't see how the projects can benefit from each other. The fact alone that one project is written in TypeScript/HTML and the other is written in C++ makes most efforts to port features very non-trivial. On top of that one works based on WebGL, the other on the full OpenGL feature set. I don't say this to be discouraging or mean, I just honestly think that the two projects live in very different domains, where they each are completely valid and valuable solutions. When you speak of unifying syntax, of course this is a different question and could bring value to users who might not always be able to use one or the other solution. Thus having a standalone desktop version of shader-toy that obeys the same syntax as the VSC integrated version (and partially the online version) could help a lot. On a side note though, we have many active users on this extension, thus radically changing our syntax would be dangerous. For now, if you are interested in growing your project and making it inviting to contributors, I would suggest you to clean up the repo a bit, introduce a build-system, make the code portable (if it isn't already), eventually introduce CI and testing. I'd be happy to spend some time to help you with that, because I think having a desktop version of shadertoy is an amazing prospect. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#62?email_source=notifications&email_token=AIAYGYITANSIWEGGIGAPI7DP45DTZA5CNFSM4H37X7IKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY3XMHA#issuecomment-506951196>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIAYGYIPTOBGHBNZZUY5AUTP45DTZANCNFSM4H37X7IA> .

Sure, I'd be interested in help cleaning up the repo so that it's more usable. I have little experience sharing code outside of the game projects I've worked on. First off - which libraries am I missing? Besides OpenGL, the project depends on FreeImage, GLUT (freeglut), and GLEW. All of these should be in the *common\GraphicsTools\external\ *directory (which should be parallel to the *shader_toy\* directory). The settings in the vcxproj specify additional include and library directory "..\common\;" so the #includes and #pragma comment(lib,..)'s can find the appropriate files. As I mentioned, you need to copy the freeglut dll from *common\GraphicsTools\external\glut\freeglut\bin\x64\freeglut.dll* to somewhere in your PATH such as C:\Windows - or I suppose you could copy it to *shader_toy\* directly .. in my local setup I have a common directory and then many separate projects which use freeglut so I didn't want to have to duplicate the dll all over the place. On Sat, Jun 29, 2019 at 4:47 AM Malacath-92 ***@***.***> wrote: > You're missing some libraries in your repo, so I can't actually build it > without searching for the right versions myself. > > Regardless of that, it sounds like you have a set of really nice > features. However I don't see how the projects can benefit from each other. > The fact alone that one project is written in TypeScript/HTML and the other > is written in C++ makes most efforts to port features very non-trivial. On > top of that one works based on WebGL, the other on the full OpenGL feature > set. > > I don't say this to be discouraging or mean, I just honestly think that > the two projects live in very different domains, where they each are > completely valid and valuable solutions. > > When you speak of unifying syntax, of course this is a different question > and could bring value to users who might not always be able to use one or > the other solution. Thus having a standalone desktop version of shader-toy > that obeys the same syntax as the VSC integrated version (and partially the > online version) could help a lot. On a side note though, we have many > active users on this extension, thus radically changing our syntax would be > dangerous. > > For now, if you are interested in growing your project and making it > inviting to contributors, I would suggest you to clean up the repo a bit, > introduce a build-system, make the code portable (if it isn't already), > eventually introduce CI and testing. I'd be happy to spend some time to > help you with that, because I think having a desktop version of shadertoy > is an amazing prospect. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#62?email_source=notifications&email_token=AIAYGYITANSIWEGGIGAPI7DP45DTZA5CNFSM4H37X7IKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY3XMHA#issuecomment-506951196>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AIAYGYIPTOBGHBNZZUY5AUTP45DTZANCNFSM4H37X7IA> > . >

On Tue, Jul 2, 2019 at 11:35 AM Malacath-92 ***@***.***> wrote: In particular I fail linking against the static libraries for FreeImage 'GraphicsTools/external/FreeImage/x64/FreeImage2017Lib.lib' — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#62?email_source=notifications&email_token=AIAYGYOWHEX5DVPVBVYVIUDP5ONXHA5CNFSM4H37X7IKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZCFVUA#issuecomment-507796176>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIAYGYPXN4WXGMQNPWQ6B3DP5ONXHANCNFSM4H37X7IA> .

On Tue, Jul 2, 2019 at 10:55 PM Malacath-92 ***@***.***> wrote: No, there is no static library for FreeImage in your repo. It should be in this <https://github.com/bernief1/common/tree/master/GraphicsTools/external/FreeImage> folder — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#62?email_source=notifications&email_token=AIAYGYPVUJCKGDP4FA5D4YDP5Q5NPA5CNFSM4H37X7IKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZDLEQQ#issuecomment-507949634>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIAYGYLM4N2WMOW6VPABW2TP5Q5NPANCNFSM4H37X7IA> .