gmane.comp.printing.pykota.user

joel.trehard | 10 Jul 15:39

Pykoticon

GoodAfternoon

I have a problem on pykoticon.  When 2 users want to print,  the user 2 
must waiting  the answer on the pop-up of the user 1 to see appearing 
his pop-up.   It slows down and a user who  forgets to confirm,  stop  
  the   others users.

Another thing,  is  there  a solution   to see appearing  this pop-up 
only according  to the poorman parameter and/or to the end of the quota 
of  the every  user ?

That's my directive askconfirmation
askconfirmation : /usr/bin/pknotify   --destination 
$PYKOTAJOBORIGINATINGHOSTNAME:7654     --timeout 120   --confirm 
"Bonjour $PYKOTAUSERNAME.\n\nVous souhaitez imprimer 
$PYKOTAPRECOMPUTEDJOBSIZE page(s). Cela vous coutera 
$PYKOTAPRECOMPUTEDJOBPRICE credits.\n\nPour information, il vous reste 
$PYKOTABALANCE credits avant cette impression.\n\nConfirmez vous 
l'impression de ce document ?"

Think you for you answer.
Joël Tréhard
IUFM  Caen

headers

Jerome Alet | 10 Jul 15:48

Re: Pykoticon

On Thu, Jul 10, 2008 at 03:40:10PM +0200, joel.trehard wrote:
> GoodAfternoon
> 
> I have a problem on pykoticon.  When 2 users want to print,  the user 2 
> must waiting  the answer on the pop-up of the user 1 to see appearing 
> his pop-up.   It slows down and a user who  forgets to confirm,  stop  
>   the   others users.

You can use the --timeout' command line option for pknotify to handle
this (not perfect, though).

I don't see a solution with the way PyKota is currently written.
This is planned for v2.0 though, where pknotify/PyKoticon will
be launched based on subscriptions to job related events.

> Another thing,  is  there  a solution   to see appearing  this pop-up 
> only according  to the poorman parameter and/or to the end of the quota 
> of  the every  user ?
> 
> That's my directive askconfirmation
> askconfirmation : /usr/bin/pknotify   --destination  ...

This one is easy to do.

Just define either the askconfirmation or overwrite_jobticket) directive :

askconfirmation : /usr/local/bin/yourscript.sh

then have your shell script either launch pknotify with the previously
defined parameters, or immediately print CANCEL on its stdout,

(Continue reading)