Juergen Schmidt wrote:
The given XView interface is effectively *only* implemented in the
toolkit module, and chances that it's implemented outside the OOo code
base are rather low (since all the code around it does not really allow
for pure UNO components outside the OOo code, but that's
Juergen, Ariel,
to make it short, i would support you to add it. If we make the change
we should start with a new wiki page to document the change and a
migration path even if it would be trivial.
okay. What location do you suggest? Do we already have an entry point in
the wiki to the
Hi Ariel,
I didn't have time to understand the reasons
given for adding a FilterOperator2, carrying with it a TableFilterField2 and
a
XSheetFilterDescriptor2; but the names just tell me there was no agreement.
Well, the agreement really was that for a major release, any API changes
can be
Frank Schönheit - Sun Microsystems Germany wrote:
Juergen, Ariel,
to make it short, i would support you to add it. If we make the change
we should start with a new wiki page to document the change and a
migration path even if it would be trivial.
okay. What location do you suggest? Do we
Hello Frank,
On Monday 29 June 2009, 07:43, Frank Schönheit - Sun Microsystems Germany
wrote:
Hi,
would adding a method to an existing published interface be considered
too incompatible for a 3.2 release?
In particular, css.awt.XView has a method setZoom, but not a getZoom,
which I'd like
Ariel Constenla-Haile wrote:
Hello Frank,
On Monday 29 June 2009, 07:43, Frank Schönheit - Sun Microsystems Germany
wrote:
Hi,
would adding a method to an existing published interface be considered
too incompatible for a 3.2 release?
In particular, css.awt.XView has a method setZoom, but
