trunk is open

[Boudewijn Rempt]

Hi,

Now that trunk is open, I would like to enable both the tiles3 engine and the
pyramid by default, because that is platform we want to optimize for 2.2.

For bug fixes: I hope that everyone will go on fixing bugs, we've only got
about 40 real bugs left and we should try tix them all :-). I would propose
that we fix all bugs in the 2.1 branch, and then forward port the fix to
trunk, so we know the fix is good and that 2.1.1 is going to be a nice
release, as well.

Any comments?
--
Boudewijn Rempt | http://www.valdyas.org
_______________________________________________
kimageshop mailing list
kimageshop@...
https://mail.kde.org/mailman/listinfo/kimageshop

[Cyrille Berger]

On Sunday 25 October 2009, Boudewijn Rempt wrote:
> Hi,
>
> Now that trunk is open, I would like to enable both the tiles3 engine and
>  the pyramid by default, because that is platform we want to optimize for
>  2.2.
yes. +\infinity :)

> For bug fixes: I hope that everyone will go on fixing bugs, we've only got
> about 40 real bugs left and we should try tix them all :-). I would propose
> that we fix all bugs in the 2.1 branch, and then forward port the fix to
> trunk, so we know the fix is good and that 2.1.1 is going to be a nice
> release, as well.
Yes but branch/2.1 is frozen until 2.1.0 and require review.

--
Cyrille Berger
_______________________________________________
kimageshop mailing list
kimageshop@...
https://mail.kde.org/mailman/listinfo/kimageshop

[Boudewijn Rempt]

On Sunday 25 October 2009, Cyrille Berger wrote:

> On Sunday 25 October 2009, Boudewijn Rempt wrote:
> > Hi,
> >
> > Now that trunk is open, I would like to enable both the tiles3 engine and
> >  the pyramid by default, because that is platform we want to optimize for
> >  2.2.
>
> yes. +\infinity :)
>
> > For bug fixes: I hope that everyone will go on fixing bugs, we've only
> > got about 40 real bugs left and we should try tix them all :-). I would
> > propose that we fix all bugs in the 2.1 branch, and then forward port the
> > fix to trunk, so we know the fix is good and that 2.1.1 is going to be a
> > nice release, as well.
>
> Yes but branch/2.1 is frozen until 2.1.0 and require review.
>

Ok -- that's an important point. Patches to the ml first :-)

--
Boudewijn Rempt | http://www.valdyas.org
_______________________________________________
kimageshop mailing list
kimageshop@...
https://mail.kde.org/mailman/listinfo/kimageshop

[Boudewijn Rempt]

On Sunday 25 October 2009, Boudewijn Rempt wrote:

Oh, and for trunk I'd like to propose the following, since we don't have a
nice gitorious environment yet with staging tree and all that:

 * plugins can always be committed, no matter what the state.
 * bug fixes need to have a bugzilla number, create a bug yourself if needed,
they need to be created for 2.1, reviewed, and then applied to 2.1 and trunk
 * trunk refactorings need to be proposed on the mailing list, where people
participating in a discussion can ask for the patch to be reviewed first.

Anything I've forgotten?
--
Boudewijn Rempt | http://www.valdyas.org
_______________________________________________
kimageshop mailing list
kimageshop@...
https://mail.kde.org/mailman/listinfo/kimageshop

On Sun, Oct 25, 2009 at 2:07 PM, Boudewijn Rempt <boud@...> wrote:

On Sunday 25 October 2009, Boudewijn Rempt wrote:

Oh, and for trunk I'd like to propose the following, since we don't have a
nice gitorious environment yet with staging tree and all that:

 * plugins can always be committed, no matter what the state.
 * bug fixes need to have a bugzilla number, create a bug yourself if needed,
they need to be created for 2.1, reviewed, and then applied to 2.1 and trunk
 * trunk refactorings need to be proposed on the mailing list, where people
participating in a discussion can ask for the patch to be reviewed first.

Anything I've forgotten?

I think we shoud have something like the Kexi TODO http://wiki.koffice.org/index.php?title=Kexi/TODOs
So we say Krita 2.2 aims for performance and blender movie usage.

We should analyse what needed for this and then list all planned features, refactorings etc. there and assign prioritys to them.
That way I hope we could be a better overview what everybody is working on.

_______________________________________________
kimageshop mailing list
kimageshop@...
https://mail.kde.org/mailman/listinfo/kimageshop

[Boudewijn Rempt]

On Sunday 25 October 2009, Sven Langkamp wrote:

> I think we shoud have something like the Kexi TODO
> http://wiki.koffice.org/index.php?title=Kexi/TODOs
> So we say Krita 2.2 aims for performance and blender movie usage.
>
> We should analyse what needed for this and then list all planned features,
> refactorings etc. there and assign prioritys to them.
> That way I hope we could be a better overview what everybody is working on.

Yes, indeed. Though we do have a big todo list already, and we've tried having
a wiki todo before, which didn't work either. I'm still working with Lukas on
his project proposal, which is a large part of that plan.

How about having a brainstorm session on the mailing list first, and then let
me come up with a page on the wiki that describes the plan?

--
Boudewijn Rempt | http://www.valdyas.org
_______________________________________________
kimageshop mailing list
kimageshop@...
https://mail.kde.org/mailman/listinfo/kimageshop

[Cyrille Berger]

On Sunday 25 October 2009, Boudewijn Rempt wrote:
> Yes, indeed. Though we do have a big todo list already, and we've tried
>  having a wiki todo before, which didn't work either. I'm still working
>  with Lukas on his project proposal, which is a large part of that plan.
Our todo contains tasks for the next twenty years :) I think a TODO for 2.2,
like the feature list page we have for koffice is quiet manageable.

--
Cyrille Berger
_______________________________________________
kimageshop mailing list
kimageshop@...
https://mail.kde.org/mailman/listinfo/kimageshop

[Boudewijn Rempt]

On Sunday 25 October 2009, Cyrille Berger wrote:
> On Sunday 25 October 2009, Boudewijn Rempt wrote:
> > Yes, indeed. Though we do have a big todo list already, and we've tried
> >  having a wiki todo before, which didn't work either. I'm still working
> >  with Lukas on his project proposal, which is a large part of that plan.
>
> Our todo contains tasks for the next twenty years :) I think a TODO for
>  2.2, like the feature list page we have for koffice is quiet manageable.
>

Sure, that's why I want some discussion on what we're going to do, and also
commitment on getting it done. I'll start:

 * Fix bugs as they arrive. My goal is to be be under 20 bugs for 2.2, and to
have no unassigned bugs. (That also means that if you think a bug is right up
your alley, that I'd like you to assign that bug to yourself.)

 * fix serialization of the paintops, so stroke recording can work again. This
might entail some refactoring.

 * finish my mypaing brush-compatible brush engine.

 * implement alpha-locking. Initial support is already committed, now I just
need to use Enkithan's icons and make it work, preferably without refactoring
pigment.

--
Boudewijn Rempt | http://www.valdyas.org
_______________________________________________
kimageshop mailing list
kimageshop@...
https://mail.kde.org/mailman/listinfo/kimageshop

[Cyrille Berger]

On Sunday 25 October 2009, Boudewijn Rempt wrote:

> On Sunday 25 October 2009, Cyrille Berger wrote:
> > On Sunday 25 October 2009, Boudewijn Rempt wrote:
> > > Yes, indeed. Though we do have a big todo list already, and we've tried
> > >  having a wiki todo before, which didn't work either. I'm still working
> > >  with Lukas on his project proposal, which is a large part of that
> > > plan.
> >
> > Our todo contains tasks for the next twenty years :) I think a TODO for
> >  2.2, like the feature list page we have for koffice is quiet manageable.
>
> Sure, that's why I want some discussion on what we're going to do, and also
> commitment on getting it done. I'll start:
>
>  * Fix bugs as they arrive. My goal is to be be under 20 bugs for 2.2, and
>  to have no unassigned bugs. (That also means that if you think a bug is
>  right up your alley, that I'd like you to assign that bug to yourself.)
>
>  * fix serialization of the paintops, so stroke recording can work again.
>  This might entail some refactoring.
>
>  * finish my mypaing brush-compatible brush engine.
>
>  * implement alpha-locking. Initial support is already committed, now I
>  just need to use Enkithan's icons and make it work, preferably without
>  refactoring pigment.

Keep up with the polishing of 2.0/2.1 things:
* finish the CTL colorspace, that include optimizations, and full support for
operations
* finish merging of dynamic brush concepts into normal brush, that include the
coloring options and angles, would probably an opportunity to look at some of
the issues
* keep polishing Shiva support, and GHNS integration
* unit testing of pigment's operations (especially the one that are a bit
broken, like convolution)

File support:
* I want EXR to be a top class citizen in Krita, support for 16bit and 32bit,
full CM (and probably layers if someone from blender is willing to answer a
few questions and provide a test file)
* since we are getting ride of GraphicsMagick, it's probably a good idea to
work on replacing some of the filter as well, from those, my priorities would
be ppm and jpeg2000

Color choosers:
* I want to ditch that *beep* dialog :) We need a great color dialog
* I have been thinking about a "digital color mixer" for a while, you will
know more soon, since I think that the first thing I want to do after my PhD
work is done ! I need fun !

I think that's all. Of course, I might work on other stuff depending on my
mood, like add more recorded actions (gradient, fill, ....), and maybe make the
tutorial docker.

--
Cyrille Berger
_______________________________________________
kimageshop mailing list
kimageshop@...
https://mail.kde.org/mailman/listinfo/kimageshop

On Sunday 25 October 2009 19:57:29 Cyrille Berger wrote:

> On Sunday 25 October 2009, Boudewijn Rempt wrote:
> > On Sunday 25 October 2009, Cyrille Berger wrote:
> > > On Sunday 25 October 2009, Boudewijn Rempt wrote:
> > > > Yes, indeed. Though we do have a big todo list already, and we've
> > > > tried having a wiki todo before, which didn't work either. I'm still
> > > > working with Lukas on his project proposal, which is a large part of
> > > > that plan.
> > >
> > > Our todo contains tasks for the next twenty years :) I think a TODO for
> > >  2.2, like the feature list page we have for koffice is quiet
> > > manageable.
> >
> > Sure, that's why I want some discussion on what we're going to do, and
> > also commitment on getting it done. I'll start:
> >
> >  * Fix bugs as they arrive. My goal is to be be under 20 bugs for 2.2,
> > and to have no unassigned bugs. (That also means that if you think a bug
> > is right up your alley, that I'd like you to assign that bug to
> > yourself.)
> >
> >  * fix serialization of the paintops, so stroke recording can work again.
> >  This might entail some refactoring.
> >
> >  * finish my mypaing brush-compatible brush engine.
> >
> >  * implement alpha-locking. Initial support is already committed, now I
> >  just need to use Enkithan's icons and make it work, preferably without
> >  refactoring pigment.
>
> Keep up with the polishing of 2.0/2.1 things:
> * finish the CTL colorspace, that include optimizations, and full support
>  for operations
> * finish merging of dynamic brush concepts into normal brush, that include
>  the coloring options and angles, would probably an opportunity to look at
>  some of the issues
> * keep polishing Shiva support, and GHNS integration
> * unit testing of pigment's operations (especially the one that are a bit
> broken, like convolution)
>
> File support:
> * I want EXR to be a top class citizen in Krita, support for 16bit and
>  32bit, full CM (and probably layers if someone from blender is willing to
>  answer a few questions and provide a test file)
> * since we are getting ride of GraphicsMagick, it's probably a good idea to
> work on replacing some of the filter as well, from those, my priorities
>  would be ppm and jpeg2000
>
> Color choosers:
> * I want to ditch that *beep* dialog :) We need a great color dialog
> * I have been thinking about a "digital color mixer" for a while, you will
> know more soon, since I think that the first thing I want to do after my
>  PhD work is done ! I need fun !
>
> I think that's all. Of course, I might work on other stuff depending on my
> mood, like add more recorded actions (gradient, fill, ....), and maybe make
>  the tutorial docker.
>

Paintops (some are thesis related):
* implement new paintops as they arrive, when I get idea
* unify my paintops GUI, work with Cyrille and use sensors and share color
dialog
* brush outline should be QPainterPath , remove KoViewConvertor from paintops
this way
* finally look at the Emanuelle's work of Kubelka-Munk color composition
* 3D brush needs shadows

Blender project:
* GLSL, OpenGL optimizations
* all we came up during brainstorm with our community and David Revoy (UI
fixes, speed-ups where can I do something)

* try to fix the bugs I'm assigned to.






_______________________________________________
kimageshop mailing list
kimageshop@...
https://mail.kde.org/mailman/listinfo/kimageshop

On Sun, Oct 25, 2009 at 7:32 PM, Boudewijn Rempt <boud@...> wrote:

On Sunday 25 October 2009, Cyrille Berger wrote:
> On Sunday 25 October 2009, Boudewijn Rempt wrote:
> > Yes, indeed. Though we do have a big todo list already, and we've tried
> >  having a wiki todo before, which didn't work either. I'm still working
> >  with Lukas on his project proposal, which is a large part of that plan.
>
> Our todo contains tasks for the next twenty years :) I think a TODO for
>  2.2, like the feature list page we have for koffice is quiet manageable.
>

Sure, that's why I want some discussion on what we're going to do, and also
commitment on getting it done. I'll start:

 * Fix bugs as they arrive. My goal is to be be under 20 bugs for 2.2, and to
have no unassigned bugs. (That also means that if you think a bug is right up
your alley, that I'd like you to assign that bug to yourself.)

 * fix serialization of the paintops, so stroke recording can work again. This
might entail some refactoring.

 * finish my mypaing brush-compatible brush engine.

 * implement alpha-locking. Initial support is already committed, now I just
need to use Enkithan's icons and make it work, preferably without refactoring
pigment.

* finish paintop presets (might interfere with the work from Boud or Lukas, so that needs more dicussion)
* adding shape layer implementation to the various visitors
* get toolbox to work correctly with different layers
* create flake shapes with Krita shape tools

And of course improving performance and trying to push the crash bugs to zero.
I'm also interested in the helping with the Blender project where I can.

_______________________________________________
kimageshop mailing list
kimageshop@...
https://mail.kde.org/mailman/listinfo/kimageshop

[Boudewijn Rempt]

Dmitry, ping? I've got 2.2 plans and commitments from Cyrille, Lukas, Sven and
me -- I need to know whether you think you'll be able to finish the tile
engine/pyramid refactoring for 2.2, too, and whether you have any other plans.

--
Boudewijn Rempt | http://www.valdyas.org
_______________________________________________
kimageshop mailing list
kimageshop@...
https://mail.kde.org/mailman/listinfo/kimageshop