[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kimageshop
Subject:    Re: whither krita -- summary
From:       Matthew Woehlke <mw_triad () users ! sourceforge ! net>
Date:       2009-09-24 16:14:35
Message-ID: h9g5tb$q4u$1 () ger ! gmane ! org
[Download RAW message or body]

Boudewijn Rempt wrote:
> go all node                  <---------> continue with the current core

I'd love to see a purely procedural, node-based paint program, but it 
would almost have to be started from scratch as a side project. Also, at 
that point, I think I would seriously consider merging it with vector 
editing.

> Use cases I've seen in the thread:
> 
>  * photo manipulation
>  * HDR workflow (for film or for pictures?

Stills (at least in my case).

>  * illustrations and comics
>  * sketching
>  * integration with movie workflow, blender
>  * web development (what is that, actually?)

What about digital real-media painting?

> Can all these things work in one application? 

Why not? ;-) Yes, it will be a bit bloated, but by the same token I can 
easily see needing just about any combination of the above in a single 
work. Therefore, being able to do everything in one application has a 
certain desirability.

Also, your point:
> So I'd say, if we go for a big integrated can-do-everything app, we 
> need to come up with a UI strategy that works
...is right on the money.

> Reasons to work on Krita:
> 
>  * prefer qt, c++ over gtk, c (I find this a bit disappointing, this can 
> hardly become a compelling reason for people to use the application)

It is if there is otherwise close to feature parity :-).

-- 
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
-- 
Anything that can go wrong, will go wrong. Plan accordingly.

_______________________________________________
kimageshop mailing list
kimageshop@kde.org
https://mail.kde.org/mailman/listinfo/kimageshop
[prev in list] [next in list] [prev in thread] [next in thread]