Hi Jürgen,
Juergen Schmidt escribió:
Juergen Schmidt escribió:
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?
that is a great idea :-)
Since the JDK came with its examples as NetBeans Projects, I was
wondering why wouldn't OOo SDK do the same (...well, reading
sometimes some mails in [EMAIL PROTECTED] against Sun, I thought you
had your concerns, and didn't want people to start complaining also
about this).
As I am in my Southern-hemisphere-summer-of-code, if I can help with
this, let me know: I have already turn some SDK examples into NetBeans
Projects.
cool, let me know which examples do you have already converted.
I'm not at home now, so I can't recall... but I have severals, last one
I've made was the amazing EmbeddedObject example
(/examples/java/EmbedDocument/EmbeddedObject), the GUI examples (BTW,
one of them crashes OOo: UnoMenu.java, I had the same problem when
closing a top window, IIRC I had to dispose both the XFrame and the
XWindow to prevent the crash...not sure, I will have to debug it), the
Filter examples, the Components examples, etc.
I had some questions:
* In some cases, I did them with an older version of the plug-in, not
using the central registration class IIRC. Should I change the examples
to "make them fit" to the latest plug-in version?
* although the plug-in does not support NB 6.0 I'm using it: it has
several enhancements, among them it shows all *unused* code. This way I
could see that some SDK examples need some clean-up. Should I clean-up
the code, or just turn them into a NB Proj. as they are?
* naming issues: what should be the package name, the extension
identifier, etc? For packages, I tried to use, when possible, the SDK
file hierarchy: for example, for
sdk/examples/DevelopersGuide/GUI
I used
org.openoffice.sdk.examples.devguide.gui
but I'm not sure if it is a good idea: the package name turns out too
long :-(
My idea is to provide the projects as zip files. I will provide a place
in the cvs section of the api project. I would also like to have some
docu for each example in the Wiki.
how should the docu be? a simple introductory comment referencing where
in the Dev's Guide to find the technical explanations? or something more
complete?
The idea is to put them under
http://wiki.services.openoffice.org/wiki/API/Samples/Java and there
under the appropriate category. The wiki page will link later to the zip
file. The docu can be shared for Eclipse projects as well.
Does that make sense?
why not shipping them with the SDK, as the JDK does?
I'm not sure if the wiki is the best place: for example, I just counted
two developers asking questions in the extensions mailing list about the
complex toolbar controls, so I suppose not many developers are trying
this amazing feature, and think that the reason why not many
[extension's] developers know Carsten Driesner's tutorials is because
they are quite "hidden" in the wiki; and on the other hand, the SDK
example is in Cpp (of course not very accessible for developers not
knowing Cpp).
Do developers really search in the Wiki for documentation, or just use
the SDK? I tend to think this last one...
Regards
Ariel.
--
Ariel Constenla-Haile
La Plata, Argentina
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.arielconstenlahaile.com.ar/ooo/
"Aus der Kriegsschule des Lebens
- Was mich nicht umbringt,
macht mich härter."
Nietzsche Götzendämmerung, Sprüche und Pfeile, 8.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
