deskew plugin

[Cyrille Berger]

> I suppose that copying+pasting plugins from krita/plugins to krita-plugins
> isn't really the best route but it's sure easier to get started on a new
> plugin that way then to have to start a new one from scratch. For example,
> I'm doing the gradient clone tool so I've simply copied the duplicate tool
> plugin and will just modify the copy function but leave the rest alone. Its
> easier not to play games with which headers to remove because they're not
> part of the "external plugin API" and add a includedir path to them. This
> of course is the problematic part.
In my opinion, modification to "official" tools and plugins should happen in 
trunk (or in a branch blessed for that specific use)

> > Krita will have show maturity when (and only when) we will see external
> > plugins project.
>
> IMHO Krita will be mature when it's ABI doesn't have to change for external
> developers to implement reasonable outside plugins. (Reasonable is course
> subjective :) I suppose krita will be very mature when it can copy TT and
> really truely not change ABI between major revisions and API between minor
> revisions.
well TT keeps a lot of stuff private ;) they don't install all their include 
files, and that's how they can keep ABI/API for a long time.

-- 
Cyrille Berger