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

List:       kde-core-devel
Subject:    Re: New KDE printing system
From:       Michael Goffioul <goffioul () imec ! be>
Date:       2001-02-28 16:12:37
[Download RAW message or body]

> how about that solution:
> 1)
> make Construktor, Destructor and Copyconstruktor protected and generate
> everything by a Factory or a private static KPrinter method (or both)
>
> or different from that
> 2)
> give the class a static data pointer
> which is implicidly shared between the instances.
> the latter has
> the disadvantage of accessing the same data with different tasks and
> threads
> and the advantage of looking consistent with QPrinter ;-)

That's what I proposed in another mail. Make the KPrinter object have an
implementation object created by the factory and shared by various KPrinter
object. Of course it is better to only have one KPrinter accessing the shared
data, but I don't think developers are creating several QPrinter objects at
the same time anyway. The advantage is to have a KPrinter class that can be
used as QPrinter class.

Difficult to find the "perfect solution" (flexible, powerful, and still 100%
compatible.

Michael.

--
------------------------------------------------------------------
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
------------------------------------------------------------------

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