Frank Schönheit - Sun Microsystems Germany wrote:
Hi Bernard,
I don't want to start a troll, but the service
com.sun.star.sheet.Spreadsheet is _unpublished_ since a long time, see
<http://api.openoffice.org/docs/common/ref/com/sun/star/sheet/Spreadsheet.html>
Hmm, okay, and what does this tell us?
i would say that it is more a bug because this service is really old,
isn't it.
The change mentioned by Christian would be of course a valid change and
fits in the current existing definition of published/unpublished API's.
The concept of unpublished was introduced for cases such as the
Childs/Children: The interface has a flaw, which can be fixed easily,
and does not require substantial effort for the clients if fixed.
I much prefer doing this small innocent fix for the next release, at the
cost of some scripts to be adjusted, over being annoying by the current
spelling error for the next *years* (finally, it looks somewhat
unprofessional, doesn't it?).
Yes, we don't have a mechanism in place which ensures that APIs become
published after a while, which leads to APIs such as the one you
mentioned. On the other hand, I doubt that anybody will do a severe
incompatible change to Spreadsheet or Shape, I think people are
responsible enough to recognize that this would be a bad idea, after the
API has been there for years.
but of course we strongly recommend that API's that are introduced to be
used by clients ... should be published after 2-3 releases.
Ok, we have also no clear concept for private API's which results in
some types that are more or less private and that will remain as
unpublished. But anyway it should be a minority.
On yet another hand, I personally would not like to declare any service
as published as long as this forbids even minor and innocent changes
which do not cause any trouble to any client, but that's another story
which I perhaps should not start again, here :-\
thanks, but you should sometimes switch the glasses and should take a
look on the whole thing from a user perspective. We have both users and
developers and from a user perspective it is a cool feature to have
compatible API's. And please don't misunderstand me i can also
understand our developers and that is the reason why we again try to
find a working or practicable compromise.
Anyway it is on my todo wish list to check frequently our unpublished
API's and i will ask for reasons why they are not published or why they
should be remain unpublished ;-)
Juergen
Ciao
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
