Difference between revisions of "Uno/Specifications"

From Apache OpenOffice Wiki
< Uno
Jump to: navigation, search
m (Claims)
 
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
#REDIRECT [[:Category:Uno:Spec]].
+
==Abstract Uno Specifications==
 +
The abstract Uno specifications are the blue prints for all concrete [[Uno#Uno implementations|Uno implementations]] (e.g [[Uno/Binary|Binary Uno]], [[Uno/Java|Java Uno]], [[Uno/Cpp|C++ Uno]]).
 +
<noinclude>[[Category:Uno]]</noinclude>
 +
 
 +
==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===
 +
<DPL>category=Uno
 +
category=Spec</DPL>
 +
* [http://udk.openoffice.org/common/man/draft/synch_thread.html Multi Threading Spec.]
 +
* [http://udk.openoffice.org/common/man/lifecycle.html The Object Life Cycle]
 +
* [http://udk.openoffice.org/common/man/execution.html The Execution Model]
 +
* [http://udk.openoffice.org/common/man/typesystem.html The Type System]
 +
* [http://udk.openoffice.org/common/man/componentmodel.html Components]
 +
* [http://udk.openoffice.org/cpp/man/spec/uris.html URIs]
 +
* [http://api.openoffice.org/docs/common/ref/com/sun/star/module-ix.html IDL Reference]

Latest revision as of 14:50, 20 June 2008

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

Personal tools