Vervette Fluid Sandbox...

[Taron]

...just imagine what he might have meant by "cursor brush"! I'm sure you will come to the right conclusion!

The previous "orange" was made with only a mega Brush circular!

[Taron]

Oh boy, I figured out how I can get my 16bit array from GL, but now I have to figure out how I can export the data, possibly zip it, but it's incredibly tedious for me to find out what I need to do. I did find a number of zip libraries, but virtually all of them only seem to handle strings. Kind of exhausting. I wished, I'd know someone, who truly knows javascript for some help. ...but on goes the quest!

Anyway, it's all very promising already, so that's really cool. At least I get the data itself, allowing session based storing in memory.

Learning all these things is really like pulling teeth more often than not.

[Taron]

...not sure, if this thread should really become a dev-log, but I'm excited enough to report that I now can save 16bit textures and load them back in, finally making it possible to continue a paint project at some other time in full quality. I still have to figure out how to compress and decompress, which seems trivial, but...eh... can't wait for the day when I think so, too. For now that's still to come, but at least there's some important progress on fundamentals to report.
A few more things to figure out, but then all of it may get pretty serious and a real tool will emerge!

Take 5

I still have to figure out how to compress and decompress, which seems trivial, but...eh...

Not sure, but maybe https://stuk.github.io/jszip/ can help?

[Taron]

Errr...not sure, yet. I have tried pako itself, which this one uses, too, except it inflates it to 200% in size, haha. Not sure what sort of conveniences are added to justify the weight, but I will have a look. I believe, my main problem is that I just don't have full command yet over javascript. There are things I don't quite know yet, which make me stumble a little when it comes to turning Float32Array into an ArrayBuffer that the zipper then compresses, later decompress and back to Float32Array. I feel that it is ridiculously easy and should not be a problem, but there must be this one little thing I'm missing. It's like I have it already, but am overlooking one piece of understanding.
I checked superficially the contents it creates and they look perfectly fine.
Sometimes there are several problems at the same time and I may be trying to fix a hole in one pipe, not realizing that I've fixed it already, while a whole other pipe was wide open. Than I decide to abandon the pipe I fixed, find the other one and close it and all works again acceptably. If only now I would go back to the fixed pipe and put it back in place. But experience then tells me, that as long as I don't know what I'm doing, I will simply spiral back down into an endless fixing hell. Thus I must first gather more information, get smarter, so to say.
Programming... I love it and it seems to hate me sometimes.
zip solutions I've looked at:
• pako
• uzip
• snappyjs
• lz-string

Yes, I very know this situation. After some years I jumped into web world again and this is result:
At the end of last year, I had to study and use React technology. https://reactjs.org/ Very nice but if someone goes deeper needs more and more libraries. One day I felt lost.
There are too many technologies and it is difficult to decide which way to go. Technology is literally changing at hand!

Your project is a little bit specific and I think js language wasn't originally invented for this type of data manipulation. It is possible to do that for sure, but don't know so much about that to assist.

Maybe these descriptions can help?
https://developer.mozilla.org/en-US/doc ... rayBuffers
https://developer.mozilla.org/en-US/doc ... oat32array

Not know if this could help but...
when fixing bugs I create a folder with all the "txt" files pluss an Info file saying what problem I'm going to fix, in which file, and in which line, perhaps you could put "trying XXX lib"
I'll keep a lot of folders each one being a diff version of the little program, each one with its own Info file. Fixing just one thing at a time.