sponsored work for Dmitry

[silvio grosso]

Hi everyone,

Sven wrote:
> These topics could be grayscale mask, fixing the canvas, finishing strokes 
framework, reducing memory footprint or improving painting performance.

I think this is a good plan :-)

Along this path, I am confident Dmitry will fix many bugs as well (the more, the better). Therefore, in the end, everyone is going to be happy :-)

Best regards,

Silvio Grosso



--- Lun 17/9/12, Sven Langkamp <sven.langkamp at gmail.com> ha scritto:

Da: Sven Langkamp <sven.langkamp at gmail.com>
Oggetto: Re: sponsored work for Dmitry
A: "Krita's developers and users mailing list" <kimageshop at kde.org>
Data: Lunedì 17 settembre 2012, 05:16

On Sun, Sep 16, 2012 at 8:02 PM, Lukast dev <lukast.dev at gmail.com> wrote:

Hello,



I propose fixing bugs related to canvas, layers and masks or basically

any crash or major bug or old bug fixed is a win.

E.g.

284060  krita   general dimula73        NEW     NOR     longs strokes become progressively slower

289915  krita   general krita-bugs-null NEW     NOR     Krita's Canvas produces

subtle artifacts on incremental updates

..and there are more.



For performance Dmitry could explore the possibilities of bitBlitting

in threads in a way where threads don't step on each other toes e.g. with tools?

Sven did some work here but Dmitry has knowledge about strokes

framework, which might

help him.

I think a major improvement could be to vectorize the composite op code. That does need more threads and should give a similar speed boost. The task isn't trivial as our memory layout isn't optimal for that, so that will require some work.

For strokes we really need some simplyfication, I think. There are lots of classes that interact is some way there and maybe we need to reevaluate some of the original requirements. Beside that we should keep in mind that at some later point we need that macro/command system that we dicussed some time ago and it should fit together.
 
From the painting bugs area: I did not find solution for correct speed

sensor, there

are multiple bugs in bugzilla about it's behaviour.



About the memory footprint, transform tool has this bug

https://bugs.kde.org/show_bug.cgi?id=263170
I don't think we should concentrate on random bugs, but rather some bigger complex that needs improvements. Maybe have three or four big topics that take about a month each.

These could be grayscale mask, fixing the canvas, finishing strokes framework, reducing memory footprint or improving painting performance.
 


That's all I have on mind currently :)



Lukas



2012/9/14 Boudewijn Rempt <boud at valdyas.org>:

> Hi,

>

> We're looking at a new period of about 4 months of sponsored work for

> Dmitry, so Dmitry and I were trying to create a planning, a list of the most

> urgent issues.

>

> Here's our list as it stands now:

>

> 1) Grayscale masks

> 2) Finish porting all tools to the strokes system

> 3) Start thinking of a way to reduce krita's memory footprint.

>

> However, we'd like some input from y'all on what is currently blocking

> productivity most, so we can review those issues for our planning :-)

>

> Boudewijn

> _______________________________________________

> kimageshop mailing list

> kimageshop at kde.org

> https://mail.kde.org/mailman/listinfo/kimageshop

_______________________________________________

kimageshop mailing list

kimageshop at kde.org

https://mail.kde.org/mailman/listinfo/kimageshop




-----Segue allegato-----

_______________________________________________
kimageshop mailing list
kimageshop at kde.org
https://mail.kde.org/mailman/listinfo/kimageshop
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kimageshop/attachments/20120917/702df738/attachment.html>