Ian Laurenson wrote:
I definitely would like to be part of such a discussion.
Some comments/ideas in-line:
On Fri, 2005-09-09 at 16:04 +0200, Jürgen Schmidt wrote:
Hi,
we plan an open discussion around the programmablity features of
OpenOffice.org. I am not 100% sure if we can arrange everything in time.
I am on vacation the next two weeks, so you should take a look to the
conference program for more details about time and location.
You can also send me an email if you are interested and i will contact
you short notice before the conference.
**************************************************************
Open discussion about OpenOffice.org programmability features
We invite you to an open discussion about the programmability features
of OpenOffice.org. The intention of this discussion is to get direct
feedback about the current situation and the existing features and to
get ideas what we can do to make it more attractive and easier to
develop for OpenOffice.org. We would like to address several topics in
this discusson:
- what can we do to increase the developer community (related to
extension, e.g. add-ons, macro libraries, ...)
* Core developers concentrate on providing components for macro
developers. For example having docked/floating windows accessible by
macros was seen as a low priority and relegated to 2.0.1 maybe. I would
have liked to seen these core features given a higher a priority.
me too, but sometimes others constraints dictate the priorities ;-)
* A system for people to donate funds for a feature and for developers
to be able to 'claim' funds having implemented a requested feature.
good idea
* A standard and easy way for people to search for, download and install
extensions. Coupled with this is an easy way for extension developers to
upload their work. A system for marking extensions as having been
checked. [I have had several posts on this topic before]
The point is that we need more core technology to provide for exmaple a
good and consistent versioning concept for UNO packages (extensions)
with a consistent updae mechanism (platform indpendent naturally). And
when we have a consistent process in place then and only then i would
like to start to prepare a extension base. Only when it works it would
be usefuil for our customers and users. But we are working or better
thinking about it and we will come with a proposal soon.
- how can we increase and improve our code snippet base on
api.openoffice.org (more snippets, ensuring quality, extend to complete
examples, ...)
I am guilty of having setup a separate system - a wiki:
http://ext.openoffice.org.nz/
the idea is good and a wiki is also good. The key point is that we
should combine all our efforts to work together on one central entry
point for developers. Maybe we can combine a wiki for docu, tips
andtrciks with a snippet/example base and in the future an extension
base for final and approved extensions.
My rationale for doing so was:
* Ease of updating the code snippets
* Ease of searching the code snippets
* Ease of cross referencing between code snippets
* Ease of mingling explanatory text
* Ease of interaction
Having said that, not very many people have contributed to the wiki.
- who can help to prepare developer documentation for different
abstaction levels and skills. The current Developer's Guide is more for
experts and we need further documentaiton for beginners. We need
specific documentation for Basic users as well as for Java, C++, CLI or
Python. Different kind of documentation reaching from best practise,
over short 5-pagers describing a single aspect to complete guides for
larger API areas (e.g. writer API)
My wiki was an attempt to try and fill, at least some of, this need. I
am willing to put time and effort into a more officially recognised
system.
perfect, i am looking forward to the conference to talk with you
- Juergen
We, that are Juergen Schmidt (project lead of the API project) and
Stephan Bergmann (project lead of the UDK project), are looking forward
to an open discussion with interested community members to share ideas,
start new collaborations with others and to drive this important
programmability aspect for OpenOffice.org forward.
Juergen + Stephan
Thanks, Ian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
