Hi Carsten
Carsten Klein wrote:
thanks for your initiative.
Thanks for your comment too.
The replies he got where rather non elaborate and leave open many questions.
And, reviewing the answers being made, I must state, that, alas, we will
have to dig deep into the "mud", hoping that the UNO core API is well
documented so that we would not have to re-engineer based on the existing
sources.
I was hoping for a more usefull answer too - also for others who wants
to start creating an OpenOffice.org application.
This, however would add to our progress the overhead of adopting said
components to make them re-usable on the broader scale. However, I have
not looked into the code for appox. 3-4 yrs. therefore I cannot know
whether they have cleaned it up and made it more black-box like, where
backend and frontend are positively divided into separate components,
provably also providing some kind of (pluggable) middle ware.
We could hope they have. I haven't read any developer documentations in
the last four years either.
An extension
facility they seem to already have included with their existing OOo
solution, however, apart from templates and scripts and the likes I wonder
whether this extension mechanism has its foundation in the UNO core?
Maybe - I hope to have a better overview when I have read/skimmed the
documents you have linked to your mail "Link Collection to Available OOo
Developer Documentation".
Any hints from SUN officials in that direction would be most appreciated.
Yes - maybe one of us should try and ask on the developer IRC channel.
And, regarding the one reply stating that, based on UNO one could
implement the lot of the application alone, well, it stands for itself -
reinvent the wheel.
I think that we might have a good start collecting links to documentation
that we feel we would require for the development and collect them for
example in the wiki or in some other document.
Yes - let's start with that. See
http://wiki.services.openoffice.org/wiki/OOPM_Project_Documents
I will search for development related links incl. API documentation and so
on and post those links on this list for now.
Thanks for the list - again ;v)
The most enjoyable greetings
--
Claus Agerskov ###= Analyze OpenOffice.org
Project Owner ##== Requirements Project Management Tool
c...@openoffice.org ==== Design/model Subproject
==== Implement http://oopm.openoffice.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@oopm.openoffice.org
For additional commands, e-mail: dev-h...@oopm.openoffice.org
