Re: [api-dev] AWT TREE: OOoBasic version of the ScriptSelector example

2007-09-24 Thread Juergen Schmidt

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]



Re: [api-dev] AWT TREE: OOoBasic version of the ScriptSelector example

2007-09-22 Thread Mathias Bauer
Laurent Godard wrote:

 Hi
 
 This will be fixed for OOo 2.4. So please be aware that an incompatible
 change to the interface is comming.
 
 Why incompatible ?
 Mark it as deprecated, no ?
 
 What about people starting using this and seeing their code not working 
 anymore after a new OOo Version. We should avoid this

This is an unpublished interface. That means that people using it must
be aware of at least some small changes in the near future. Otherwise we
don't need to distinguish between published and unpublished interfaces.

People using unpublished interfaces should subscribe to the
interface-announce mailing list where all changes are reported. A change
like the one mentioned by Christian is so trivial that it shouldn't be a
big problem. And the interface was introduced in 2.3 so only a few
people will be using it at all. And if they are subscribed to this list
they now know that there will be this small change.

Ciao,
Mathias

-- 
Mathias Bauer (mba) - Project Lead OpenOffice.org Writer
OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
Please don't reply to [EMAIL PROTECTED].
I use it for the OOo lists and only rarely read other mails sent to it.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [api-dev] AWT TREE: OOoBasic version of the ScriptSelector example

2007-09-22 Thread Bernard Marcelly

Message de Mathias Bauer  date 2007-09-22 10:38 :

Laurent Godard wrote:


Hi


This will be fixed for OOo 2.4. So please be aware that an incompatible
change to the interface is comming.

Why incompatible ?
Mark it as deprecated, no ?

What about people starting using this and seeing their code not working 
anymore after a new OOo Version. We should avoid this


This is an unpublished interface. That means that people using it must
be aware of at least some small changes in the near future. Otherwise we
don't need to distinguish between published and unpublished interfaces.

People using unpublished interfaces should subscribe to the
interface-announce mailing list where all changes are reported. A change
like the one mentioned by Christian is so trivial that it shouldn't be a
big problem. And the interface was introduced in 2.3 so only a few
people will be using it at all. And if they are subscribed to this list
they now know that there will be this small change.

Ciao,
Mathias



Hi,
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

Same for the service com.sun.star.sheet.Shape

Regards
  Bernard

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [api-dev] AWT TREE: OOoBasic version of the ScriptSelector example

2007-09-22 Thread Frank Schönheit - Sun Microsystems Germa ny
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?


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.


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 :-\

Ciao
Frank

-- 
- Frank Schönheit, Software Engineer [EMAIL PROTECTED] -
- Sun Microsystems  http://www.sun.com/staroffice -
- OpenOffice.org Base   http://dba.openoffice.org -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [api-dev] AWT TREE: OOoBasic version of the ScriptSelector example

2007-09-20 Thread Christian Lippka - Sun Microsystems Germany

Andrew Douglas Pitonyak wrote:

Ariel Constenla-Haile wrote:


PS 2: though my English is very me-Tarzan-you-Jane, 

No, your English is much better than that.

isn't it wrong
Childs as plural of Child, instead of Children? 

Children is the correct plural for Child.

The Java API uses
Children for the plural ( z.B. DefaultMutableTreeNode.allowsChildren ,
.children, .getAllowsChildren() ... ), OOo API Childs.




This will be fixed for OOo 2.4. So please be aware that an incompatible
change to the interface is comming.

Regards,
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [api-dev] AWT TREE: OOoBasic version of the ScriptSelector example

2007-09-20 Thread Laurent Godard

Hi


This will be fixed for OOo 2.4. So please be aware that an incompatible
change to the interface is comming.


Why incompatible ?
Mark it as deprecated, no ?

What about people starting using this and seeing their code not working 
anymore after a new OOo Version. We should avoid this


Laurent

--
Laurent Godard [EMAIL PROTECTED] - Ingénierie OpenOffice.org - 
http://www.indesko.com
Nuxeo Enterprise Content Management  http://www.nuxeo.com - 
http://www.nuxeo.org

Livre Programmation OpenOffice.org, Eyrolles 2004-2006

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[api-dev] AWT TREE: OOoBasic version of the ScriptSelector example

2007-09-07 Thread Ariel Constenla-Haile

Hello people

I continue working with the tree control.
As a first result of a fast reading of the IDL, I have adapted the
Scripting Framework example on the Developer's Guide
OpenOffice.org_2.3_SDK/examples/DevelopersGuide/ScriptingFramework/ScriptSelector/ScriptSelector

You can find it here:
http://www.arielconstenlahaile.com.ar/ooo/docs/TREE_CONTROL.zip

I did it very fast, so I'm not completely sure if it works 100% (I
didn't test the Scripting Framework API) and the code is not very clean.
You can test it on your own.

And of course there will be some Java examples implementing the
XTreeDataModel.

Once I'm sure I understand everything (besides the differences, it's not
so difficult if you're used to the JTree), I hope I could write a short
tutorial on this topic (in Spanish and English): I have recived ten
mails yesterday from my web site asking how to use it, they were
surprised that this feature is available but there is no documentation
at all (no API ref., and most important: no OOo Help at all!!!).

In this situation, the common user with no programming knowledge at all
gets disappointed when he/she can draw a control on the Basic IDE, but
it has no functionality at all (not even a sample tree drawn in the
control, as in the NetBeans IDE).

Bye and thanks.

PS 1: do you know who wrote the ScriptSelector, so I give him/her the
credit in my HOW-TO?

PS 2: though my English is very me-Tarzan-you-Jane, isn't it wrong
Childs as plural of Child, instead of Children? The Java API uses
Children for the plural ( z.B. DefaultMutableTreeNode.allowsChildren ,
.children, .getAllowsChildren() ... ), OOo API Childs.


--
Ariel Constenla-Haile
La Plata, Argentina

[EMAIL PROTECTED]
[EMAIL PROTECTED]

http://www.arielconstenlahaile.com.ar/ooo/



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [api-dev] AWT TREE: OOoBasic version of the ScriptSelector example

2007-09-07 Thread Andrew Douglas Pitonyak

Ariel Constenla-Haile wrote:


PS 2: though my English is very me-Tarzan-you-Jane, 

No, your English is much better than that.

isn't it wrong
Childs as plural of Child, instead of Children? 

Children is the correct plural for Child.

The Java API uses
Children for the plural ( z.B. DefaultMutableTreeNode.allowsChildren ,
.children, .getAllowsChildren() ... ), OOo API Childs.


--
Andrew Pitonyak
My Macro Document: http://www.pitonyak.org/AndrewMacro.odt
My Book: http://www.hentzenwerke.com/catalog/oome.htm
Info:  http://www.pitonyak.org/oo.php
See Also: http://documentation.openoffice.org/HOW_TO/index.html

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]