Stephan Bergmann wrote:
On 01/27/09 09:13, Mathias Bauer wrote:
BTW: a keyword unpublished would come in handy here as it could become
the hyperlink itself! It seems we did it the wrong way. Not only because
of this but also because (as usual!) not the standard way of doing
things (the
Hi Ariel,
Means: If existing API is unpublished, then IMO we should extend it
incompatibly, if it becomes a little better / less ugly thereby
I've found no way to change its ugliness without breaking API design rules.
Don't know what you have in mind.
Yes, doing it completely right
Ariel Constenla-Haile wrote:
Hello Juergen,
On Sunday 18 January 2009 09:50, Juergen Schmidt wrote:
I know my design is awful and looks complicated, but that's the best I
could imagine in the current OOo API design/situation; vid.
Hi Ariel,
first: no offense intended with my mail. I perfectly understand the
difficulties of extending an existing ... suboptimal API ...
There is one problem with your
solution, I don't want that we change an interface (XMenuExtended)
incompatible which has been available since four
Hello Frank,
On Sunday 18 January 2009 17:08, Frank Schönheit - Sun Microsystems Germany
wrote:
Hi Ariel,
first: no offense intended with my mail. I perfectly understand the
difficulties of extending an existing ... suboptimal API ...
There is one problem with your
solution, I don't
And it *can* even be discussed if css.awt.MenuBar and css.awt.PopupMenu are
*really* published: do not forget they were added after I open issues
http://api.openoffice.org/issues/show_bug.cgi?id=82512
http://api.openoffice.org/issues/show_bug.cgi?id=82514
my mistake when copypaste: i82514
Hello Frank,
On Saturday 17 January 2009 19:08, Frank Schönheit - Sun Microsystems Germany
wrote:
Hi Carsten,
With the following we work have been enhanced this API, by extending
it with new interfaces.
+com.sun.star.awt.XMenuExtended2
interface XMenuExtended2
{
