Re: [api-dev] Unpublished UNO API

2006-08-28 Thread Mathias Bauer
Bjoern Milcke wrote: Hi Jürgen, I am always happy when one of my demo components developed for StarOffice 6.0 (before OO.org) work with StarOffice 8 as well. I think it can be a good reason for customers to switch to SO/OO.org using our API (with java for example) because they know that

Re: [api-dev] Unpublished UNO API

2006-08-23 Thread Jürgen Schmidt
Hi Ingrid, Ingrid Halama wrote: Hi Jürgen, all, Jürgen Schmidt wrote: Frank Schönheit - Sun Microsystems Germany wrote: Hi Stephan, Second, we neither have nor plan to have in place a mechanism to detect that some UNO component/OOo extension uses an old revision of some unpublished API.

Re: [api-dev] Unpublished UNO API

2006-08-23 Thread Bjoern Milcke
Hi Jürgen, I am always happy when one of my demo components developed for StarOffice 6.0 (before OO.org) work with StarOffice 8 as well. I think it can be a good reason for customers to switch to SO/OO.org using our API (with java for example) because they know that the implementation of

Re: [api-dev] Unpublished UNO API

2006-08-22 Thread Ingrid Halama
Hi Jürgen, all, Jürgen Schmidt wrote: Frank Schönheit - Sun Microsystems Germany wrote: Hi Stephan, Second, we neither have nor plan to have in place a mechanism to detect that some UNO component/OOo extension uses an old revision of some unpublished API. That is, there will not be any

Re: [api-dev] Unpublished UNO API

2006-08-18 Thread Jürgen Schmidt
Frank Schönheit - Sun Microsystems Germany wrote: Hi Stephan, Second, we neither have nor plan to have in place a mechanism to detect that some UNO component/OOo extension uses an old revision of some unpublished API. That is, there will not be any warning if you deploy such a

Re: [api-dev] Unpublished UNO API

2006-08-18 Thread Stephan Bergmann
Frank Schönheit - Sun Microsystems Germany wrote: Hi Stephan, Second, we neither have nor plan to have in place a mechanism to detect that some UNO component/OOo extension uses an old revision of some unpublished API. That is, there will not be any warning if you deploy such a

[api-dev] public vs. published (was: [api-dev] Unpublished UNO API)

2006-08-18 Thread Frank Schönheit - Sun Microsystems Germa ny
Hi Stephan, See http://www.martinfowler.com/ieeeSoftware/published.pdf for the source of that term. Interesting reading, thanks for the pointer. However, I think Fowler uses the term published in a different meaning than we do. While he doesn't clearly define the terms and their difference,

[api-dev] Unpublished UNO API

2006-08-17 Thread Stephan Bergmann
Hi all, there are two issues with unpublished UNO API I want you (as both an API author and consumer) to be aware of: First, if you release some unpublished API that is badly needed by UNO component/OOo extension writers to get their job done, chances are that those writers will use your

Re: [api-dev] Unpublished UNO API

2006-08-17 Thread Laurent Godard
Hi Stefan there are two issues with unpublished UNO API I want you (as both an API author and consumer) to be aware of: thanks for this reminder :-) First, if you release some unpublished API that is badly needed by UNO component/OOo extension writers to get their job done, chances are

Re: [api-dev] Unpublished UNO API

2006-08-17 Thread Jürgen Schmidt
Laurent Godard wrote: Hi Stefan there are two issues with unpublished UNO API I want you (as both an API author and consumer) to be aware of: thanks for this reminder :-) First, if you release some unpublished API that is badly needed by UNO component/OOo extension writers to get their