GSoC Status - Week 5 (Customizable prints)

[Dirk Hohndel]

On Wed, Jul 01, 2015 at 05:23:32PM +0300, Lubomir I. Ivanov wrote:
> On 1 July 2015 at 17:18, Dirk Hohndel <dirk at hohndel.org> wrote:
> > On Wed, Jul 01, 2015 at 04:51:13PM +0300, Lubomir I. Ivanov wrote:
> >>
> >> basically, i was going to ask about the whole b&w vs color printing.
> >> given that in the new print stack the user will have complete control
> >> of colors, layout and so on via templates, do we still need the "print
> >> in color" toggle, which will supposedly override the template colors
> >> and convert everything to greyscale.
> >
> > My instinctive reaction would be that this seems odd and redundant. If you
> > want greyscale, build a greyscale template. But I may be missing
> > something.
> >
> >> i would say, yes.
> >> also, we might have an easy solution to do that via CSS (suggested in
> >> a previous email), but Gehad needs to confirm it.
> >
> > Can you explain why you think the answer is yes?
> >
> 
> it would act like an override, so if one likes a template, he/she can
> still toggle off the "print in color" and produce b&w output of said
> template.
> if it's way too difficult to implement, i guess we can consider it as
> redundant and remove the option completely.

So IIRC the problem we had was that you had to pick smart "colors" (i.e.,
good gray values) for b/w prints to look reasonable.

So if I build a nice color template - how would this pick colors that work
well?

I'm not saying I'm against having it - I'm asking if this is worth
focusing time on vs. just creating a couple of strong b/w templates (and
fixing the profile2 problem which I think you have either way, correct?).

I'll be happy to be convinced that I'm wrong and that this adds a valuable
feature... I'm just poking at this to understand if this is the right
space to focus our energy on.

/D