Hi,
yes, using attributes is highly recommended!
Besides that it seems that some attributes are already part of one of
the property value sequences ("Collate" at least, IIRC). That should be
checked.
But why should we call this "XPrinterPicker"? Perhaps we should devide
this interface into two, one that contains all attributes and another
one derived from the first one containing the dialog specific parts
(parent and whatever else). This way we also get an interface for an
object we can use to transport printer settings (instead of using the
whole dialog).
Ciao,
Mathias
Christian Lippka - Sun Microsystems Germany wrote:
> Hi C.,
>
> just a small comment. Do you know about [attributes] in idl? This way
> you do not have to specify the get/set methods by hand.
>
> Regards,
> Christian
>
> Caolan McNamara wrote:
>> Any comments on this initial attempt to make an idl for the printer
>> dialog to form a basis of uno-ifying the dialog ?
>>
>> Might be ok to remove the FromTo stuff, we have references to the old
>> version of this spread throughout our existing code, but the current
>> dialog doesn't actually implement it so it never kicks in.
>>
>> C.
>>
>>
>> ------------------------------------------------------------------------
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
Mathias Bauer (mba) - Project Lead OpenOffice.org Writer
OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
Please don't reply to "[EMAIL PROTECTED]".
I use it for the OOo lists and only rarely read other mails sent to it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
