Gerhard Schuster wrote:
Hi Juergen,
you sound hurt.
If I've written anything that hurt your feelings please forgive me.
no problem, sometimes it sounds a little bit to strange for Sun from my
perspective and i don't like this argumentation because often people
don't know the details or the facts behind. Anyway don't care about it.
I don't intend to accuse you of anything but having done great work
with OpenOffice.
JS> mmm, a useless statement with out any concrete examples, isn't it
I'm happy to provide the example, but don't know how to do it. Do you
want me to attach the Eclispe project as a zip file?
Why not? I plan to provide all SDK examples as NetBeans projects. Why
not for Eclipse?
JS> Sometimes i have the feeling that it is regardless what Sun is doing
JS> somebody will always complain about it. If we do more for NetBeans than
JS> Eclispe than it is wrong if we prefer Java more than Python it is wrong.
JS> If Sun sponsor Sun open source projects with a lot of money it is wrong
JS> and Sun is bad ... I don't understand it.
If your own IDE is NetBeans and your language is Java it is just
narural that your Product is easier to use in NetBeans and Java.
JS> sorry but that is again nonsense. Of course there are API's where we
JS> have better API's today but they are not out dated. I am sure that all
JS> of them work.
I used the Java examples to design my own code. Then I had a problem
and I posted my code and one of your core developers told me off,
because I used System.exit() in my code. He saied that according to a
golden rule of OpenOffice one never shall use System.exit()
mmh interesting, but that is not true. We use System.exit because of
some technical reasons based on garbage collection and bridges etc.
Maybe it is obsolete today, i have to check it. But at least in the past
it was necessary. I wouldn't call it out dated.
But it happens that all of the Java examples of the DevelpersGuide use
System.exit().
This is what I mean with out dated.
Also if there are better APIs now this also qualifies for the examples
being outdated in my opinion.
for most of the API's we don't have never ones. I is more that we have
additional API's for some things that make the life easier. And of
course not everything is documented yet but that is a complete different
problem and it will change.
The examples are the only source where people can see how to work with
the API.
sure
Juergen
JS> Anyway I will think about a place where we can host this kind of helper
JS> libraries. I can't promise anything but can at least offer to host it in
JS> the API project where you would have cvs access and can create your own
JS> web page under the umbrella of the API project that would be of course
JS> a good place for it. By the way the Eclispe plugin source code is hosted
JS> there as well
Ok, I would setup a web page.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
