Whither Krita?

[Dmitry Kazakov]

I've just read the thread...

*for Cyrille:*
About filter-based approach that Gimp uses...

I've thought about something like that for Krita recently. And i've got the
following idea:

All the actions on the image (except of painting) could be based on adj.
layers. E.g. if you want to change the size of the image (or switch to a
different colorspace), you can just add a proper layer into the stack. If
you do not want to have an additional layer, you can merge it down.

I'm thinking this idea over on leisure... And i think i'll be able to
publish details one day =)

This idea has many advantages:
1) We can keep design of the Krita extremely simple:
  - a small kernel for managing stack
  - a paintop kernel
2) All the featutures, like tranformation, CS-switch, channel-blending can
be easily made as filters (mind! no kis_transformation_layer! its simply not
needed)
3) A user will have a uniform interface(!) for all actions
4) At the moment, we have too much code duplication in Visitors that makes
image/ design weird.

*for Cyrille (again):*
You said about script-based filters. Like Invert filter written with digits.

Most of the stuff described with "linear pixel color conversion function"
can be represented with "Curves" filter. Any scripting here is simply
redundant if we do not base coefficients on source image at least. More than
that MOST of the color conversion features can be based on Curves, in case
we do not do any automation.

*for Boud:*
About Git.

What are we waiting for? Will Git really help our project? If it does, why
not just set up any public hub for that? Like github.com? Our git repository
without history is just 149M.
Commits from a public hub could be transmitted to svn daily (Thomas, ping!
Is it possible?).

About stopping features creation process and starting fixing bug.

There are many design issues that simply can't be fixed easily. I'd say we
should "stop features creation and start discussion of the design" and make
our code easy to maintain.

*for All:*
Someone said that krita has many abilities: vector graphics, raster and so
on...

I don't think it's good to have all-in-one application. We shouldn't break a
basic principles of our users - "unixway" and kiss. Most of our users are
unix-users, right?
That's why i think it's better to have good communications between
Krita<->Karbon instead of an ability to work with vectors inside krita.



-- 
Dmitry Kazakov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kimageshop/attachments/20090919/406a92f0/attachment.htm