Yvan Barthélemy wrote: > 2006/10/22, Mathias Bauer <[EMAIL PROTECTED]>: >> >> You are right. Perhaps it's time to create one? >> > > Probably but : > * I have no experience yet with UNO. > * I am not sure about what benefits UNO will bring > * I don't know where to start and I have no idea how to achive this > > However I am interested doing it.
That's fine. :-) I'm afraid that just implementing the print dialog won't be enouh as we also have to change the code using it. This means code in VCL but IIRC mainly in sfx2 and the applications. As this is an area I'm very interested to refactor (as our crash report statistics shows some very "popular" though hard to fix crashes there) we could think about a joint effort. I will find out which code we need to change and if we have the resources to do it. I won't be able to do this before next week because I'm on vacation this week. As an alternative the UNO printer dialog could be introduced into VCL only, below the C++ class we are currently using, but I have my doubts that this will be possible. Besides that the implementation of the print dialog as a UNO component is not more complicated than writing a "normal" C++ class. A UNO component is just a C++ class with a defined interface and some mandatory methods for its UNO contracts that nowadays can be implemented using code generators, nothing magic or complicated. The implementation of a UNO component starts with its interface design. This can be done by looking on the current PrinterDialog class definition of our printer dialog and of course also on possible additional requirements the Apple dialog has. Ciao, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
