Re: [api-dev] Unfortunate document event name - how to fix it?

2009-05-14 Thread Robert Vojta
On Wed, May 13, 2009 at 7:14 PM, Mathias Bauer nospamfor...@gmx.de wrote: Hi Mathias, The best documentation is an API that doesn't need one. This deals with the fact that people don't like to read documentation. Having speaking names for events is a good thing per se, not just some language

Re: [api-dev] Unfortunate document event name - how to fix it?

2009-05-14 Thread Paolo Mantovani
Hi, Robert Vojta ha scritto: On Wed, May 13, 2009 at 7:14 PM, Mathias Bauer nospamfor...@gmx.de wrote: Hi Mathias, The best documentation is an API that doesn't need one. This deals with the fact that people don't like to read documentation. Having speaking names for events is a good

[api-dev] Proposal: first convention to discuss API changes in the future

2009-05-14 Thread Juergen Schmidt
Hi, i would like to suggest that we start new threads to discuss proposals for API changes with a subject API.CHANGE-ver: e.g. API.CHANGE-4.0: That allows to search all changes quite easy and to get a fast overview. If nobody disagree i will put it on the wiki page as one

Re: [api-dev] Exploring OpenOffice.org API through MindMaps

2009-05-14 Thread Mathias Bauer
RKVS Raman wrote: Hi, Recently I started this small activity of converting the services and interfaces defined in OpenOffice.org API to XMind Mindmaps. Have started hosting it at the following blog. http://ooomindmaps.blogspot.com/ Hope it is useful to OpenOffice.org folks for

Re: [api-dev] Proposal: first convention to discuss API changes in the future

2009-05-14 Thread Ariel Constenla-Haile
Hello Juergen, On Thursday 14 May 2009, 06:44, Juergen Schmidt wrote: Hi, i would like to suggest that we start new threads to discuss proposals for API changes with a subject API.CHANGE-ver: e.g. API.CHANGE-4.0: is this ver the current version where the to-be-changed API

Re: [api-dev] Proposal: first convention to discuss API changes in the future

2009-05-14 Thread Juergen Schmidt
Ariel Constenla-Haile wrote: Hello Juergen, On Thursday 14 May 2009, 06:44, Juergen Schmidt wrote: Hi, i would like to suggest that we start new threads to discuss proposals for API changes with a subject API.CHANGE-ver: e.g. API.CHANGE-4.0: is this ver the current version where

Re: [api-dev] Proposal: first convention to discuss API changes in the future

2009-05-14 Thread Ariel Constenla-Haile
Hello Juergen, On Thursday 14 May 2009, 10:34, Juergen Schmidt wrote: i would like to suggest that we start new threads to discuss proposals for API changes with a subject API.CHANGE-ver: e.g. API.CHANGE-4.0: is this ver the current version where the to-be-changed API

Re: [api-dev] Unfortunate document event name - how to fix it?

2009-05-14 Thread Ariel Constenla-Haile
Hello Matthias, On Tuesday 12 May 2009, 06:06, Matthias B. wrote: That you even consider removing this event is exactly the lack of commitment to compatibility I have critized in the long thread about OOo quality recently. I'm not sure what you're meaning with lack of commitment to

Re: [api-dev] Proposal: first convention to discuss API changes in the future

2009-05-14 Thread Juergen Schmidt
Ariel Constenla-Haile wrote: Hello Juergen, On Thursday 14 May 2009, 10:34, Juergen Schmidt wrote: i would like to suggest that we start new threads to discuss proposals for API changes with a subject API.CHANGE-ver: e.g. API.CHANGE-4.0: is this ver the current version where the

Re: [api-dev] Unfortunate document event name - how to fix it?

2009-05-14 Thread Ariel Constenla-Haile
Hello Mathias, On Wednesday 13 May 2009, 14:14, Mathias Bauer wrote: The best documentation is an API that doesn't need one. This deals with the fact that people don't like to read documentation. Having speaking names for events is a good thing per se, not just some language aesthetics. +1

Re: [api-dev] Proposal: first convention to discuss API changes in the future

2009-05-14 Thread Ariel Constenla-Haile
Hello Juergen, On Thursday 14 May 2009, 11:35, Juergen Schmidt wrote: is there already a general agreement about when API changes will be allowed? only major (for example only OOo 4.0, OOo 5.0), or also minor (OOo 3.3, OOo 3.4), or even micro (OOo 3.2.1)? mmh, i think yes, we should take

Re: [api-dev] Proposal: first convention to discuss API changes in the future

2009-05-14 Thread Frank Schönheit - Sun Microsystems Germany
Hi Ariel, It makes sense that if someone adds a new member, the @since tag is also added, and autodoc respects it; not the case nowadays: cf. http://svn.services.openoffice.org/opengrok/xref/DEV300_m47/offapi/com/sun/star/accessibility/AccessibleRelationType.idl#117 vs.

Re: [api-dev] Proposal: first convention to discuss API changes in the future

2009-05-14 Thread Frank Schönheit - Sun Microsystems Germany
Hi Ariel, done, http://www.openoffice.org/issues/show_bug.cgi?id=101932 Seen and ttargeted it, thanks. another thing that has to be fixed (if changes to published API are going to be allowed) is one of the sdk tools that won't let you do that (now I can't recall if it was the idlc that

Re: [api-dev] Proposal: first convention to discuss API changes in the future

2009-05-14 Thread Ariel Constenla-Haile
Hello Frank, On Thursday 14 May 2009, 15:12, Frank Schönheit - Sun Microsystems Germany wrote: Hi Ariel, is there already a general agreement about when API changes will be allowed? In my understanding, there was no definitive answer to this question in the thread which discussed it.

Re: [api-dev] Proposal: first convention to discuss API changes in the future

2009-05-14 Thread Frank Schönheit - Sun Microsystems Germany
Hi Ariel, I have several changes in mind for the awt module (including my enhanced menu API); this module has several non-senses (like a top window not being a window, and the like). I volunteer myself for fixing the ones in my list (once API changes are allowed). Ah, great, that's most