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

List:       kde-devel
Subject:    Re: QuickPrint implementation (RFC)
From:       Michael Goffioul <goffioul () imec ! be>
Date:       2001-03-31 15:41:43
[Download RAW message or body]

> > - The action would be named, the name corresponding to the printer where to send
> >     print job. By default, the name would be empty, meaning to use user default printer.
>
> You can't have a variable name for an action. It would prevent using this
> action in the XMLUI (where actions are defined by name).
> The printer could be stored in the app's config file (or desktop-global) instead,
> no ?
> Or did you simply mean the text of the action (for instance, for those using
> text under or besides icons, in toolbars, and in the tooltip ?
> (All that's handled by KAction of course, you only need to setText()).

I don't mean to store any printer name in the XMLUI file. I mean that when the action is
created, it is in default state: the default printer is used. If the user uses another printer
(for example with the delayed popup), then the last printer is used. At this moment, the
KPrinter object saves the last used printer in the application rc file. This can also be
used by the action to initalize itself, however this is a dangerous behaviour that can be
confusing, IMO it is more consistent to initialize with the default printer. If the user
doesn't remember that last time he used a different printer, he can then send the print job
anywhere without being aware of it.

> > - From a performance point of view, everything should be created on demand: the
> >     KPrinter object should be created only when the button is first clicked, the printer
> >     list should only be retrieved when the popup menu is shown, ...to not slow down
> >     the application start-up.
>
> And all that being handled internally by the action, I suppose ?
> In that case, it's fine IMHO.

Yes, all this would be handled by the action, which will be reponsible for the KPrinter object.

> OTOH from the user point of view, I personnally hate such buttons.
> I often click on the wrong button by mistake, and since it starts printing
> immediately it's too late already. IMHO there should at least be a confirmation
> dialog box [maybe with a don't-show-again], or the full dialog with everything
> already set up... which is the case by default, isn't it ? :}

When the print dialog is first popped up, the last printer used is set as default, but the
default printer options are used (maybe I should change that to always use the user
default printer on first time). On further calls, the print dialog is set up in the state it
was closed on previous call.
Personally, I don't like those "quickprint" buttons neither, exactly for the same reasons
as you, but somebody requested it. And if a lot of people wants it, then I think it should
be implemented. I don't think it's too much work, but of course, applications have to
use it, otherwise it's useless.
That's why I'm asking of people finds it useful or not.

Michael.

PS: What OTOH stands for ?

--
------------------------------------------------------------------
Michael Goffioul                IMEC-DESICS-MIRA
e-mail: goffioul@imec.be        (Mixed-Signal and RF Applications)
Tel:    +32/16/28-8510          Kapeldreef, 75
Fax:    +32/16/28-1515          3001 HEVERLEE, BELGIUM
------------------------------------------------------------------



 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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