Content deleted Content added
m Removed malplaced space. |
m →External links: HTTP to HTTPS for SourceForge |
||
(11 intermediate revisions by 10 users not shown) | |||
Line 1:
{{Use dmy dates|date=September 2017}}
[[File:UNO API.png|thumb|UNO API]]
'''Universal Network Objects''' ('''UNO''') is the [[software component|component model]] used in the [[OpenOffice.org]] and [[LibreOffice]] computer software [[application suite]]s. It is interface-based and designed to offer interoperability between different [[programming language]]s, object models and machine architectures, on a single machine, within a LAN or over the Internet.
Users can implement or access UNO components from any programming language for which a [[language binding]] exists. Complete UNO language bindings exist for [[C++]] (compiler-dependent), [[Java (programming language)|Java]], [[Object REXX]], [[Python (programming language)|Python]], and [[Tcl (programming language)|Tcl]]. Bindings allowing access, but not writing, to components exist for [[StarOffice Basic]], [[
Universal Network Objects operate within the UNO Runtime Environment (URE).<ref>{{ cite web | url = http://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/l10n/archive/Universal_i18n_framework.pdf | title = Universal I18n Framework for Office Applications: Technical Overview | first = Dieter | last = Loeschky
The [[Apache OpenOffice]] version of UNO is released under the terms [[Apache License]] (Version 2) as [[free and open source software]].
Line 10 ⟶ 12:
Examples: an external program can export an [[OpenDocument|ODT]] file as a [[PDF]] file, or import and convert a [[Office Open XML|DOCX]], calling LibreOffice by the UNO interface. Another external program can access a cell and formulas from LibreOffice Calc file.
Application examples: ''Docvert'',<ref>{{cite web|url=http://holloway.co.nz/docvert/|title=Docvert
== UNO for Add-Ons ==
Programmers can write and integrate their own UNO components to OpenOffice/LibreOffice. Those components can be added to the LibreOffice menus and toolbars;
The Add-Ons can extend the functionality of LibreOffice.
Line 22 ⟶ 24:
#Change the user interface (menus or toolbars). This can be done almost automatically by writing an XML text file that describes the changes.
Application example: ''jOpenDocument''.<ref>{{cite web|url=http://www.jopendocument.org/|title=jOpenDocument Homepage. Open Document library|
== References ==
Line 32 ⟶ 34:
;Apache OpenOffice
* [http://udk.openoffice.org/ UNO Development Kit project page]
* [http://www.openoffice.org/udk/common/man/uno.html Overview and
* [http://www.openoffice.org/api/docs/java/ref/overview-summary.html
* [http://api.openoffice.org/SDK/index.html OpenOffice.org Software Development Kit]
* [https://web.archive.org/web/20080501062521/http://odftoolkit.openoffice.org/transition.html ODF Toolkit: Transition Steps]
Line 40 ⟶ 42:
;LibreOffice
* [http://api.libreoffice.org/docs/tools.html see unoexe and unopkg]
* [https://chris-sherlock.gitbook.io/inside-libreoffice/universal-network-objects Inside LibreOffice: Universal Network Objects]
;Language bridges (native for Java and Python)
* [
* [http://www.wstech2.net/index.php?do=0a,01,05 UNO for PHP (written in C++)] {{Webarchive|url=https://web.archive.org/web/20160304003131/http://www.wstech2.net/index.php?do=0a,01,05 |date=4 March 2016 }}
* [https://sourceforge.net/projects/uno-pas-bridge/ UNO for FreePascal/Delphi] maybe orphaned
{{OpenOffice}}
|