Hi Joerg,
Joerg Budischewski wrote:
Hi,
good news and a lot of (conceptual) work to do. Have fun with this :-).
You know us :-)
Some annotations:
* The link
http://udk.openoffice.org/common/man/spec/transparentofficecomponents.htm
Where did you find this link? Certainly needs to be ...html !
seem to be broken to me.
* A statement about the OLE-Bridge should be added (I think, it should
be a part of the URE).
It is not yet part of the URE, as there might be conflicts with the office.
* I would love to be pyuno a part of the URE, however I will just be
able to give eMail support, I won't have time to do source/packaging
modifications (the cws-overhead is simply too large for me to do
anything more beside pyuno maintenance in my very limited time I have
left for ooo currently ).
Don't worry. See below.
I guess, the main conceptual problem is, that one needs to bundle the
python runtime as it currently is in the office, which is not nice but
unchangeable as long as python community itself does not long for binary
compatibility as e.g. java does it.
Just let it be an implementation detail only, and it should be OK.
Beside this, it should be relatively easy to add pyuno to the ure, what
needs to be installed can be viewed in scp2/source/python.
Be aware, that this will be just the first version of the URE. In this
version it is probably not going to support any extensions mechanism
despite registering UNO components with "regcomp".
A later version is likely to support adding bridges, UNO packages etc..
So, I suggest to just wait until than and to provide pyuno as a UNO
package. This may make also sense for Java or remote or the ole bridge,
but let's see :-).
Just think about it, and please add the decision to the ure feature
document.
Hope the above would be fine for you.
Bye,
Joerg
Kay
Kay Ramme - Sun Germany - Hamburg wrote:
Dear OpenOffice.org and UNO friends,
I am pleased to announce that a sponsor, who is preferring to stay
anonymous, is supporting us to do the next step in modulizing the
OpenOffice.org office suite and to make its component model available
independently. That means, that we are going to factor out the highly
requested
Universal Network Objects (UNO)
into its own
Uno Runtime Environment (URE)
The URE allows the usage of UNO independently of the OpenOffice.org
productivity suite. UNO is OpenOffice.orgs underlying component model,
allowing language agnostic and remote transparent development of
add-ins, components and applications.
As UNO has already been designed with independence in mind, the URE is
mainly about bundling the appropriate libraries, executables etc. into
their own package. Please have a look at the URE proposal at
http://udk.openoffice.org/common/man/draft/standalone_uno_1_0.html
respectively the UNO homepage at
http://udk.openoffice.org
for details. The URE is planned to be released with OOo 2.0. As OOo
2.0 is already advanced in its development, the plan is to adapt OOo
to the URE with its next major (see
http://www.openoffice.org/issues/show_bug.cgi?id=50467) release.
XPCom, Bonobo and Mono fans might want to give UNO a try and see if we
can/want to bridge from one component model to another, to reach
higher overall interoperability.
Distro packagers might want to provide the URE (and the OOo SDK) with
their distro, not only as a prerequisite for past OOo 2.0 releases but
to enable people to develop UNO components.
Porters might want to port the URE, which is mainly a packaging task,
to their favorite platform.
Please send feedback to [email protected], respectively to
Stephan Bergmann ([EMAIL PROTECTED], UDK co-lead) or Kay Ramme
([EMAIL PROTECTED], UDK lead).
Kay
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
