Yvan Barthélemy wrote:
Thanks for the answer Jan,
In fact, what I want to do is to provide similar mechanism in svtools
in order to implement a native printing dialog instead of the one
provided by svtools.
My goal is to add an aqua directory where I will put Aqua
Implementation specific sources. But I don't know how should I do to
compile these one rather than the default one.
Pardon, but I think that is not a good idea. It is true that there are
some platform dependent files left in svtools for historical reasons,
however the better approach to do a native dialog is like the file
dialog already does, that is via an own UNO service. We should strive to
contain system abstraction to as few modules as possible.
Also replacing the print dialog may not be as easy as it sounds since
the PrinDialog objects are currently passed around in the application as
a kind of container for print settings.
Just my 2 cents, pl
--
If you give someone a program, you will frustrate them for a day;
if you teach them how to program, you will frustrate them for a lifetime.
-- Author unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
