Difference between revisions of "Uno"

From Apache OpenOffice Wiki
Jump to: navigation, search
m
(Rolling back, redirects work only on internal links ... :-()
Line 1: Line 1:
#redirect http://udk.openoffice.org/
+
Lead: [[KR|Kay Ramme]] Co-Lead: [[User:Sb|Stephan Bergmann]]
 +
 
 +
This is the [[Uno]] Wiki. '''Uno''' stands for '''Universal Network Objects'''.
 +
 
 +
[[Uno]] is the interface based component model of http://OpenOffice.org. [[Uno]] offers interoperability between programming languages, object models and hardware architectures, either in process or over process boundaries, as well as in the intranet or the Internet. Uno components may be implemented in and accessed from any programming language for which a Uno [[Uno#Uno_Implementations|implementation]] (AKA language binding) and an appropriate bridge or adapter exists.
 +
 
 +
It is planned to move most content from the [http://udk.openoffice.org http://udk.openoffice.org] pages into the Wiki. '''[[Uno/Effort/Migrate Documentation|You are welcome to help]]'''.
 +
Probably most interesting for many people is, what we are currently doing in Uno, which you can find in the [[Uno/Effort|efforts]] area. One of the bigger things is the [[Uno/Effort/Binary/Extend Threading-Model|extension to Binary Unos threading-model]].
 +
 
 +
The Uno Wiki organization is described in [[Uno/Meta/Organization]].
 +
 
 +
==Functional Overview==
 +
[[Image:Uno-Arc.jpg|center]]
 +
 
 +
{{:Uno/Modules}}
 +
{{:Uno/Efforts}}
 +
{{:Uno/Articles&Tutorials}}
 +
 
 +
==Things to be Done==
 +
* [[Uno/To-Dos]] - Uno To-Dos
 +
 
 +
{{:Uno/Spec}}
 +
 
 +
{{:Uno/Implementations}}
 +
 
 +
{{:Uno/Misc}}
 +
 
 +
{{:Uno/Terms}}
 +
 
 +
 
 +
[[Category:Project]]
 +
[[Category:Development]]

Revision as of 09:22, 14 December 2006

Lead: Kay Ramme Co-Lead: Stephan Bergmann

This is the Uno Wiki. Uno stands for Universal Network Objects.

Uno is the interface based component model of http://OpenOffice.org. Uno offers interoperability between programming languages, object models and hardware architectures, either in process or over process boundaries, as well as in the intranet or the Internet. Uno components may be implemented in and accessed from any programming language for which a Uno implementation (AKA language binding) and an appropriate bridge or adapter exists.

It is planned to move most content from the http://udk.openoffice.org pages into the Wiki. You are welcome to help. Probably most interesting for many people is, what we are currently doing in Uno, which you can find in the efforts area. One of the bigger things is the extension to Binary Unos threading-model.

The Uno Wiki organization is described in Uno/Meta/Organization.

Functional Overview

Uno-Arc.jpg

Modules

Things in progress - Efforts

Articles and Tutorials on Uno.

Things to be Done

Abstract Uno Specifications

The abstract Uno specifications are the blue prints for all concrete Uno implementations (e.g Binary Uno, Java Uno, C++ Uno).


Claims

Not every specification is required to be available for a particular Uno implementation. A specification either is

  • required - must be implemented by all Uno implementations, or
  • recommended - is recommended to be implemented, or
  • optional - may be implemented.

Specifications

Implementations

Misc

Terms

Personal tools