Pixel.tools editor allows artists to pixel together on the same image/animation.

[AlexHW]

Alright, I fixed the initialization of the colors- that should've been addressed a long time ago but I kept putting it off. It also now remembers your previous colors whenever you return to the editor.
Ensuring they get initialized fixes the issue with them becoming black. Also, I fixed a bug I found in the process.
Not sure what you mean with the brush snapping to the grid within the colordex- are you sure that's the case?
Right click doesn't do anything at the moment- I'm still unsure whether to make it used for the secondary color.
I tried your suggestion with the blending of the brush outline with the previous color. Let me know if that looks better.

[Ai]

Actually, on close inspection, the behaviour isn't snapping to a 2x2 grid (though that's the usual outcome when not actually painting). I would bet on Firefox performing motion compression on the events arriving from the tablet .. which is consistent with the behaviour of 'strokes faster than a moderate speed become increasingly polygonal'

Anyway, you can see it happening in a  zoomed in view in this 2min video clip, where I continuously move the cursor as little as I can. Was not able to test this with the WacomWebPlugin, as it instantly crashed when I reloaded pixel.tools. Not sure that you can do anything to ask Firefox for uncompressed motion events, so it may be unaddressable from your side.

Yeah, the new brush outline is much less jarring.

[AlexHW]

Okay, I fixed that snapping issue. The colordex and secondary viewport were useing the primary viewports zoom value for the brush edge- so it was moving it extra pixels because the primary viewport was zoomed in. That's fixed now.
Is the wacomwebplugin crash related to it not being supported on linux, or do you think it is something related with the editor?

[Ai]

Okay, I fixed that snapping issue. The colordex and secondary viewport were useing the primary viewports zoom value for the brush edge- so it was moving it extra pixels because the primary viewport was zoomed in. That's fixed now.

Ah. Yeah, looks good now.

Is the wacomwebplugin crash related to it not being supported on linux, or do you think it is something related with the editor?

No idea. Although not being officially supported, I don't see how something notional like that could ever cause a crash. The unofficial plugin might well be buggy -- on my system, crashing appears to be the usual case, not the exceptional one.

Anyway I went and did some testing.

http://www.wacomeng.com/web/TestFBCanvasScribble.html seems to be quite happy -- pretty smooth motion, plugin doesn't crash

http://www.wacomeng.com/web/TestFBPluginTable.html initially crashes. Reloading makes it work reasonably, with the caveat that pressure always remains at 0

It could be down to a few things really. The plugin could not play well with EvDev-based tablet drivers, it could just be buggy (IMO if a software crashes, it is always that software's responsibility, even if said crash occurred as a side effect of the behaviour of other system elements). There's really no reason to assume that pixel.tools is responsible.

[AlexHW]

Thanks for that info, Ai.

I've finally got around to creating a video that demonstrates how to setup and use the Colordex.
http://youtu.be/QGLg-N9RT44

Also, I adjusted the system so that as long as either the big square or little square is off a color, then it'll work (before it would only work in transparent space if the big square was off, which sometimes made things confusing).

[AlexHW]

Okay, I finally got around to uploading it to Github for those who keep asking.
https://github.com/prominentdetail/Pixel.Tools
Hope we can all collaborate together on this to improve it and make it the best pixel editor out there!

[MasqueradeFisher]

Yo, the website is down BTW

[AlexHW]

Yo, the website is down BTW

moved it to https://prominentdetail.github.io/Pixel.Tools/