phildo3

nice! how'd you find this game?

"Ok, so I think my password is something like ILoveBananas123, but I can't remember if it was like or love, or if the numbers came first or second, or where the capitalizations were... oh dang I'm screwed"-

Not anymore!

("123" <{"I""i"}("Love""Like"){"B""b"}"ananas">[-m1])

I initially made this as a tool to help alongside game development - specifically spritesheet editing, and futzing with textures-as-data and the like. Was never intended to be a high level replacement for photoshop or anything hah.

(ugh, what is this "limit 2 posts per hour" madness... lol)

(not to mention correcting for gamma depending on exactly what you want to do with your blur... again, pixQL probably isn't the right tool for this as it currently stands hah)

It's possible, but unfortunately a bit obtuse in this language (you might want to just use photoshop for something like that...).

One way you could do it is as follows:

OPERATE SET R = (IN[COL,ROW-1].R + IN[COL-1,ROW] + ...)/8;

Unfortunately, that's just the R channel. I should find a way to consider COLOR that would be smart enough to just have it apply the operation across all channels. (right now, the COLOR keyword is nice for simple "set color to this" type of things)

Thanks for the feedback! Definitely considering where to prioritize features, and drawing or "select where in polygon(x1,y1,x2,y2,...)", etc... are definitely on the table (first I need to fiddle with some compatibility stuff and clean up the code a bit).

As far as the license, I haven't yet decided... pretty new/naive when it comes to deciding something like that... I don't plan on selling it for money, and I obviously like that the source is available, and want contributions, etc... but yeah. not sure. (Any tips would be welcome :P)

maybe. but as it stands, so long as you can compile it, it doesn't need any external libraries or installs or anything like that, which is something I value (I assume your post is hinting at using node, rather than some in-browser thing... if not, there are plenty of other reasons I prefer to keep it out of the browser hah).

Author here- My reason for deviating slightly from traditional SQL syntax is that I don't find it to be super intuitive. Yes, "UPDATE color SET r = 255 WHERE col = 100" is a pretty straightforward looking thing for those of us familiar with SQL, but simple things like the fact that you set the value before deciding what you're setting the value of are a bit off putting. The separation of queries into multiple statements along with this fact lead to just universally cleaner and more consistent looking syntax even as queries get complex.

That said, I'm still very much in the "trying things out" phase w.r.t. syntax 'n such. So the feedback is appreciated! (And you're not the only one who has suggested this...)

Curious what you'd expect the result of a join to be? I assume you mean across multiple images? Currently, that would be a bit odd as the function of "select" exists more along the lines of "composing a mask" more than it does "fetching data", so not entirely sure how that'd fit in. Still very interesting. If you're interested in fleshing that idea out here, it could be helpful for me!

Thanks!