Hi, I'm Bryan, the original author of pixelsnap.

I'd be keen to have PixelSnap included in the official Inkscape repository,
and to do whatever's necessary for that purpose (I don't mind releasing it
under GPL, either -- I just like the MIT license because it's short & sweet)

Just a brief rant on why I think PixelSnap is a useful part of a digital
artist's workflow, even if they know inkscape's tools:

I'm a fairly technical user of Inkscape, but in spite of the great work done
on snapping & grids recently (kudos to the people involved with that!), I've
still found the "right" way to be a bit of a pain in the backside.

The reasons Rob gives below are two good examples. Another big reason why
the "right" way is often unworkable is the fact that odd-width strokes are
offset by exactly 0.5 pixels. I understand the reasoning for this, but it
means you have to have 2 pixel-sized grids, one pixel-aligned, and one
mid-pixel-aligned.

Also, you have to keep the grid on permanently while editing for the "right"
way to work, unless you want to go back and edit all your vectors later on.
I don't find it very easy working with grids all over my work. Sometimes I
don't want stuff to snap either -- I only want vertical & horizontal lines
to snap-to-pixel.

I'd also rather set up meaningful grids for my artwork -- i.e. grids for
layout purposes, not grids to overcome the shortcomings of my screen.

Alexandre Prokoudine wrote:
>
> On 1/13/10, Rob Antonishen wrote:
>> The biggest benefit is when working with existing images that were not
>> necessarily drawn to pixel snap.
>>
>> Or after rescaling images and resnapping the elements to the nearest
>> pixel.
>
> Exactly :)
>

--
Bryan Hoyt, Web developer — Brush Technology
Ph: +64 3 942 7833 Mobile: +64 21 238 7955
Web: brush.co.nz