whither krita -- summary

[Boudewijn Rempt]

On Thursday 24 September 2009, Cyrille Berger wrote:

> I will let you count how many different way you have to make a new layer :)
>  We need to make cuts in that menu. I would be tempted to move all the
>  transform business (rotate, shear, mirror...) in the transform tool (it's
>  the koffice intereaction model after all). Maybe the metadata could be
>  merged with properties. I would also merge layer and mask menu, most of
>  the entry are the same, and we could just disable those that don't apply.

I really want to cut down the layer menu before we release. Specifically, 
I want to remove:

 * layer/new: everything above the separator, that's also in the layer box
 * remove, hide, properties, raise, lower, top, bottom

(because these aren't synched with the options in the layerbox, leading to
bugs).

 * tonemapping to layer/effects 

I would love metadata to be in properties, instead of the menu, let's just 
make that another tab. It doesn't add a string, so we can do it now. 

And aol to merging the layer and the mask menu, but I'm not sure that that's 
actually easy to do.

> 
> > > > And, actually, the services a kde needs to have running mean that
> > > > it's very unlikely that there will ever be a krita installer for
> > > > windows or a krita dmg for OSX.
> > >
> > > hum we have that for windows. I just think that those platforms need
> > > love.
> >
> > Do you mean the kde-windows installer?
> 
> yes.
> 
> > Because I don't think that really
> > counts. It's not an installer for Krita, so it weirds out everyone who
> >  doesn't know about the linux way.
> 
> I don't think it is that hard to hide all the complexity, like having
> preselected krita and skip all the mess of packages selection. It shouldn't
>  be even hard to have an .exe that ship with all the "packages". Even if
>  nowdays, setup.exe that go on internet to download the software is very
>  common.

I have a fear that it's going to be really hard to have a setup.exe that 
doesn't interfere with amarok's setup.exe in that case. But we can probably 
leave that for now to the kde-windows guys.

> 
> > > Well we have some good UI concept as well, like the filter "class", the
> > >  paintop "class" and tool "class", I think we more have a problem of
> > >  uniformity, most paintop widgets seems different from one an other.
> > > Filter aren't really better.
> >
> > That's a good  point.
> 
> Could be good to define UI guidelines, and then have code to support that.

the paintop options thing was a start, but it was burdened by a historical 
background that has clouded my judgement when I designed it. It needs, alas, 
work.

-- 
Boudewijn Rempt | http://www.valdyas.org