https://wiki.openoffice.org/w/api.php?action=feedcontributions&feedformat=atom&user=MauricioApache OpenOffice Wiki - User contributions [en]2026-05-25T14:36:49ZUser contributionsMediaWiki 1.35.14https://wiki.openoffice.org/w/index.php?title=File:Pyuno007.png&diff=161523File:Pyuno007.png2010-03-29T20:39:46Z<p>Mauricio: Cuadro de mensaje de pregunta</p>
<hr />
<div>Cuadro de mensaje de pregunta</div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=File:Pyuno006.png&diff=161521File:Pyuno006.png2010-03-29T19:52:07Z<p>Mauricio: Mensaje informativo</p>
<hr />
<div>Mensaje informativo</div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=OOoES/Desarrollo/PyUNO_ES_bak&diff=157035OOoES/Desarrollo/PyUNO ES bak2010-02-11T05:54:15Z<p>Mauricio: </p>
<hr />
<div>== El conector de Python-Uno ==<br />
Traducido por: Alexandro Colorado<br />
<br />
=== Introducción ===<br />
El conector de python-Uno o PyUno te permite usar el API estandard de OpenOffice.org desde el tan bien conocido lenguaje llamado python. Tambié te permite desarrollar componentes en python, aunque los componentes de PyUno pueden ser corridos durante el proceso dentro de la suite, este tambien puede ser conjugado desde Java, C++ o ser construido desde el lenguaje StarBasic.<br />
<br />
<br />
La versión original de este documento lo puedes encontrar en http://udk.openoffice.org/python/python-bridge.html<br />
<br />
=== Descargas ===<br />
<br />
Puedes descargar esta documentaci&oacuten incluyendo sus ejemplos y archivos de apoyo para este nuevo modo de trabajo basado en scripting para trabajos no en linea.<br />
<br />
<br />
Descarga pyuno-docs.zip<br />
<br />
<br />
<br />
=== Estado ===<br />
El conector de PyUno esta completado, pero no ha sido empleado por suficiente gente, así que puede contener algunos errores. Ahora esta integrado a la fuente de OpenOffice.org 1.1. Aunque no corre con el la fuente de las versiones 1.0 para atras.<br />
<br />
Actualmente la documentación esta enfocada a desarrolladores, que cuentan con la suficiente experiencia en el API nativo de OpenOffice.org y que lo han usado bajo otro lenguaje(Java/C++/StarBasic). Si eres un novato y sientes que alguna información es requerida, te sugerimos buscarla en la "La Guía del Desarrollador".<br />
<br />
<br />
<br />
=== El Tutorial PyUno para OpenOffice.org ===<br />
En este tutorial, mostramos como se puede usar el conector PyUNO para automatizar tareas dentro de OpenOffice.org. Este documento no es un tutorial de OpenOffice.org existen ya muchos documentos enfocados a esta actividad. A continuación mostraremos los pasos a seguir dentro de PyUNO<br />
<br />
<br />
==== Instalación de PyUNO ====<br />
Desde la versión OpenOffice.org 1.1 RC4 para arriba, PyUNO es incluido en la instalación por default. Si tienes una versió anterior a esta puedes saltar el proximo parrafo.<br />
<br />
<br />
Al Usar OpenOffice.org 1.1RC3 o antes, el conector de PyUNO debe ser seleccionado manualmente para su instalación. Escoga entonces la instalación personalizada.<br />
<br />
<br />
y activa el conector de Python-Uno en los componentes opcionales<br />
<br />
<br />
Tambien puedes instalar PyUNO despues de la instalación inicial, corriendo la instalación de OpenOffice.org sombre si misa y seleccionando Modificar en el siguiente dialogo.<br />
<br />
<br />
Nota: Cuando inicias el script de comienzo (eg. install --prefix=/usr/local) para instalación, solo puedes comenzar python despues de la instalación, solo puedes instalar pyuno despues de haber ejecutado el script setup /net y escogido Modify. Nota, que OOo Rc2 el cual no instala dos archivos ini como deviera.<br />
<br />
<br />
<br />
==== Modo del conector PyUNO ====<br />
<br />
<br />
PyUNO puede usar dos metodologías diferentes:<br />
Dentro del ejecutable de Python(y fuera del proceso de OpenOffice.org).<br />
<br />
<br />
Usa esta metodología cuando: <br />
Comienzes a usar python (tiene un enfoque mas intuitivo.<br />
quieres apuntar a ejecuciones del script comenzando procesos separados (ie. cgi-script dentro de un http-server.<br />
Quieres un retorno rapido de codigo-ejecución codigo-ejecución.<br />
<br />
Hola Mundo<br />
<br />
Asegurate, de que OOo no este corriendo(cierra el QuickStarter tambien). Activa una terminal ya sea cmd en WinNT+, command en Win9x o bash en *nix. Ve al directorio donde reside el programa de OpenOffice.org y activa OOo con los siguientes parametros.<br />
:\Program Files\OpenOffice1.1\program> soffice "-accept=socket,host=localhost,port=2002;urp;" <br />
<br />
Ahora comienza el archivo hello_world.py con tu editor de texto favorito e incluye el siguiente codigo.<br />
<code>[python] import uno<br />
<br />
# get the uno component context from the PyUNO runtime<br />
localContext = uno.getComponentContext()<br />
<br />
# create the UnoUrlResolver <br />
resolver = localContext.ServiceManager.createInstanceWithContext(<br />
"com.sun.star.bridge.UnoUrlResolver", localContext )<br />
<br />
# connect to the running office <br />
ctx = resolver.resolve( "uno:socket,host=localhost,port=2002;urp;StarOffice.ComponentContext" )<br />
smgr = ctx.ServiceManager<br />
<br />
# get the central desktop object<br />
desktop = smgr.createInstanceWithContext( "com.sun.star.frame.Desktop",ctx)<br />
<br />
# access the current writer document<br />
model = desktop.getCurrentComponent()<br />
<br />
# access the document's text property<br />
text = model.Text<br />
<br />
# create a cursor<br />
cursor = text.createTextCursor()<br />
<br />
# insert the text into the document<br />
text.insertString( cursor, "Hello World", 0 )<br />
<br />
# Do a nasty thing before exiting the python process. In case the<br />
# last call is a oneway call (e.g. see idl-spec of insertString),<br />
# it must be forced out of the remote-bridge caches before python<br />
# exits the process. Otherwise, the oneway call may or may not reach<br />
# the target object.<br />
# I do this here by calling a cheap synchronous call (getPropertyValue).<br />
ctx.ServiceManager</code><br />
<br />
Ejecuta el script pasado con el siguiente comando<br />
c:\Program Files\OpenOffice1.1\program> .\python hello_world.py <br />
<br />
Este script escribe la cadena Hello World dentro del documento OpenWriter<br />
<br />
==== Dentro del proceso de OpenOffice.org ====<br />
<br />
Usa este modo cuando:<br />
* Quieras facilmente ejecutar tu codigo en multiples maquinas<br />
* Tu codigo sea necesitado por llamadas de otros programas<br />
* Tienes mas experiencia con el funcionamiento de PyUNO.<br />
* Quieres que tu codigo corra con el mejor desempeño<br />
Hola Mundo<br />
<br />
El ejemplo siguiente esta guardado como un componente de UNO, esto significa, que el codigo que ejecuta la insersion necesita ser embedido en una class de python. Aparte, el codigo-de-conexion a la suite necesita ser remplazado por un punto clave, el cual usa el cargador de python para iniciar una clase de python.<br />
hello_world.py<br />
<code>[python]import uno<br />
import unohelper<br />
<br />
from com.sun.star.task import XJobExecutor<br />
<br />
# implement a UNO component by deriving from the standard unohelper.Base class<br />
# and from the interface(s) you want to implement.<br />
class HelloWorldJob( unohelper.Base, XJobExecutor ):<br />
def __init__( self, ctx ):<br />
# store the component context for later use<br />
self.ctx = ctx<br />
<br />
def trigger( self, args ):<br />
# note: args[0] == "HelloWorld", see below config settings<br />
<br />
# retrieve the desktop object<br />
desktop = self.ctx.ServiceManager.createInstanceWithContext(<br />
"com.sun.star.frame.Desktop", self.ctx )<br />
<br />
# get current document model<br />
model = desktop.getCurrentComponent()<br />
<br />
# access the document's text property<br />
text = model.Text<br />
<br />
# create a cursor<br />
cursor = text.createTextCursor()<br />
<br />
# insert the text into the document<br />
text.insertString( cursor, "Hello World", 0 )<br />
<br />
# pythonloader looks for a static g_ImplementationHelper variable<br />
g_ImplementationHelper = unohelper.ImplementationHelper()<br />
<br />
# <br />
g_ImplementationHelper.addImplementation( \<br />
HelloWorldJob, # UNO object class<br />
"org.openoffice.comp.pyuno.demo.HelloWorld", # implemenation name<br />
# Change this name for your own<br />
# script <br />
("com.sun.star.task.Job",),) # list of implemented services<br />
# (the only service)</code><br />
<br />
El codigo necesita ser enlazado a un evento. Esto puede hacerce configurando estas opciones.<br />
Addons.xcu: <br />
<br />
<br />
Both files must be packaged up into a single zip file by using your favourite zip utility, e.g. infozip<br />
<code>[bash]zip hello_world.zip Addons.xcu hello_world_comp.py<br />
adding: Addons.xcu (deflated 55%)<br />
adding: hello_world_comp.py (deflated 55%)</code><br />
<br />
Estos paquetes pueden ser implementados dentro de una instalación de OpenOffice.org usando la herramienta <br />
pkgchk<br />
, el cual esta ubicada en el directorio de program dentro de OOo. Se advierte que OOo debe de estar completamente cerrado. <br />
c:\Program Files\OpenOffice.org1.1\program> pkgchk hello_world.zip<br />
c:\Program Files\OpenOffice.org1.1\program><br />
<br />
Si el proceso se realiza con exito, no tendras ningun reotorno de la herramienta. Y cuando comienzes de nuevo OOo, encontraras una nueva entrada del menu (ver Tools / Aditional Components / Insert Hello World).<br />
<br />
Como puedes ver las lineas de los scripts bases son identicas, pero la forma para extraer los componentes de office difieren.<br />
Ejemplos<br />
* ooextract.py- Una herramienta de linea de comando la cual extrae el contenido de un archivo creado con OpenOffice.org en un modo stout.<br />
* swriter.py- Herramienta de linea de comando la cual crea y llena un documento de Writer con cierto texto y tablas con formato.<br />
* swritercomp.py y swritercompclient.pyIgual que la anterior pero esta esta en modo componente UNO, asi que corre dentro de OpenOffice.org. Uno puede ver la mejora en el desempeño corriendo el componente como un proceso.<br />
biblioaccess.py- Herramienta de linea de comando, que presenta el contenido del la base de datos, biblio, que incluye OpenOffice.org<br />
<br />
=== Conexión al lenguaje UNO ===<br />
<br />
A continuación encontrarás la completa descripción de las herramientas UNO se conectan con el lenguaje de Python.<br />
El typo de mapeo UNOEl tipo de dato IDL<br />
<br />
<br />
tipos de enteros (byte, short, unsigned long, hyper, unsigned hyper Representación en Python<br />
<br />
<br />
Python solo conoce los datatypes encontrados en C long y long long como tipos de enteros. En la mayor parte de las maquinas, un long es un valor de 32 bit mientras long long es de 64 bits.<br />
* Valores de UNO (por ejemplo, retorno del valor de un metodo UNO)<br />
* Valores que tiene los tipos byte, short, unsigned short, long o unsigned, long son convertidos a un valor python long. <br />
* Valores que tienen un tipo de hyper u unsigned hyper son convertidos a python como long long.<br />
* Valores enviados a UNO (por ejemplo, el argumento de un metodo UNO)<br />
<br />
<br />
Si hay un tipo concreto en el metodo IDL, el valor es convertido a un tipo concreto (de hecho el servicio de invoación hace este trabajo). Si el metodo solo contiene un any, cada valor del entero será convertido al typo de dato mas pequeño, donde el valor se ajusta y lo manda al objeto UNO (así que 5 se convierte en un byte, 150 se vuelve short, 0x1f023 un long y los valores mayores a 0xffffffff se convierten en un hyper.<br />
boolean <br />
<br />
<br />
Python tiene, internamente un datatype buleano, el cual es derivado del tipo de entero (ver http://python.org/peps/pep-0285.html ). Ahí existe el True y False, el cual PyUNO usa para distinguir entre valores integrales o buleanos.<br />
<br />
<br />
Mientras el buleano sea especificado en el metodo de interfaz, podrás seguir usando numeros. En los ejemplos siguientes, todas las llamadas son validas:<br />
<code>[python]#idl signature void takeBool( [in] boolean bool )<br />
unoObject.takeBool( 1 ) # valid, passing true (PyUNO runtime<br />
# does the conversion<br />
unoObject.takeBool( True) ) # valid, passing true<br />
unoObject.takeBool( False ) # valid, passing false</code><br />
<br />
Si embargo, cuando quieres especificamente pasar un buleano, cuando solo any es especificado, tu debes usar True y False.<br />
idl signature void foo( [in] any value )<br />
<br />
<code>[python]# implementation expects a boolean (which is separately documented<br />
# e.g. in the service specification.<br />
unoObject.foo( True ) # valid, pass a true<br />
unoObject.foo( 1 ) # bad, just passing a 1, implementation will<br />
# probably not be able to deal with it correctly.</code><br />
<br />
Nota: Tambien existe el uso de la clase uno.Bool, el cual es no es usado desde pyuno 0.9.2 aunque se sigue soportando. Ya no lo usen.<br />
string En general, la cadena esta mapeada dentro de la cadena-unicodigo de python. Sin embargo, quizas pases una cadena de 8-bits cuando se espere una cade de UNO, el conector convierte los 8-bits a una cadena-unicodigo usando el locale del sistema. <br />
<code>[python]# idl signatore foo( [in] string value )<br />
# both lines are valid<br />
unoObject.foo( u'my foo string' )<br />
unoObject.foo( 'my foo string' )<br />
char Un char es mapeado a un uno.Char. Tiene el miembro de una cadena-unicodigo publico con lenght 1 como contenedor del char unicodigo. <br />
# idl signature foo( [in] char c)<br />
unoObject.foo( uno.Char( u'h' ) ) #valid<br />
unoObject.foo( 'h' ) #wrong<br />
<br />
enum </code><br />
<br />
<br />
Un valor enum es representado concretamente por una instancia de la clase uno.Enum. Tiene dos miembros, typeName es una string conteniendo el nombre del tipo enum y value contiene el valor de enum.<br />
<br />
Puedes concretar los valores de enum de dos formas:<br />
<br />
<br />
1.(suggested) by importing<br />
from enumname import enumvalue. <br />
<br />
E.g. <br />
[code]from com.sun.star.uno.TypeClass import UNSIGNED_LONG<br />
.<br />
.<br />
.<br />
unoObject.setValue( UNSIGNED_LONG )<br />
if unoObject.getValue() == UNSIGNED_LONG:[/code]<br />
<br />
<br />
2.(in rare situations)<br />
<br />
<br />
<code>[python]import uno<br />
<br />
unoObject.setValue( uno.Enum( "com.sun.star.uno.TypeClass", "UNSIGNED_LONG") )<br />
if unoObject.getValue() == uno.Enum( "com.sun.star.uno.TypeClass", "UNSIGNED_LONG"):</code><br />
<br />
La primera soluci&ooacute;n tiene la ventaja de que en caso de el fallo en enum manda una RunTimeException o excepción del tiempo de proceso al momento que la fuente de python es importada.<br />
<br />
<br />
''type ''<br />
Un tipo se mapea a uno.type . Tiene miembros publicos llamados typeName (cadenas) y typeClass (el valor enum de com.sun.star.uno.TypeClass). Ahi existe una función uno.getTypeByName() para facilmente crear una instancia de type, las funciones crean un RunTimeException en caso que el type no se conosca.<br />
<br />
Puedes crear valores concretos de dos formas:<br />
1. from module-where-type-lives-in import typeOfTypeName. <br />
<br />
E.g. to create XComponent's type, use <br />
<br />
<br />
from com.sun.star.lang import typeOfXComponent<br />
.<br />
.<br />
.<br />
unoObject.setType( typeOfXComponent )<br />
if unoObject.getType() == typeOfXComponent: <br />
<br />
2.(in rare situations, e.g. for types of simple values)<br />
<br />
<code>[python]<br />
import uno<br />
<br />
unoObject.setType( uno.getTypeByName( "com.sun.star.uno.XComponent" ) )<br />
if unoObject.getType() == uno.getTypeByName( "com.sun.star.uno.XComponent"):<br />
struct (and exception) </code><br />
Para cada uno struct (o excepción), una nueva clase de python es generada al vuelo. La clase generada refleja la jerarquia heredada del tipo UNO (es importante para el administrador de excepciones, ver abajo).<br />
<br />
Uno puede generar una clase struct usando el mecanismo de importación. Una instanacia del struct puede entonces ser instanciada usando el constructor de python. El constructor soporta el argumento cero (miembros obtienen el constructor default), 1 argumento con el mismo tipo (copia el constructor), y n argumentos, donde n es el nombre de elementos que contiene el struct. El struct soporta el operador de equality, dos struct son iguales, si son del mismo type y cada miembro es igual.<br />
<br />
Ejemplo.<br />
<code>[python]<br />
from com.sun.star.beans import PropertyValue<br />
from com.sun.star.uno import Exception,RuntimeException<br />
<br />
propVal = PropertyValue() # Default constructor<br />
propVal.Name = "foo"<br />
propVal.Value = 2<br />
<br />
if propVal == PropertyValue( "foo", 2 ): # Memberwise constructor<br />
# true !<br />
pass<br />
<br />
if propVal == PropertyValue( propVal ): # Copy Constructor<br />
# true </code><br />
<br />
Una instancia del struct UNO puede ser inicialmente construida de la función uno.createUnoStruct() y pasando el nombre de la struct como el primer parametro y el argumento opcional del constructor (ver arriba para un ejemplo de un posible ctors).<br />
<br />
ATENCION: En UNO, struct tiene el valor semantico, sin embargo, la manera como se maneja en python no refleja esto. Cuando el struct es pasado de un parametro a una funcion, el valor es pasado la funcion llamada. Las siguientes modificaciones a la instancia de la struct no afectaran a la funcion llamada. Sin embargo, la simple asignaci&oactue;n de una struct a otra variable local no crea una copia, simplemente crea un alias de la instancia original.<br />
<code>[python]<br />
struct = uno.createUnoStruct( "com.sun.star.beans.PropertyValue" )<br />
<br />
struct.Name = "foo"<br />
struct2 = struct<br />
struct2.Name = "python" # modifies also struct, probably not desired !<br />
unoObject.call( struct, struct2 ) # passes the same struct 2 times !<br />
<br />
struct.Name = "doobidooo" # even worse style. If the UNO object is implemented<br />
# in python, you possibly modify the callee's value.<br />
# Don't do this !<br />
sequence </code><br />
Una secuencia generalmente esta trazada a una tupla de python. Una lista de de python (!) no es aceptada.<br />
<code>[python]# idl signature XInterface createInstanceWithArguments(<br />
# [in] string servicename, [in] sequence )<br />
doc = smgr.createInstanceWithArguments( "foo.service", ("arg1",2))</code><br />
<br />
Atención desde la version 0.9.2 El idl sequence<byte> es trazado a la clase uno.ByteSquence. Tiene un miembro cadena llamado value, el cual contiene los datos de la secuencia de byte. Tal como la bytesequence es generalmente un contenedor para datos binarios, esta clase permite manejar binarios eficientemente. Esto tambien embede pyuno a python, ya que python mantiene datos binarios en cadenas.<br />
<code>[python]# idl signature writeBytes( [in] sequence%lt; byte > data )<br />
#<br />
out.writeBytes( uno.ByteSequence( "abc" ) )<br />
<br />
# you could also write the following<br />
begin = uno.ByteSequence( "ab" )<br />
out.writeBytes( begin + "c" )<br />
<br />
# but this does not work !<br />
out.writeBytes( "abc" ) # ERROR, no implict conversion supported by the runtime !<br />
<br />
<br />
# idl signature long readBytes( [out] sequence , [in] length )<br />
len,seq = in.readBytes( dummy, 3 )<br />
<br />
# the statements do the same thing <br />
print seq == "abc":<br />
print seq == uno.ByteSequence( "abc" )<br />
constants </code><br />
Una constante UNO idl puede ser dada por diferentes maneras:<br />
Usa el valor concreto especificado en el archivo idl<br />
Una constante es su valor y solo su valor. Ya que las modificaciones de los valores de la contacia es incompatible.<br />
Usa el mecanismo de importación para crear variables con un nombre constante<br />
La solución es la mas leida.<br />
Usauno.getConstatByName()<br />
puede ser util de vez en cuando. Las funciones RunTimeException se ejecutan en caso que la constante sea desconocida. <br />
<code>[python]from com.sun.star.beans.PropertyConcept import ATTRIBUTES<br />
.<br />
.<br />
.<br />
# the following 3 lines are equivalent<br />
unoObject.setConcept( ATTRIBUTES )<br />
unoObject.setConcept( 4 )<br />
unoObject.setConcept( uno.getConstantByName( "com.sun.star.beans.PropertyConcept.ATTRIBUTES" ) )<br />
any </code><br />
En general el programador en python nunca llega a tener contacto con anys. Si alguna vez saliera any en un metodo, el programador puede tan solo pasar un valor concreto. Consecuentemente, los retornos de valores o parametros tambien nunca contiene un any concreto.<br />
<br />
Sin embargo, hay ciertas circumstancias, donde el programdor de python quiera pasar un valor type concreto a una funcion que llame (nota, esto es solo posible para llamadas del 'conector', no puedes pasar un valor de type a ningun otro objeto python-uno).<br />
<br />
Puedes crear un uno.Any( ), pasando el type ( como typename o como uno.Type) y su valor.<br />
<code>[python]# constructs a uno.Any, that contains a byte<br />
byteAny = uno.Any( "byte" , 5 )<br />
<br />
# constructs a sequences of shorts<br />
byteAny = uno.Any( "[]short", (4,5))</code><br />
<br />
<br />
Estas anys solo pueden ser usadas junto con el uno.invoke, el cual permite invocar un metodo dentro de un objeto arbitrario con un type any.<br />
<code>[python]# the normal call<br />
uno.setPropertyValue( "foo", (4,5))<br />
<br />
# the uno.invoke call<br />
uno.invoke( obj, "setPropertyValue" , ("foo",uno.Any( "[]short", (4,5))) )</code><br />
<br />
Cuando obj es un objeto conectado, la funcion que se llama obtiene la secuencia como una sequence(short). Cuando obj es un objeto local de python, solo obtiene el (4,5) como si lo hubiera obtenido con la llamada normal.<br />
<br />
=== Implementando los objetos UNO ===<br />
Podras usar clases de python para implementar los objetos UNO. Instancias de python pueden ser pasadas como argumentos a llamados de UNO donde los anys o interfaces concretas hayan sido especificadas.<br />
<br />
Para ser un objeto UNO, una clase de python DEBE implementar la interface com.sun.star.lang.XTypeProvider implementando los metodos getTypes() y getImplementationID(), el cual informa el bridge de python, sobre cual UNO concreta la interfaz con la clase que implementa python. La funci&ooacute;n de getTypes() define que interfaz son definidas por las clases.<br />
<br />
Para hacer esto mas fácil, existe una clase unohelper.Base, donde uno objeto UNO de python se originara de el. Tu puedes entonces implementar una interfaz UNO simpmente originandolo de la interfaz preferida. El siguiente ejemplo implementa la interfaz com.sun.star.lang.XTypeProvider, el cual almacena toda la información escrita en el espacion de una ByteSequence(). (Nota: esta implementació es bastante pobre y es solo con propositos de demostración.<br />
<code>[python]import unohelper<br />
from com.sun.star.io import XOutputStream<br />
class SequenceOutputStream( unohelper.Base, XOutputStream ):<br />
def __init__( self ):<br />
self.s = uno.ByteSequence("")<br />
self.closed = 0<br />
<br />
def closeOutput(self):<br />
self.closed = 1<br />
<br />
def writeBytes( self, seq ):<br />
self.s = self.s + seq<br />
<br />
def flush( self ):<br />
pass<br />
<br />
def getSequence( self ):<br />
return self.s</code><br />
<br />
Desde la lista de clases bases, la implementación unohelper.Base implementa correctamente la interfaz XTypeProvider.<br />
Implementando componentes de Python UNO.<br />
<br />
Existe un cargador de componentes a python. Esto permite crear instancias de clases de python no solo en el proceso de python pero en cual quialquier proceso arbitrario de UNO incluyendo OpenOffice.org. El cargador de python, carga el runtime de python bajo demanda en caso de no estar cargado y ejecutando codigo de python desde el interprete root de python.<br />
<br />
Si el lector no esta familiarizado con el proceso de registro de componentes, entonces se sugiere que vaya el maual de desarrollo de OpenOffice.org para una amplia explicación.<br />
<br />
El cargador de Python actualmente soporta los siguientes protocolos para urls recibidas:Nombre del Protocolo Descripción<br />
vnd.openoffice.pymodule <br />
El protocolo depende en parte interpretado por el nombre del modulo de python, el cual es importado usando el componente de importación comun en python (el cual usa la variable de ambiente de PYTHONPATH).<br />
<br />
Ejemplo. vnd.openoffice.pymodule:MyPythonComponent<br />
<br />
Usando esta url ej. en XLoader.activate() intentara correr al archivo MyPythonComponent.py desde los directorios, los cuales son listados dentro de la variable de ambiente PYTHONPATH. Toma nota que no debes usar el prefijo *.py en este caso.<br />
<br />
El modulo mostrado es agregado al mapeo de sys.modules.<br />
file <br />
Obligatoriamente el url debe ser absoluto al archivo componente de python. El archivo mismo no necesita ser contenido en el PYTHONPATH, simplemente importar los archivos que estan contenidos en el PYTHONPATH. El modulo no es adherido al sys.modules.<br />
<br />
Ejemplo: file:///path/to/MyPythonComponent.py<br />
vnd.sun.star.expand <br />
El cargador de python soporta el mecanismo de expansion de macros tal como los cargadores de Java y C++.<br />
<br />
Ejemplo: vnd.sun.star.expand:$UNO_USER_PACKAGES_CACHE/MyPythonComponent.py<br />
<br />
<br />
Despues de que el modulo esta importado, el cargador de python busca una variable del modulo-global con el nombre g_ImplementationHelper el cual es esperado ser una intancia del unohelper.ImplementationHelper. El siguiente ejemplo hace que un componente de uno fuera de los objetsos UNO ( no es que el componente sea tan útil, por que en esta ocasion no existe un metodo UNO que reciba una tupla tampoco existe especificaci&ooacute;n de servicio com.sun.star.io.OutputStream, solo estan aquí como ejemplo. )<br />
<code>[python]import unohelper<br />
from com.sun.star.io import XOutputStream<br />
<br />
g_ImplementationHelper = unohelper.ImplementationHelper()<br />
<br />
class TupleOutputStream( unohelper.Base, XOutputStream ):<br />
# The component must have a ctor with the component context as argument.<br />
def __init__( self, ctx ):<br />
self.t = ()<br />
self.closed = 0<br />
<br />
# idl void closeOutput();<br />
def closeOutput(self):<br />
self.closed = 1<br />
<br />
# idl void writeBytes( [in] sequence seq );<br />
def writeBytes( self, seq ):<br />
self.t = self.t + seq # simply add the incoming tuple to the member<br />
<br />
# idl void flush();<br />
def flush( self ):<br />
pass<br />
<br />
# convenience function to retrieve the tuple later (no UNO function, may<br />
# only be called from python )<br />
def getTuple( self ):<br />
return self.t<br />
<br />
# add the TupleOutputStream class to the implementation container,<br />
# which the loader uses to register/instantiate the component.<br />
g_ImplementationHelper.addImplementation( \<br />
TupleOutputStream,"org.openoffice.pyuno.PythonOutputStream",<br />
("com.sun.star.io.OutputStream",),)</code><br />
<br />
Asumamos, que este codigo es guardado en un archivo llamado tuplestrm.py y el archivo existe en algun lugar dentro de la variable PYTHONPATH, puede ser registrado al OO1beta construido del siguiente formato:<br />
regcomp -register -br types.rdb -br services.rdb -r services.rdb -c vnd.openoffice.pymodule:tuplestrm <br />
<br />
Claro que tambien puedes usar el pkgchk del tutorial en el capitulo<br />
pkgchk tuplestrm.py <br />
<br />
aunque este comando crea una copia del archivo (cuando el script cambia, debe ser reimplementado usando el comando que sigue. )<br />
<br />
Este componente puede ser llamado desde OpenOffice.org Basic con:<br />
<code>[python]tupleStrm = createUnoService( "com.sun.star.io.OutputStream" )<br />
tupleStrm.flush()</code></div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=File:Pyuno005.png&diff=156852File:Pyuno005.png2010-02-10T06:58:38Z<p>Mauricio: </p>
<hr />
<div></div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=File:Pyuno004.png&diff=156851File:Pyuno004.png2010-02-10T06:56:18Z<p>Mauricio: </p>
<hr />
<div></div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=File:Pyuno002.png&diff=156440File:Pyuno002.png2010-02-06T06:51:53Z<p>Mauricio: uploaded a new version of "File:Pyuno002.png"</p>
<hr />
<div></div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=File:Pyuno003.png&diff=156431File:Pyuno003.png2010-02-06T05:46:05Z<p>Mauricio: </p>
<hr />
<div></div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=File:Pyuno002.png&diff=156430File:Pyuno002.png2010-02-06T05:45:44Z<p>Mauricio: </p>
<hr />
<div></div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=File:Pyuno001.png&diff=156428File:Pyuno001.png2010-02-06T05:35:48Z<p>Mauricio: </p>
<hr />
<div></div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=ES&diff=156423ES2010-02-06T05:13:50Z<p>Mauricio: /* OpenOffice.org Espa&ntilde;ol */</p>
<hr />
<div>{{DISPLAYTITLE: Wiki de OpenOffice.org Español}}<br />
<br />
[[image:Oooespanol.png]]<br />
=== [[OpenOffice.org|OpenOffice.org]] Espa&ntilde;ol===<br />
<br />
<br />
Pagina de la comunidad en Espa&ntilde;ol<br />
<br />
<div style="background-color: #eff3ff;"><br />
Aprende como '''[[OOoES/AyudaWiki |contribuir con el wiki]]'''.<br />
</div><br />
<br />
== Bienvenido al wiki de OpenOffice.org==<br />
Este wiki es para todos los proyectos asociados con OpenOffice.org (OOo). Es nuevo, por lo que esta enfocado principalmente a recursos para desarrolladores. Cuando se añadan otros proyectos, se listarán aquí. Haz clic sobre un enlace para ir a la página que quieras. <br />
* [[OOoES/Desarrollo/Inicio|Desarrollo]] <br />
* [[Marketing|Mercadeo (internacional)]]<br />
* [[ES/Marketing|Mercadeo (en español)]]<br />
* [[NLC|Confederación idioma nativo]]<br />
* [[#Finding general OpenOffice.org user help|Recursos de usuario]]<br />
* [[OOoES/Desarrollo/Aseguramiento de la calidad|Aseguramiento de la calidad]]<br />
<br />
Contribuye con el Wiki de OpenOffice.org. Por favor, usa tu login de OOo para la cuenta del wiki. Para evitar el spam, algunas funciones están disponibles solamente si estás registrado. Posiblemente más adelante seamos capaces de evitar la administración separada de usuarios y autenticarte con las credenciales del sitio de OpenOffice.org.<br />
<br />
Para iniciar la edición del wiki ve [[Help:Editing]].<br />
<br />
----<br />
<br />
<div style="width:45%; float:right;"><br />
=== Traducciones ===<br />
Traducciones de otras p&aacute;gina de proyectos dentro de OpenOffice.org donde la comunidad tiene participaci&oacute;n.<br />
* [[OOoES/Traduccion/Localizacion_ES_30|Localizacion_ES]] Localización de OOo tanto el UI como la ayuda.<br />
* Traducción de herramientas de localización:<br />
** [[Traduccion_QA1]]<br />
** [[Traduccion_TCM]]<br />
** [[QATrack_ES]]<br />
* [http://www.slideshare.net/jza/issue-tracker/|Issue Tracker] - presentaci&oacute;n de issue tracker.<br />
</div><br />
<div style="width:45%"><br />
<br />
=== Proyectos ===<br />
Iniciativas o proyectos dentro de la comunidad.<br />
* Lista de tareas en las que pueden contribuir [[contribuciones_OOoES]].<br />
* [[Comparativa_MSvsOOo| Comparativa de funcionalidad entre Microsoft Office y OpenOffice.org]] '''Nuevo'''<br />
* [[Propuesta_estandarizacion | Plantilla de Propuesta de migraci&oacute;n hacia OpenDocument y OpenOffice.org]] '''Nuevo'''<br />
* [[TemarioCertificacionOOo | Temario de Certifcación de OpenOffice.org]]<br />
* [[Desarrollo/Diccionarios | Diccionarios]]<br />
</div><br />
<br />
===Varios===<br />
* [[OOoES/Desarrollo/CSS |OOoES Styles]] of the [[OOoES]], CSS practices.<br />
* [[API@OOo_ES]] Traduccion del volante de noticias del proyecto API<br />
* [[Referencia Modulos]] Referencia a modulos de OpenOffice.org<br />
* [[Tips OOo]] Aqui podras encontrar tips y recursos de como mejorar tu experiencia con OpenOffice.org<br />
* [[ES_Documentacion | Documentaci&oacute;n]] Guia sobre como esta organizada la documentacion.<br />
* [[OOo y Distros Linux]] Nexo entre OpenOffice.org y las principales distribuciones de Linux<br />
<br />
<br />
[[Category:NLC]] [[Category:OOoES]]</div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=ES&diff=156422ES2010-02-06T05:13:18Z<p>Mauricio: /* OpenOffice.org Espa&ntilde;ol */</p>
<hr />
<div>{{DISPLAYTITLE: Wiki de OpenOffice.org Español}}<br />
<br />
[[image:Oooespanol.png]]<br />
=== [[OpenOffice|OpenOffice.org]] Espa&ntilde;ol===<br />
<br />
<br />
Pagina de la comunidad en Espa&ntilde;ol<br />
<br />
<div style="background-color: #eff3ff;"><br />
Aprende como '''[[OOoES/AyudaWiki |contribuir con el wiki]]'''.<br />
</div><br />
<br />
== Bienvenido al wiki de OpenOffice.org==<br />
Este wiki es para todos los proyectos asociados con OpenOffice.org (OOo). Es nuevo, por lo que esta enfocado principalmente a recursos para desarrolladores. Cuando se añadan otros proyectos, se listarán aquí. Haz clic sobre un enlace para ir a la página que quieras. <br />
* [[OOoES/Desarrollo/Inicio|Desarrollo]] <br />
* [[Marketing|Mercadeo (internacional)]]<br />
* [[ES/Marketing|Mercadeo (en español)]]<br />
* [[NLC|Confederación idioma nativo]]<br />
* [[#Finding general OpenOffice.org user help|Recursos de usuario]]<br />
* [[OOoES/Desarrollo/Aseguramiento de la calidad|Aseguramiento de la calidad]]<br />
<br />
Contribuye con el Wiki de OpenOffice.org. Por favor, usa tu login de OOo para la cuenta del wiki. Para evitar el spam, algunas funciones están disponibles solamente si estás registrado. Posiblemente más adelante seamos capaces de evitar la administración separada de usuarios y autenticarte con las credenciales del sitio de OpenOffice.org.<br />
<br />
Para iniciar la edición del wiki ve [[Help:Editing]].<br />
<br />
----<br />
<br />
<div style="width:45%; float:right;"><br />
=== Traducciones ===<br />
Traducciones de otras p&aacute;gina de proyectos dentro de OpenOffice.org donde la comunidad tiene participaci&oacute;n.<br />
* [[OOoES/Traduccion/Localizacion_ES_30|Localizacion_ES]] Localización de OOo tanto el UI como la ayuda.<br />
* Traducción de herramientas de localización:<br />
** [[Traduccion_QA1]]<br />
** [[Traduccion_TCM]]<br />
** [[QATrack_ES]]<br />
* [http://www.slideshare.net/jza/issue-tracker/|Issue Tracker] - presentaci&oacute;n de issue tracker.<br />
</div><br />
<div style="width:45%"><br />
<br />
=== Proyectos ===<br />
Iniciativas o proyectos dentro de la comunidad.<br />
* Lista de tareas en las que pueden contribuir [[contribuciones_OOoES]].<br />
* [[Comparativa_MSvsOOo| Comparativa de funcionalidad entre Microsoft Office y OpenOffice.org]] '''Nuevo'''<br />
* [[Propuesta_estandarizacion | Plantilla de Propuesta de migraci&oacute;n hacia OpenDocument y OpenOffice.org]] '''Nuevo'''<br />
* [[TemarioCertificacionOOo | Temario de Certifcación de OpenOffice.org]]<br />
* [[Desarrollo/Diccionarios | Diccionarios]]<br />
</div><br />
<br />
===Varios===<br />
* [[OOoES/Desarrollo/CSS |OOoES Styles]] of the [[OOoES]], CSS practices.<br />
* [[API@OOo_ES]] Traduccion del volante de noticias del proyecto API<br />
* [[Referencia Modulos]] Referencia a modulos de OpenOffice.org<br />
* [[Tips OOo]] Aqui podras encontrar tips y recursos de como mejorar tu experiencia con OpenOffice.org<br />
* [[ES_Documentacion | Documentaci&oacute;n]] Guia sobre como esta organizada la documentacion.<br />
* [[OOo y Distros Linux]] Nexo entre OpenOffice.org y las principales distribuciones de Linux<br />
<br />
<br />
[[Category:NLC]] [[Category:OOoES]]</div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=ES&diff=156419ES2010-02-06T05:07:01Z<p>Mauricio: /* Bienvenido al wiki de OpenOffice.org */</p>
<hr />
<div>{{DISPLAYTITLE: Wiki de OpenOffice.org Español}}<br />
<br />
[[image:Oooespanol.png]]<br />
=== [[OpenOffice|OpenOffice]].org Espa&ntilde;ol===<br />
<br />
<br />
Pagina de la comunidad en Espa&ntilde;ol<br />
<br />
<div style="background-color: #eff3ff;"><br />
Aprende como '''[[OOoES/AyudaWiki |contribuir con el wiki]]'''.<br />
</div><br />
<br />
== Bienvenido al wiki de OpenOffice.org==<br />
Este wiki es para todos los proyectos asociados con OpenOffice.org (OOo). Es nuevo, por lo que esta enfocado principalmente a recursos para desarrolladores. Cuando se añadan otros proyectos, se listarán aquí. Haz clic sobre un enlace para ir a la página que quieras. <br />
* [[OOoES/Desarrollo/Inicio|Desarrollo]] <br />
* [[Marketing|Mercadeo (internacional)]]<br />
* [[ES/Marketing|Mercadeo (en español)]]<br />
* [[NLC|Confederación idioma nativo]]<br />
* [[#Finding general OpenOffice.org user help|Recursos de usuario]]<br />
* [[OOoES/Desarrollo/Aseguramiento de la calidad|Aseguramiento de la calidad]]<br />
<br />
Contribuye con el Wiki de OpenOffice.org. Por favor, usa tu login de OOo para la cuenta del wiki. Para evitar el spam, algunas funciones están disponibles solamente si estás registrado. Posiblemente más adelante seamos capaces de evitar la administración separada de usuarios y autenticarte con las credenciales del sitio de OpenOffice.org.<br />
<br />
Para iniciar la edición del wiki ve [[Help:Editing]].<br />
<br />
----<br />
<br />
<div style="width:45%; float:right;"><br />
=== Traducciones ===<br />
Traducciones de otras p&aacute;gina de proyectos dentro de OpenOffice.org donde la comunidad tiene participaci&oacute;n.<br />
* [[OOoES/Traduccion/Localizacion_ES_30|Localizacion_ES]] Localización de OOo tanto el UI como la ayuda.<br />
* Traducción de herramientas de localización:<br />
** [[Traduccion_QA1]]<br />
** [[Traduccion_TCM]]<br />
** [[QATrack_ES]]<br />
* [http://www.slideshare.net/jza/issue-tracker/|Issue Tracker] - presentaci&oacute;n de issue tracker.<br />
</div><br />
<div style="width:45%"><br />
<br />
=== Proyectos ===<br />
Iniciativas o proyectos dentro de la comunidad.<br />
* Lista de tareas en las que pueden contribuir [[contribuciones_OOoES]].<br />
* [[Comparativa_MSvsOOo| Comparativa de funcionalidad entre Microsoft Office y OpenOffice.org]] '''Nuevo'''<br />
* [[Propuesta_estandarizacion | Plantilla de Propuesta de migraci&oacute;n hacia OpenDocument y OpenOffice.org]] '''Nuevo'''<br />
* [[TemarioCertificacionOOo | Temario de Certifcación de OpenOffice.org]]<br />
* [[Desarrollo/Diccionarios | Diccionarios]]<br />
</div><br />
<br />
===Varios===<br />
* [[OOoES/Desarrollo/CSS |OOoES Styles]] of the [[OOoES]], CSS practices.<br />
* [[API@OOo_ES]] Traduccion del volante de noticias del proyecto API<br />
* [[Referencia Modulos]] Referencia a modulos de OpenOffice.org<br />
* [[Tips OOo]] Aqui podras encontrar tips y recursos de como mejorar tu experiencia con OpenOffice.org<br />
* [[ES_Documentacion | Documentaci&oacute;n]] Guia sobre como esta organizada la documentacion.<br />
* [[OOo y Distros Linux]] Nexo entre OpenOffice.org y las principales distribuciones de Linux<br />
<br />
<br />
[[Category:NLC]] [[Category:OOoES]]</div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=OOoES/Desarrollo/PyUNO_ES_bak&diff=156405OOoES/Desarrollo/PyUNO ES bak2010-02-06T02:40:26Z<p>Mauricio: Created page with '== El conector de Python-Uno == Traducido por: Alexandro Colorado === Introducción === El conector de python-Uno o PyUno te permite usar el API estandard de OpenOffice.org desd…'</p>
<hr />
<div>== El conector de Python-Uno ==<br />
Traducido por: Alexandro Colorado<br />
<br />
=== Introducción ===<br />
El conector de python-Uno o PyUno te permite usar el API estandard de OpenOffice.org desde el tan bien conocido lenguaje llamado python. Tambié te permite desarrollar componentes en python, aunque los componentes de PyUno pueden ser corridos durante el proceso dentro de la suite, este tambien puede ser conjugado desde Java, C++ o ser construido desde el lenguaje StarBasic.<br />
<br />
<br />
La versión original de este documento lo puedes encontrar en http://udk.openoffice.org/python/python-bridge.html<br />
<br />
=== Descargas ===<br />
<br />
Puedes descargar esta documentaci&oacuten incluyendo sus ejemplos y archivos de apoyo para este nuevo modo de trabajo basado en scripting para trabajos no en linea.<br />
<br />
<br />
Descarga pyuno-docs.zip<br />
<br />
<br />
<br />
=== Estado ===<br />
El conector de PyUno esta completado, pero no ha sido empleado por suficiente gente, así que puede contener algunos errores. Ahora esta integrado a la fuente de OpenOffice.org 1.1. Aunque no corre con el la fuente de las versiones 1.0 para atras.<br />
<br />
Actualmente la documentación esta enfocada a desarrolladores, que cuentan con la suficiente experiencia en el API nativo de OpenOffice.org y que lo han usado bajo otro lenguaje(Java/C++/StarBasic). Si eres un novato y sientes que alguna información es requerida, te sugerimos buscarla en la "La Guía del Desarrollador".<br />
<br />
<br />
<br />
=== El Tutorial PyUno para OpenOffice.org ===<br />
En este tutorial, mostramos como se puede usar el conector PyUNO para automatizar tareas dentro de OpenOffice.org. Este documento no es un tutorial de OpenOffice.org existen ya muchos documentos enfocados a esta actividad. A continuación mostraremos los pasos a seguir dentro de PyUNO<br />
<br />
<br />
==== Instalación de PyUNO ====<br />
Desde la versión OpenOffice.org 1.1 RC4 para arriba, PyUNO es incluido en la instalación por default. Si tienes una versió anterior a esta puedes saltar el proximo parrafo.<br />
<br />
<br />
Al Usar OpenOffice.org 1.1RC3 o antes, el conector de PyUNO debe ser seleccionado manualmente para su instalación. Escoga entonces la instalación personalizada.<br />
<br />
<br />
y activa el conector de Python-Uno en los componentes opcionales<br />
<br />
<br />
Tambien puedes instalar PyUNO despues de la instalación inicial, corriendo la instalación de OpenOffice.org sombre si misa y seleccionando Modificar en el siguiente dialogo.<br />
<br />
<br />
Nota: Cuando inicias el script de comienzo (eg. install --prefix=/usr/local) para instalación, solo puedes comenzar python despues de la instalación, solo puedes instalar pyuno despues de haber ejecutado el script setup /net y escogido Modify. Nota, que OOo Rc2 el cual no instala dos archivos ini como deviera.<br />
<br />
<br />
<br />
==== Modo del conector PyUNO ====<br />
<br />
<br />
PyUNO puede usar dos metodologías diferentes:<br />
Dentro del ejecutable de Python(y fuera del proceso de OpenOffice.org).<br />
<br />
<br />
Usa esta metodología cuando: <br />
Comienzes a usar python (tiene un enfoque mas intuitivo.<br />
quieres apuntar a ejecuciones del script comenzando procesos separados (ie. cgi-script dentro de un http-server.<br />
Quieres un retorno rapido de codigo-ejecución codigo-ejecución.<br />
<br />
Hola Mundo<br />
<br />
Asegurate, de que OOo no este corriendo(cierra el QuickStarter tambien). Activa una terminal ya sea cmd en WinNT+, command en Win9x o bash en *nix. Ve al directorio donde reside el programa de OpenOffice.org y activa OOo con los siguientes parametros.<br />
:\Program Files\OpenOffice1.1\program> soffice "-accept=socket,host=localhost,port=2002;urp;" <br />
<br />
Ahora comienza el archivo hello_world.py con tu editor de texto favorito e incluye el siguiente codigo.<br />
<code>[python] import uno<br />
<br />
# get the uno component context from the PyUNO runtime<br />
localContext = uno.getComponentContext()<br />
<br />
# create the UnoUrlResolver <br />
resolver = localContext.ServiceManager.createInstanceWithContext(<br />
"com.sun.star.bridge.UnoUrlResolver", localContext )<br />
<br />
# connect to the running office <br />
ctx = resolver.resolve( "uno:socket,host=localhost,port=2002;urp;StarOffice.ComponentContext" )<br />
smgr = ctx.ServiceManager<br />
<br />
# get the central desktop object<br />
desktop = smgr.createInstanceWithContext( "com.sun.star.frame.Desktop",ctx)<br />
<br />
# access the current writer document<br />
model = desktop.getCurrentComponent()<br />
<br />
# access the document's text property<br />
text = model.Text<br />
<br />
# create a cursor<br />
cursor = text.createTextCursor()<br />
<br />
# insert the text into the document<br />
text.insertString( cursor, "Hello World", 0 )<br />
<br />
# Do a nasty thing before exiting the python process. In case the<br />
# last call is a oneway call (e.g. see idl-spec of insertString),<br />
# it must be forced out of the remote-bridge caches before python<br />
# exits the process. Otherwise, the oneway call may or may not reach<br />
# the target object.<br />
# I do this here by calling a cheap synchronous call (getPropertyValue).<br />
ctx.ServiceManager</code><br />
<br />
Ejecuta el script pasado con el siguiente comando<br />
c:\Program Files\OpenOffice1.1\program> .\python hello_world.py <br />
<br />
Este script escribe la cadena Hello World dentro del documento OpenWriter<br />
<br />
==== Dentro del proceso de OpenOffice.org ====<br />
<br />
Usa este modo cuando:<br />
* Quieras facilmente ejecutar tu codigo en multiples maquinas<br />
* Tu codigo sea necesitado por llamadas de otros programas<br />
* Tienes mas experiencia con el funcionamiento de PyUNO.<br />
* Quieres que tu codigo corra con el mejor desempeño<br />
Hola Mundo<br />
<br />
El ejemplo siguiente esta guardado como un componente de UNO, esto significa, que el codigo que ejecuta la insersion necesita ser embedido en una class de python. Aparte, el codigo-de-conexion a la suite necesita ser remplazado por un punto clave, el cual usa el cargador de python para iniciar una clase de python.<br />
hello_world.py<br />
<code>[python]import uno<br />
import unohelper<br />
<br />
from com.sun.star.task import XJobExecutor<br />
<br />
# implement a UNO component by deriving from the standard unohelper.Base class<br />
# and from the interface(s) you want to implement.<br />
class HelloWorldJob( unohelper.Base, XJobExecutor ):<br />
def __init__( self, ctx ):<br />
# store the component context for later use<br />
self.ctx = ctx<br />
<br />
def trigger( self, args ):<br />
# note: args[0] == "HelloWorld", see below config settings<br />
<br />
# retrieve the desktop object<br />
desktop = self.ctx.ServiceManager.createInstanceWithContext(<br />
"com.sun.star.frame.Desktop", self.ctx )<br />
<br />
# get current document model<br />
model = desktop.getCurrentComponent()<br />
<br />
# access the document's text property<br />
text = model.Text<br />
<br />
# create a cursor<br />
cursor = text.createTextCursor()<br />
<br />
# insert the text into the document<br />
text.insertString( cursor, "Hello World", 0 )<br />
<br />
# pythonloader looks for a static g_ImplementationHelper variable<br />
g_ImplementationHelper = unohelper.ImplementationHelper()<br />
<br />
# <br />
g_ImplementationHelper.addImplementation( \<br />
HelloWorldJob, # UNO object class<br />
"org.openoffice.comp.pyuno.demo.HelloWorld", # implemenation name<br />
# Change this name for your own<br />
# script <br />
("com.sun.star.task.Job",),) # list of implemented services<br />
# (the only service)</code><br />
<br />
El codigo necesita ser enlazado a un evento. Esto puede hacerce configurando estas opciones.<br />
Addons.xcu: <br />
<br />
<br />
Both files must be packaged up into a single zip file by using your favourite zip utility, e.g. infozip<br />
<code>[bash]zip hello_world.zip Addons.xcu hello_world_comp.py<br />
adding: Addons.xcu (deflated 55%)<br />
adding: hello_world_comp.py (deflated 55%)</code><br />
<br />
Estos paquetes pueden ser implementados dentro de una instalación de OpenOffice.org usando la herramienta <br />
pkgchk<br />
, el cual esta ubicada en el directorio de program dentro de OOo. Se advierte que OOo debe de estar completamente cerrado. <br />
c:\Program Files\OpenOffice.org1.1\program> pkgchk hello_world.zip<br />
c:\Program Files\OpenOffice.org1.1\program><br />
<br />
Si el proceso se realiza con exito, no tendras ningun reotorno de la herramienta. Y cuando comienzes de nuevo OOo, encontraras una nueva entrada del menu (ver Tools / Aditional Components / Insert Hello World).<br />
<br />
Como puedes ver las lineas de los scripts bases son identicas, pero la forma para extraer los componentes de office difieren.<br />
Ejemplos<br />
* ooextract.py- Una herramienta de linea de comando la cual extrae el contenido de un archivo creado con OpenOffice.org en un modo stout.<br />
* swriter.py- Herramienta de linea de comando la cual crea y llena un documento de Writer con cierto texto y tablas con formato.<br />
* swritercomp.py y swritercompclient.pyIgual que la anterior pero esta esta en modo componente UNO, asi que corre dentro de OpenOffice.org. Uno puede ver la mejora en el desempeño corriendo el componente como un proceso.<br />
biblioaccess.py- Herramienta de linea de comando, que presenta el contenido del la base de datos, biblio, que incluye OpenOffice.org<br />
<br />
=== Conexión al lenguaje UNO ===<br />
<br />
A continuación encontrarás la completa descripción de las herramientas UNO se conectan con el lenguaje de Python.<br />
El typo de mapeo UNOEl tipo de dato IDL<br />
<br />
<br />
tipos de enteros (byte, short, unsigned long, hyper, unsigned hyper Representación en Python<br />
<br />
<br />
Python solo conoce los datatypes encontrados en C long y long long como tipos de enteros. En la mayor parte de las maquinas, un long es un valor de 32 bit mientras long long es de 64 bits.<br />
* Valores de UNO (por ejemplo, retorno del valor de un metodo UNO)<br />
* Valores que tiene los tipos byte, short, unsigned short, long o unsigned, long son convertidos a un valor python long. <br />
* Valores que tienen un tipo de hyper u unsigned hyper son convertidos a python como long long.<br />
* Valores enviados a UNO (por ejemplo, el argumento de un metodo UNO)<br />
<br />
<br />
Si hay un tipo concreto en el metodo IDL, el valor es convertido a un tipo concreto (de hecho el servicio de invoación hace este trabajo). Si el metodo solo contiene un any, cada valor del entero será convertido al typo de dato mas pequeño, donde el valor se ajusta y lo manda al objeto UNO (así que 5 se convierte en un byte, 150 se vuelve short, 0x1f023 un long y los valores mayores a 0xffffffff se convierten en un hyper.<br />
boolean <br />
<br />
<br />
Python tiene, internamente un datatype buleano, el cual es derivado del tipo de entero (ver http://python.org/peps/pep-0285.html ). Ahí existe el True y False, el cual PyUNO usa para distinguir entre valores integrales o buleanos.<br />
<br />
<br />
Mientras el buleano sea especificado en el metodo de interfaz, podrás seguir usando numeros. En los ejemplos siguientes, todas las llamadas son validas:<br />
<code>[python]#idl signature void takeBool( [in] boolean bool )<br />
unoObject.takeBool( 1 ) # valid, passing true (PyUNO runtime<br />
# does the conversion<br />
unoObject.takeBool( True) ) # valid, passing true<br />
unoObject.takeBool( False ) # valid, passing false</code><br />
<br />
Si embargo, cuando quieres especificamente pasar un buleano, cuando solo any es especificado, tu debes usar True y False.<br />
idl signature void foo( [in] any value )<br />
<br />
<code>[python]# implementation expects a boolean (which is separately documented<br />
# e.g. in the service specification.<br />
unoObject.foo( True ) # valid, pass a true<br />
unoObject.foo( 1 ) # bad, just passing a 1, implementation will<br />
# probably not be able to deal with it correctly.</code><br />
<br />
Nota: Tambien existe el uso de la clase uno.Bool, el cual es no es usado desde pyuno 0.9.2 aunque se sigue soportando. Ya no lo usen.<br />
string En general, la cadena esta mapeada dentro de la cadena-unicodigo de python. Sin embargo, quizas pases una cadena de 8-bits cuando se espere una cade de UNO, el conector convierte los 8-bits a una cadena-unicodigo usando el locale del sistema. <br />
<code>[python]# idl signatore foo( [in] string value )<br />
# both lines are valid<br />
unoObject.foo( u'my foo string' )<br />
unoObject.foo( 'my foo string' )<br />
char Un char es mapeado a un uno.Char. Tiene el miembro de una cadena-unicodigo publico con lenght 1 como contenedor del char unicodigo. <br />
# idl signature foo( [in] char c)<br />
unoObject.foo( uno.Char( u'h' ) ) #valid<br />
unoObject.foo( 'h' ) #wrong<br />
<br />
enum </code><br />
<br />
<br />
Un valor enum es representado concretamente por una instancia de la clase uno.Enum. Tiene dos miembros, typeName es una string conteniendo el nombre del tipo enum y value contiene el valor de enum.<br />
<br />
Puedes concretar los valores de enum de dos formas:<br />
<br />
<br />
1.(suggested) by importing<br />
from enumname import enumvalue. <br />
<br />
E.g. <br />
[code]from com.sun.star.uno.TypeClass import UNSIGNED_LONG<br />
.<br />
.<br />
.<br />
unoObject.setValue( UNSIGNED_LONG )<br />
if unoObject.getValue() == UNSIGNED_LONG:[/code]<br />
<br />
<br />
2.(in rare situations)<br />
<br />
<br />
<code>[python]import uno<br />
<br />
unoObject.setValue( uno.Enum( "com.sun.star.uno.TypeClass", "UNSIGNED_LONG") )<br />
if unoObject.getValue() == uno.Enum( "com.sun.star.uno.TypeClass", "UNSIGNED_LONG"):</code><br />
<br />
La primera soluci&ooacute;n tiene la ventaja de que en caso de el fallo en enum manda una RunTimeException o excepción del tiempo de proceso al momento que la fuente de python es importada.<br />
<br />
<br />
''type ''<br />
Un tipo se mapea a uno.type . Tiene miembros publicos llamados typeName (cadenas) y typeClass (el valor enum de com.sun.star.uno.TypeClass). Ahi existe una función uno.getTypeByName() para facilmente crear una instancia de type, las funciones crean un RunTimeException en caso que el type no se conosca.<br />
<br />
Puedes crear valores concretos de dos formas:<br />
1. from module-where-type-lives-in import typeOfTypeName. <br />
<br />
E.g. to create XComponent's type, use <br />
<br />
<br />
from com.sun.star.lang import typeOfXComponent<br />
.<br />
.<br />
.<br />
unoObject.setType( typeOfXComponent )<br />
if unoObject.getType() == typeOfXComponent: <br />
<br />
2.(in rare situations, e.g. for types of simple values)<br />
<br />
<code>[python]<br />
import uno<br />
<br />
unoObject.setType( uno.getTypeByName( "com.sun.star.uno.XComponent" ) )<br />
if unoObject.getType() == uno.getTypeByName( "com.sun.star.uno.XComponent"):<br />
struct (and exception) </code><br />
Para cada uno struct (o excepción), una nueva clase de python es generada al vuelo. La clase generada refleja la jerarquia heredada del tipo UNO (es importante para el administrador de excepciones, ver abajo).<br />
<br />
Uno puede generar una clase struct usando el mecanismo de importación. Una instanacia del struct puede entonces ser instanciada usando el constructor de python. El constructor soporta el argumento cero (miembros obtienen el constructor default), 1 argumento con el mismo tipo (copia el constructor), y n argumentos, donde n es el nombre de elementos que contiene el struct. El struct soporta el operador de equality, dos struct son iguales, si son del mismo type y cada miembro es igual.<br />
<br />
Ejemplo.<br />
<code>[python]<br />
from com.sun.star.beans import PropertyValue<br />
from com.sun.star.uno import Exception,RuntimeException<br />
<br />
propVal = PropertyValue() # Default constructor<br />
propVal.Name = "foo"<br />
propVal.Value = 2<br />
<br />
if propVal == PropertyValue( "foo", 2 ): # Memberwise constructor<br />
# true !<br />
pass<br />
<br />
if propVal == PropertyValue( propVal ): # Copy Constructor<br />
# true </code><br />
<br />
Una instancia del struct UNO puede ser inicialmente construida de la función uno.createUnoStruct() y pasando el nombre de la struct como el primer parametro y el argumento opcional del constructor (ver arriba para un ejemplo de un posible ctors).<br />
<br />
ATENCION: En UNO, struct tiene el valor semantico, sin embargo, la manera como se maneja en python no refleja esto. Cuando el struct es pasado de un parametro a una funcion, el valor es pasado la funcion llamada. Las siguientes modificaciones a la instancia de la struct no afectaran a la funcion llamada. Sin embargo, la simple asignaci&oactue;n de una struct a otra variable local no crea una copia, simplemente crea un alias de la instancia original.<br />
<code>[python]<br />
struct = uno.createUnoStruct( "com.sun.star.beans.PropertyValue" )<br />
<br />
struct.Name = "foo"<br />
struct2 = struct<br />
struct2.Name = "python" # modifies also struct, probably not desired !<br />
unoObject.call( struct, struct2 ) # passes the same struct 2 times !<br />
<br />
struct.Name = "doobidooo" # even worse style. If the UNO object is implemented<br />
# in python, you possibly modify the callee's value.<br />
# Don't do this !<br />
sequence </code><br />
Una secuencia generalmente esta trazada a una tupla de python. Una lista de de python (!) no es aceptada.<br />
<code>[python]# idl signature XInterface createInstanceWithArguments(<br />
# [in] string servicename, [in] sequence )<br />
doc = smgr.createInstanceWithArguments( "foo.service", ("arg1",2))</code><br />
<br />
Atención desde la version 0.9.2 El idl sequence<byte> es trazado a la clase uno.ByteSquence. Tiene un miembro cadena llamado value, el cual contiene los datos de la secuencia de byte. Tal como la bytesequence es generalmente un contenedor para datos binarios, esta clase permite manejar binarios eficientemente. Esto tambien embede pyuno a python, ya que python mantiene datos binarios en cadenas.<br />
<code>[python]# idl signature writeBytes( [in] sequence%lt; byte > data )<br />
#<br />
out.writeBytes( uno.ByteSequence( "abc" ) )<br />
<br />
# you could also write the following<br />
begin = uno.ByteSequence( "ab" )<br />
out.writeBytes( begin + "c" )<br />
<br />
# but this does not work !<br />
out.writeBytes( "abc" ) # ERROR, no implict conversion supported by the runtime !<br />
<br />
<br />
# idl signature long readBytes( [out] sequence , [in] length )<br />
len,seq = in.readBytes( dummy, 3 )<br />
<br />
# the statements do the same thing <br />
print seq == "abc":<br />
print seq == uno.ByteSequence( "abc" )<br />
constants </code><br />
Una constante UNO idl puede ser dada por diferentes maneras:<br />
Usa el valor concreto especificado en el archivo idl<br />
Una constante es su valor y solo su valor. Ya que las modificaciones de los valores de la contacia es incompatible.<br />
Usa el mecanismo de importación para crear variables con un nombre constante<br />
La solución es la mas leida.<br />
Usauno.getConstatByName()<br />
puede ser util de vez en cuando. Las funciones RunTimeException se ejecutan en caso que la constante sea desconocida. <br />
<code>[python]from com.sun.star.beans.PropertyConcept import ATTRIBUTES<br />
.<br />
.<br />
.<br />
# the following 3 lines are equivalent<br />
unoObject.setConcept( ATTRIBUTES )<br />
unoObject.setConcept( 4 )<br />
unoObject.setConcept( uno.getConstantByName( "com.sun.star.beans.PropertyConcept.ATTRIBUTES" ) )<br />
any </code><br />
En general el programador en python nunca llega a tener contacto con anys. Si alguna vez saliera any en un metodo, el programador puede tan solo pasar un valor concreto. Consecuentemente, los retornos de valores o parametros tambien nunca contiene un any concreto.<br />
<br />
Sin embargo, hay ciertas circumstancias, donde el programdor de python quiera pasar un valor type concreto a una funcion que llame (nota, esto es solo posible para llamadas del 'conector', no puedes pasar un valor de type a ningun otro objeto python-uno).<br />
<br />
Puedes crear un uno.Any( ), pasando el type ( como typename o como uno.Type) y su valor.<br />
<code>[python]# constructs a uno.Any, that contains a byte<br />
byteAny = uno.Any( "byte" , 5 )<br />
<br />
# constructs a sequences of shorts<br />
byteAny = uno.Any( "[]short", (4,5))</code><br />
<br />
<br />
Estas anys solo pueden ser usadas junto con el uno.invoke, el cual permite invocar un metodo dentro de un objeto arbitrario con un type any.<br />
<code>[python]# the normal call<br />
uno.setPropertyValue( "foo", (4,5))<br />
<br />
# the uno.invoke call<br />
uno.invoke( obj, "setPropertyValue" , ("foo",uno.Any( "[]short", (4,5))) )</code><br />
<br />
Cuando obj es un objeto conectado, la funcion que se llama obtiene la secuencia como una sequence(short). Cuando obj es un objeto local de python, solo obtiene el (4,5) como si lo hubiera obtenido con la llamada normal.<br />
<br />
=== Implementando los objetos UNO ===<br />
Podras usar clases de python para implementar los objetos UNO. Instancias de python pueden ser pasadas como argumentos a llamados de UNO donde los anys o interfaces concretas hayan sido especificadas.<br />
<br />
Para ser un objeto UNO, una clase de python DEBE implementar la interface com.sun.star.lang.XTypeProvider implementando los metodos getTypes() y getImplementationID(), el cual informa el bridge de python, sobre cual UNO concreta la interfaz con la clase que implementa python. La funci&ooacute;n de getTypes() define que interfaz son definidas por las clases.<br />
<br />
Para hacer esto mas fácil, existe una clase unohelper.Base, donde uno objeto UNO de python se originara de el. Tu puedes entonces implementar una interfaz UNO simpmente originandolo de la interfaz preferida. El siguiente ejemplo implementa la interfaz com.sun.star.lang.XTypeProvider, el cual almacena toda la información escrita en el espacion de una ByteSequence(). (Nota: esta implementació es bastante pobre y es solo con propositos de demostración.<br />
<code>[python]import unohelper<br />
from com.sun.star.io import XOutputStream<br />
class SequenceOutputStream( unohelper.Base, XOutputStream ):<br />
def __init__( self ):<br />
self.s = uno.ByteSequence("")<br />
self.closed = 0<br />
<br />
def closeOutput(self):<br />
self.closed = 1<br />
<br />
def writeBytes( self, seq ):<br />
self.s = self.s + seq<br />
<br />
def flush( self ):<br />
pass<br />
<br />
def getSequence( self ):<br />
return self.s</code><br />
<br />
Desde la lista de clases bases, la implementación unohelper.Base implementa correctamente la interfaz XTypeProvider.<br />
Implementando componentes de Python UNO.<br />
<br />
Existe un cargador de componentes a python. Esto permite crear instancias de clases de python no solo en el proceso de python pero en cual quialquier proceso arbitrario de UNO incluyendo OpenOffice.org. El cargador de python, carga el runtime de python bajo demanda en caso de no estar cargado y ejecutando codigo de python desde el interprete root de python.<br />
<br />
Si el lector no esta familiarizado con el proceso de registro de componentes, entonces se sugiere que vaya el maual de desarrollo de OpenOffice.org para una amplia explicación.<br />
<br />
El cargador de Python actualmente soporta los siguientes protocolos para urls recibidas:Nombre del Protocolo Descripción<br />
vnd.openoffice.pymodule <br />
El protocolo depende en parte interpretado por el nombre del modulo de python, el cual es importado usando el componente de importación comun en python (el cual usa la variable de ambiente de PYTHONPATH).<br />
<br />
Ejemplo. vnd.openoffice.pymodule:MyPythonComponent<br />
<br />
Usando esta url ej. en XLoader.activate() intentara correr al archivo MyPythonComponent.py desde los directorios, los cuales son listados dentro de la variable de ambiente PYTHONPATH. Toma nota que no debes usar el prefijo *.py en este caso.<br />
<br />
El modulo mostrado es agregado al mapeo de sys.modules.<br />
file <br />
Obligatoriamente el url debe ser absoluto al archivo componente de python. El archivo mismo no necesita ser contenido en el PYTHONPATH, simplemente importar los archivos que estan contenidos en el PYTHONPATH. El modulo no es adherido al sys.modules.<br />
<br />
Ejemplo: file:///path/to/MyPythonComponent.py<br />
vnd.sun.star.expand <br />
El cargador de python soporta el mecanismo de expansion de macros tal como los cargadores de Java y C++.<br />
<br />
Ejemplo: vnd.sun.star.expand:$UNO_USER_PACKAGES_CACHE/MyPythonComponent.py<br />
<br />
<br />
Despues de que el modulo esta importado, el cargador de python busca una variable del modulo-global con el nombre g_ImplementationHelper el cual es esperado ser una intancia del unohelper.ImplementationHelper. El siguiente ejemplo hace que un componente de uno fuera de los objetsos UNO ( no es que el componente sea tan útil, por que en esta ocasion no existe un metodo UNO que reciba una tupla tampoco existe especificaci&ooacute;n de servicio com.sun.star.io.OutputStream, solo estan aquí como ejemplo. )<br />
<code>[python]import unohelper<br />
from com.sun.star.io import XOutputStream<br />
<br />
g_ImplementationHelper = unohelper.ImplementationHelper()<br />
<br />
class TupleOutputStream( unohelper.Base, XOutputStream ):<br />
# The component must have a ctor with the component context as argument.<br />
def __init__( self, ctx ):<br />
self.t = ()<br />
self.closed = 0<br />
<br />
# idl void closeOutput();<br />
def closeOutput(self):<br />
self.closed = 1<br />
<br />
# idl void writeBytes( [in] sequence seq );<br />
def writeBytes( self, seq ):<br />
self.t = self.t + seq # simply add the incoming tuple to the member<br />
<br />
# idl void flush();<br />
def flush( self ):<br />
pass<br />
<br />
# convenience function to retrieve the tuple later (no UNO function, may<br />
# only be called from python )<br />
def getTuple( self ):<br />
return self.t<br />
<br />
# add the TupleOutputStream class to the implementation container,<br />
# which the loader uses to register/instantiate the component.<br />
g_ImplementationHelper.addImplementation( \<br />
TupleOutputStream,"org.openoffice.pyuno.PythonOutputStream",<br />
("com.sun.star.io.OutputStream",),)</code><br />
<br />
Asumamos, que este codigo es guardado en un archivo llamado tuplestrm.py y el archivo existe en algun lugar dentro de la variable PYTHONPATH, puede ser registrado al OO1beta construido del siguiente formato:<br />
regcomp -register -br types.rdb -br services.rdb -r services.rdb -c vnd.openoffice.pymodule:tuplestrm <br />
<br />
Claro que tambien puedes usar el pkgchk del tutorial en el capitulo<br />
pkgchk tuplestrm.py <br />
<br />
aunque este comando crea una copia del archivo (cuando el script cambia, debe ser reimplementado usando el comando que sigue. )<br />
<br />
Este componente puede ser llamado desde OpenOffice.org Basic con:<br />
<code>[python]tupleStrm = createUnoService( "com.sun.star.io.OutputStream" )<br />
tupleStrm.flush()</code><br />
[[Category:ES]]</div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=Python_es&diff=156143Python es2010-02-02T08:09:50Z<p>Mauricio: </p>
<hr />
<div>{{Extensions}}<br />
[[image:Py-uno_128.png|PyUNO Logo]] [[image:Pyuno_logo_a.jpg]] <br />
=== Empezando con PyUNO ===<br />
* Que es PyUNO ?<br />
* Que necesito saber? <br />
* Donde empiezo ?<br />
** Desde Linux<br />
** Desde Windows<br />
* Donde guardo mis macros ? <br />
** En el directorio compartido de OpenOffice.org<br />
** En el directorio del usuario<br />
** Dentro de un documento<br />
* Mi primer macro <br />
* PyUNO dentro de OpenOffice.org<br />
* PyUNO fuera de OpenOffice.org<br />
<br />
<br />
Efforts on moving PyUNO to '''Python 2.5''' continue. Liyuan is pushing this initiative and has [http://udk.openoffice.org/servlets/ReadMsg?listName=dev&msgNo=3704 commited the CWS] on the UDK mailing list. The [[CWS]], however, is not ready, and was sent back on issue [http://www.openoffice.org/issues/show_bug.cgi?id=71327 71327].<br />
<br />
=== Python and OpenOffice.org ===<br />
OpenOffice.org ships with the python scripting language, version 2.3.4. This Python distribution comes with the [[Uno]] module, which connects the [[API|UNO API]] to the python scripting language. To run this version of Python on Linux, you can go directly to the OpenOffice.org PATH. And as one would expect with any distribution of Python, OOo-Python can be run from the command line as well.<br />
<br />
==== Where is the IDE ? ====<br />
OpenOffice.org's IDE doesn't support Python, so development has to be done from another editor that does. Any volunteer for a binding is welcomed.<br />
<br />
==== Tips & Tricks ====<br />
<br />
Here is some useful information about using python in OOo.<br />
<br />
===== Debug output =====<br />
<br />
If you launch a python script, any error will silently break the execution, making your extension hard to debug. To change this behaviour, one can change the<br />
'''LogLevel'''<br />
.<br />
<br />
Have a look in <br />
''/path/to/ooo/program/'''pythonscript.py''''' <br />
and replace <br />
''LogLevel.use = LogLevel.'''NONE'''''<br />
with<br />
''LogLevel.use = LogLevel.'''DEBUG'''''<br />
.<br />
<br />
There are also currently-undocumented environment variables that tell the pyUno bridge to log every call. Set the environment variable<br />
''export PYUNO_LOGLEVEL=ARGS''<br />
. The output may be a little hard to read, but helpful nonetheless.<br />
<br />
Note that his applies only to Linux. For Windows, you need some more switches, and the output gets written to files (there is no stdout on windows :-( ).<br />
<br />
There are still some error messages that won't appear in these logs; this will improve in the near future (cws pyunofixes4). Once the cws is integrated, I will document these switches on the official pyuno site. <br />
<br />
''Thanks to Joerg Budischewski''<br />
.<br />
<br />
=== Python specific information for Extension creation ===<br />
To create extensions for python, it is important that you have enough familiarity with the UNO components, as well as with packaging your code for easy distribution through the ''OpenOffice.org package manager''. Please check the tutorials to learn how to component-ize your code, and how to deploy remote scripting through a service implementation.<br />
<br />
To learn to run Python on Windows, visit [[Using Python on Windows| this link]] for more detailed information.<br />
<br />
=== Getting Started ===<br />
*[[Using Python on Windows]] - New to Python? Learn how to use python on Windows<br />
*[[Using Python on Linux]] - A must read for an overview on Python and OOo relations<br />
* [[pyUNO bridge]] - Official page of the PyUNO bridge at the [http://udk.openoffice.org/ UDK site]<br />
* [[Python as a macro language]] in OpenOffice.org 2.x - How to use the Python scripting framework<br />
* [http://lucasmanual.com/mywiki/OpenOffice PyUNO Manual] Lukasz created a pyUNO manual. '''new'''<br />
* [http://www.linuxjournal.com/content/starting-stopping-and-connecting-openoffice-python Starting/Stopping and connecting using Python] From Linux Journal<br />
* Introduction on testing pyUNO programs with [[doctests]]<br />
* Create a [http://codesnippets.services.openoffice.org/Office/Office.MessageBoxWithTheUNOBasedToolkit.snip dialog box] in PyUNO.<br />
* [http://codesnippets.services.openoffice.org/Office/Office.ConnectViaPipe.snip Connect to openoffice.org] from PyUNO<br />
* [[PyUNO samples]] currently shipping with OpenOffice.org and the explanation.<br />
* Enhanced [http://www.oooforum.org/forum/viewtopic.phtml?p=257496#257496 Capitalized.py] script by ''The gray Cardinal'' at OOoforum.<br />
<br />
=== PyUNO Modules ===<br />
*[[Danny's Python Modules]] - Collection guide from DannyB's modules.<br />
*[[PrinttoWriter.py]] - This makes it easy and convenient to print a bunch of text into a Writer document.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=8456 Developing Calc Functions in Python] - Learn how Python can be used to script your spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=56037#56037 Generating a Spreadsheet through Python] - Automatically generate new spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=9115 Python container components]<br />
*[[PyUNOServer]] - The PyUNOServer is a script that works as an XML server for OpenOffice.org Calc<br />
*[[calcParser]] - calcParser is a small parser using the native SAX utilities within the OpenOffice.org python<br />
*[[OoConfig]] - OoConfig is a Python extension that seeks to provide a configuration editing facility similar to Mozilla's about:config<br />
*[[Bibliographic/Hints and Tips/OOoRISExport.py|OOoRISExport.py]] - Exports the bibliographic database in RIS format. Also [http://bibliographic.openoffice.org/files/documents/124/3078/RISImport.py RISImport.py]<br />
*[[Zotero_Plugin |Zotero Plugin]] - The Zotero plugin provides citation and bibliographic table insertion and editing functions for Writer documents.<br />
<br />
=== Hacking Around ===<br />
*[[UNO component packaging]] - How to create UNO components as well as the basics of script componentizing<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=38234#38234 Python component to parse XML] - Python is great to parse XML, PyUNO is also excellent when working with XML<br />
*[[Example of Service in Python]] - Learn how to run Python as a service, this is useful for remote scripting.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=76972#76972 Modify spreadsheet] - Example of storing and retrieving a custom attribute on a spreadsheet cell.<br />
*A simple [[daemon in Python]] - Learn how to run Python as a daemon<br />
*[[Loook.py]] - a simple Python tool that searches for text strings in OpenOffice.org.<br />
*[[odt2txt.py]] - convert ODF to plain text using python (and convert the txt to html).<br />
<br />
=== Python rules OOo (by B. Bois) ===<br />
[[image:python_power_for_OOo.png|Python rules OOo :-)]]<br />
<br />
<br />
<br />
[[Category:Extensions]]<br />
[[Category:Python]]<br />
[[Category:Uno]]</div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=Python_es&diff=156142Python es2010-02-02T08:08:45Z<p>Mauricio: </p>
<hr />
<div>{{Extensions}}<br />
[[image:Py-uno_128.png|PyUNO Logo]] [[image:Pyuno_logo_a.jpg]] <br />
=== Empezando con PyUNO ===<br />
* Que es PyUNO ?<br />
* Que necesito saber? <br />
* Donde empiezo ?<br />
** Desde Linux<br />
** Desde Windows<br />
* Donde guardo mis macros ? <br />
** En el directorio compartido de OpenOffice.org<br />
** En el directorio del usuario<br />
** Dentro de un documento<br />
* Mi primer macro ?<br />
* PyUNO dentro de OpenOffice.org<br />
* PyUNO fuera de OpenOffice.org<br />
<br />
<br />
Efforts on moving PyUNO to '''Python 2.5''' continue. Liyuan is pushing this initiative and has [http://udk.openoffice.org/servlets/ReadMsg?listName=dev&msgNo=3704 commited the CWS] on the UDK mailing list. The [[CWS]], however, is not ready, and was sent back on issue [http://www.openoffice.org/issues/show_bug.cgi?id=71327 71327].<br />
<br />
=== Python and OpenOffice.org ===<br />
OpenOffice.org ships with the python scripting language, version 2.3.4. This Python distribution comes with the [[Uno]] module, which connects the [[API|UNO API]] to the python scripting language. To run this version of Python on Linux, you can go directly to the OpenOffice.org PATH. And as one would expect with any distribution of Python, OOo-Python can be run from the command line as well.<br />
<br />
==== Where is the IDE ? ====<br />
OpenOffice.org's IDE doesn't support Python, so development has to be done from another editor that does. Any volunteer for a binding is welcomed.<br />
<br />
==== Tips & Tricks ====<br />
<br />
Here is some useful information about using python in OOo.<br />
<br />
===== Debug output =====<br />
<br />
If you launch a python script, any error will silently break the execution, making your extension hard to debug. To change this behaviour, one can change the<br />
'''LogLevel'''<br />
.<br />
<br />
Have a look in <br />
''/path/to/ooo/program/'''pythonscript.py''''' <br />
and replace <br />
''LogLevel.use = LogLevel.'''NONE'''''<br />
with<br />
''LogLevel.use = LogLevel.'''DEBUG'''''<br />
.<br />
<br />
There are also currently-undocumented environment variables that tell the pyUno bridge to log every call. Set the environment variable<br />
''export PYUNO_LOGLEVEL=ARGS''<br />
. The output may be a little hard to read, but helpful nonetheless.<br />
<br />
Note that his applies only to Linux. For Windows, you need some more switches, and the output gets written to files (there is no stdout on windows :-( ).<br />
<br />
There are still some error messages that won't appear in these logs; this will improve in the near future (cws pyunofixes4). Once the cws is integrated, I will document these switches on the official pyuno site. <br />
<br />
''Thanks to Joerg Budischewski''<br />
.<br />
<br />
=== Python specific information for Extension creation ===<br />
To create extensions for python, it is important that you have enough familiarity with the UNO components, as well as with packaging your code for easy distribution through the ''OpenOffice.org package manager''. Please check the tutorials to learn how to component-ize your code, and how to deploy remote scripting through a service implementation.<br />
<br />
To learn to run Python on Windows, visit [[Using Python on Windows| this link]] for more detailed information.<br />
<br />
=== Getting Started ===<br />
*[[Using Python on Windows]] - New to Python? Learn how to use python on Windows<br />
*[[Using Python on Linux]] - A must read for an overview on Python and OOo relations<br />
* [[pyUNO bridge]] - Official page of the PyUNO bridge at the [http://udk.openoffice.org/ UDK site]<br />
* [[Python as a macro language]] in OpenOffice.org 2.x - How to use the Python scripting framework<br />
* [http://lucasmanual.com/mywiki/OpenOffice PyUNO Manual] Lukasz created a pyUNO manual. '''new'''<br />
* [http://www.linuxjournal.com/content/starting-stopping-and-connecting-openoffice-python Starting/Stopping and connecting using Python] From Linux Journal<br />
* Introduction on testing pyUNO programs with [[doctests]]<br />
* Create a [http://codesnippets.services.openoffice.org/Office/Office.MessageBoxWithTheUNOBasedToolkit.snip dialog box] in PyUNO.<br />
* [http://codesnippets.services.openoffice.org/Office/Office.ConnectViaPipe.snip Connect to openoffice.org] from PyUNO<br />
* [[PyUNO samples]] currently shipping with OpenOffice.org and the explanation.<br />
* Enhanced [http://www.oooforum.org/forum/viewtopic.phtml?p=257496#257496 Capitalized.py] script by ''The gray Cardinal'' at OOoforum.<br />
<br />
=== PyUNO Modules ===<br />
*[[Danny's Python Modules]] - Collection guide from DannyB's modules.<br />
*[[PrinttoWriter.py]] - This makes it easy and convenient to print a bunch of text into a Writer document.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=8456 Developing Calc Functions in Python] - Learn how Python can be used to script your spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=56037#56037 Generating a Spreadsheet through Python] - Automatically generate new spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=9115 Python container components]<br />
*[[PyUNOServer]] - The PyUNOServer is a script that works as an XML server for OpenOffice.org Calc<br />
*[[calcParser]] - calcParser is a small parser using the native SAX utilities within the OpenOffice.org python<br />
*[[OoConfig]] - OoConfig is a Python extension that seeks to provide a configuration editing facility similar to Mozilla's about:config<br />
*[[Bibliographic/Hints and Tips/OOoRISExport.py|OOoRISExport.py]] - Exports the bibliographic database in RIS format. Also [http://bibliographic.openoffice.org/files/documents/124/3078/RISImport.py RISImport.py]<br />
*[[Zotero_Plugin |Zotero Plugin]] - The Zotero plugin provides citation and bibliographic table insertion and editing functions for Writer documents.<br />
<br />
=== Hacking Around ===<br />
*[[UNO component packaging]] - How to create UNO components as well as the basics of script componentizing<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=38234#38234 Python component to parse XML] - Python is great to parse XML, PyUNO is also excellent when working with XML<br />
*[[Example of Service in Python]] - Learn how to run Python as a service, this is useful for remote scripting.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=76972#76972 Modify spreadsheet] - Example of storing and retrieving a custom attribute on a spreadsheet cell.<br />
*A simple [[daemon in Python]] - Learn how to run Python as a daemon<br />
*[[Loook.py]] - a simple Python tool that searches for text strings in OpenOffice.org.<br />
*[[odt2txt.py]] - convert ODF to plain text using python (and convert the txt to html).<br />
<br />
=== Python rules OOo (by B. Bois) ===<br />
[[image:python_power_for_OOo.png|Python rules OOo :-)]]<br />
<br />
<br />
<br />
[[Category:Extensions]]<br />
[[Category:Python]]<br />
[[Category:Uno]]</div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=Python_es&diff=156141Python es2010-02-02T08:07:10Z<p>Mauricio: </p>
<hr />
<div>{{Extensions}}<br />
[[image:Py-uno_128.png|PyUNO Logo]] [[image:Pyuno_logo_a.jpg]] <br />
=== Empezando con PyUNO ===<br />
* Que es PyUNO ?<br />
* Que necesito saber? <br />
* Donde empiezo ?<br />
** Desde Linux<br />
** Desde Windows<br />
* Donde guardo mis macros ? <br />
** En el directorio compartido de OpenOffice.org<br />
** En el directorio del usuario<br />
** Dentro de un documento<br />
* Mi primer macro ?<br />
* PyUNO dentro de OpenOffice.org<br />
* PyUNO fuera de OPenOffice.org<br />
<br />
<br />
Efforts on moving PyUNO to '''Python 2.5''' continue. Liyuan is pushing this initiative and has [http://udk.openoffice.org/servlets/ReadMsg?listName=dev&msgNo=3704 commited the CWS] on the UDK mailing list. The [[CWS]], however, is not ready, and was sent back on issue [http://www.openoffice.org/issues/show_bug.cgi?id=71327 71327].<br />
<br />
=== Python and OpenOffice.org ===<br />
OpenOffice.org ships with the python scripting language, version 2.3.4. This Python distribution comes with the [[Uno]] module, which connects the [[API|UNO API]] to the python scripting language. To run this version of Python on Linux, you can go directly to the OpenOffice.org PATH. And as one would expect with any distribution of Python, OOo-Python can be run from the command line as well.<br />
<br />
==== Where is the IDE ? ====<br />
OpenOffice.org's IDE doesn't support Python, so development has to be done from another editor that does. Any volunteer for a binding is welcomed.<br />
<br />
==== Tips & Tricks ====<br />
<br />
Here is some useful information about using python in OOo.<br />
<br />
===== Debug output =====<br />
<br />
If you launch a python script, any error will silently break the execution, making your extension hard to debug. To change this behaviour, one can change the<br />
'''LogLevel'''<br />
.<br />
<br />
Have a look in <br />
''/path/to/ooo/program/'''pythonscript.py''''' <br />
and replace <br />
''LogLevel.use = LogLevel.'''NONE'''''<br />
with<br />
''LogLevel.use = LogLevel.'''DEBUG'''''<br />
.<br />
<br />
There are also currently-undocumented environment variables that tell the pyUno bridge to log every call. Set the environment variable<br />
''export PYUNO_LOGLEVEL=ARGS''<br />
. The output may be a little hard to read, but helpful nonetheless.<br />
<br />
Note that his applies only to Linux. For Windows, you need some more switches, and the output gets written to files (there is no stdout on windows :-( ).<br />
<br />
There are still some error messages that won't appear in these logs; this will improve in the near future (cws pyunofixes4). Once the cws is integrated, I will document these switches on the official pyuno site. <br />
<br />
''Thanks to Joerg Budischewski''<br />
.<br />
<br />
=== Python specific information for Extension creation ===<br />
To create extensions for python, it is important that you have enough familiarity with the UNO components, as well as with packaging your code for easy distribution through the ''OpenOffice.org package manager''. Please check the tutorials to learn how to component-ize your code, and how to deploy remote scripting through a service implementation.<br />
<br />
To learn to run Python on Windows, visit [[Using Python on Windows| this link]] for more detailed information.<br />
<br />
=== Getting Started ===<br />
*[[Using Python on Windows]] - New to Python? Learn how to use python on Windows<br />
*[[Using Python on Linux]] - A must read for an overview on Python and OOo relations<br />
* [[pyUNO bridge]] - Official page of the PyUNO bridge at the [http://udk.openoffice.org/ UDK site]<br />
* [[Python as a macro language]] in OpenOffice.org 2.x - How to use the Python scripting framework<br />
* [http://lucasmanual.com/mywiki/OpenOffice PyUNO Manual] Lukasz created a pyUNO manual. '''new'''<br />
* [http://www.linuxjournal.com/content/starting-stopping-and-connecting-openoffice-python Starting/Stopping and connecting using Python] From Linux Journal<br />
* Introduction on testing pyUNO programs with [[doctests]]<br />
* Create a [http://codesnippets.services.openoffice.org/Office/Office.MessageBoxWithTheUNOBasedToolkit.snip dialog box] in PyUNO.<br />
* [http://codesnippets.services.openoffice.org/Office/Office.ConnectViaPipe.snip Connect to openoffice.org] from PyUNO<br />
* [[PyUNO samples]] currently shipping with OpenOffice.org and the explanation.<br />
* Enhanced [http://www.oooforum.org/forum/viewtopic.phtml?p=257496#257496 Capitalized.py] script by ''The gray Cardinal'' at OOoforum.<br />
<br />
=== PyUNO Modules ===<br />
*[[Danny's Python Modules]] - Collection guide from DannyB's modules.<br />
*[[PrinttoWriter.py]] - This makes it easy and convenient to print a bunch of text into a Writer document.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=8456 Developing Calc Functions in Python] - Learn how Python can be used to script your spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=56037#56037 Generating a Spreadsheet through Python] - Automatically generate new spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=9115 Python container components]<br />
*[[PyUNOServer]] - The PyUNOServer is a script that works as an XML server for OpenOffice.org Calc<br />
*[[calcParser]] - calcParser is a small parser using the native SAX utilities within the OpenOffice.org python<br />
*[[OoConfig]] - OoConfig is a Python extension that seeks to provide a configuration editing facility similar to Mozilla's about:config<br />
*[[Bibliographic/Hints and Tips/OOoRISExport.py|OOoRISExport.py]] - Exports the bibliographic database in RIS format. Also [http://bibliographic.openoffice.org/files/documents/124/3078/RISImport.py RISImport.py]<br />
*[[Zotero_Plugin |Zotero Plugin]] - The Zotero plugin provides citation and bibliographic table insertion and editing functions for Writer documents.<br />
<br />
=== Hacking Around ===<br />
*[[UNO component packaging]] - How to create UNO components as well as the basics of script componentizing<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=38234#38234 Python component to parse XML] - Python is great to parse XML, PyUNO is also excellent when working with XML<br />
*[[Example of Service in Python]] - Learn how to run Python as a service, this is useful for remote scripting.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=76972#76972 Modify spreadsheet] - Example of storing and retrieving a custom attribute on a spreadsheet cell.<br />
*A simple [[daemon in Python]] - Learn how to run Python as a daemon<br />
*[[Loook.py]] - a simple Python tool that searches for text strings in OpenOffice.org.<br />
*[[odt2txt.py]] - convert ODF to plain text using python (and convert the txt to html).<br />
<br />
=== Python rules OOo (by B. Bois) ===<br />
[[image:python_power_for_OOo.png|Python rules OOo :-)]]<br />
<br />
<br />
<br />
[[Category:Extensions]]<br />
[[Category:Python]]<br />
[[Category:Uno]]</div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=Python_es&diff=156140Python es2010-02-02T08:06:21Z<p>Mauricio: </p>
<hr />
<div>{{Extensions}}<br />
[[image:Py-uno_128.png|PyUNO Logo]] [[image:Pyuno_logo_a.jpg]] <br />
=== Empezando con PyUNO ===<br />
* Que es PyUno ?<br />
* Que necesito saber? <br />
* Donde empiezo ?<br />
** Desde Linux<br />
** Desde Windows<br />
* Donde guardo mis macros ? <br />
** En el directorio compartido de OpenOffice.org<br />
** En el directorio del usuario<br />
** Dentro de un documento<br />
* Mi primer macro ?<br />
* PyUNO dentro de OpenOffice.org<br />
* PyUNO fuera de OPenOffice.org<br />
<br />
<br />
Efforts on moving PyUNO to '''Python 2.5''' continue. Liyuan is pushing this initiative and has [http://udk.openoffice.org/servlets/ReadMsg?listName=dev&msgNo=3704 commited the CWS] on the UDK mailing list. The [[CWS]], however, is not ready, and was sent back on issue [http://www.openoffice.org/issues/show_bug.cgi?id=71327 71327].<br />
<br />
=== Python and OpenOffice.org ===<br />
OpenOffice.org ships with the python scripting language, version 2.3.4. This Python distribution comes with the [[Uno]] module, which connects the [[API|UNO API]] to the python scripting language. To run this version of Python on Linux, you can go directly to the OpenOffice.org PATH. And as one would expect with any distribution of Python, OOo-Python can be run from the command line as well.<br />
<br />
==== Where is the IDE ? ====<br />
OpenOffice.org's IDE doesn't support Python, so development has to be done from another editor that does. Any volunteer for a binding is welcomed.<br />
<br />
==== Tips & Tricks ====<br />
<br />
Here is some useful information about using python in OOo.<br />
<br />
===== Debug output =====<br />
<br />
If you launch a python script, any error will silently break the execution, making your extension hard to debug. To change this behaviour, one can change the<br />
'''LogLevel'''<br />
.<br />
<br />
Have a look in <br />
''/path/to/ooo/program/'''pythonscript.py''''' <br />
and replace <br />
''LogLevel.use = LogLevel.'''NONE'''''<br />
with<br />
''LogLevel.use = LogLevel.'''DEBUG'''''<br />
.<br />
<br />
There are also currently-undocumented environment variables that tell the pyUno bridge to log every call. Set the environment variable<br />
''export PYUNO_LOGLEVEL=ARGS''<br />
. The output may be a little hard to read, but helpful nonetheless.<br />
<br />
Note that his applies only to Linux. For Windows, you need some more switches, and the output gets written to files (there is no stdout on windows :-( ).<br />
<br />
There are still some error messages that won't appear in these logs; this will improve in the near future (cws pyunofixes4). Once the cws is integrated, I will document these switches on the official pyuno site. <br />
<br />
''Thanks to Joerg Budischewski''<br />
.<br />
<br />
=== Python specific information for Extension creation ===<br />
To create extensions for python, it is important that you have enough familiarity with the UNO components, as well as with packaging your code for easy distribution through the ''OpenOffice.org package manager''. Please check the tutorials to learn how to component-ize your code, and how to deploy remote scripting through a service implementation.<br />
<br />
To learn to run Python on Windows, visit [[Using Python on Windows| this link]] for more detailed information.<br />
<br />
=== Getting Started ===<br />
*[[Using Python on Windows]] - New to Python? Learn how to use python on Windows<br />
*[[Using Python on Linux]] - A must read for an overview on Python and OOo relations<br />
* [[pyUNO bridge]] - Official page of the PyUNO bridge at the [http://udk.openoffice.org/ UDK site]<br />
* [[Python as a macro language]] in OpenOffice.org 2.x - How to use the Python scripting framework<br />
* [http://lucasmanual.com/mywiki/OpenOffice PyUNO Manual] Lukasz created a pyUNO manual. '''new'''<br />
* [http://www.linuxjournal.com/content/starting-stopping-and-connecting-openoffice-python Starting/Stopping and connecting using Python] From Linux Journal<br />
* Introduction on testing pyUNO programs with [[doctests]]<br />
* Create a [http://codesnippets.services.openoffice.org/Office/Office.MessageBoxWithTheUNOBasedToolkit.snip dialog box] in PyUNO.<br />
* [http://codesnippets.services.openoffice.org/Office/Office.ConnectViaPipe.snip Connect to openoffice.org] from PyUNO<br />
* [[PyUNO samples]] currently shipping with OpenOffice.org and the explanation.<br />
* Enhanced [http://www.oooforum.org/forum/viewtopic.phtml?p=257496#257496 Capitalized.py] script by ''The gray Cardinal'' at OOoforum.<br />
<br />
=== PyUNO Modules ===<br />
*[[Danny's Python Modules]] - Collection guide from DannyB's modules.<br />
*[[PrinttoWriter.py]] - This makes it easy and convenient to print a bunch of text into a Writer document.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=8456 Developing Calc Functions in Python] - Learn how Python can be used to script your spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=56037#56037 Generating a Spreadsheet through Python] - Automatically generate new spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=9115 Python container components]<br />
*[[PyUNOServer]] - The PyUNOServer is a script that works as an XML server for OpenOffice.org Calc<br />
*[[calcParser]] - calcParser is a small parser using the native SAX utilities within the OpenOffice.org python<br />
*[[OoConfig]] - OoConfig is a Python extension that seeks to provide a configuration editing facility similar to Mozilla's about:config<br />
*[[Bibliographic/Hints and Tips/OOoRISExport.py|OOoRISExport.py]] - Exports the bibliographic database in RIS format. Also [http://bibliographic.openoffice.org/files/documents/124/3078/RISImport.py RISImport.py]<br />
*[[Zotero_Plugin |Zotero Plugin]] - The Zotero plugin provides citation and bibliographic table insertion and editing functions for Writer documents.<br />
<br />
=== Hacking Around ===<br />
*[[UNO component packaging]] - How to create UNO components as well as the basics of script componentizing<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=38234#38234 Python component to parse XML] - Python is great to parse XML, PyUNO is also excellent when working with XML<br />
*[[Example of Service in Python]] - Learn how to run Python as a service, this is useful for remote scripting.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=76972#76972 Modify spreadsheet] - Example of storing and retrieving a custom attribute on a spreadsheet cell.<br />
*A simple [[daemon in Python]] - Learn how to run Python as a daemon<br />
*[[Loook.py]] - a simple Python tool that searches for text strings in OpenOffice.org.<br />
*[[odt2txt.py]] - convert ODF to plain text using python (and convert the txt to html).<br />
<br />
=== Python rules OOo (by B. Bois) ===<br />
[[image:python_power_for_OOo.png|Python rules OOo :-)]]<br />
<br />
<br />
<br />
[[Category:Extensions]]<br />
[[Category:Python]]<br />
[[Category:Uno]]</div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=Python_es&diff=156139Python es2010-02-02T08:05:45Z<p>Mauricio: </p>
<hr />
<div>{{Extensions}}<br />
[[image:Py-uno_128.png|PyUNO Logo]] [[image:Pyuno_logo_a.jpg]] <br />
=== Empezando con PyUNO ===<br />
* Que es PyUno ?<br />
* Que necesito saber? <br />
* Donde empiezo ?<br />
** Desde Linux<br />
** Desde Windows<br />
* Donde guardo mis macros ? <br />
** En el directorio compartido de OpenOffice.org<br />
** En el directorio del usuario<br />
** Dentro de un documento<br />
* Mi primer macro ?<br />
* PyUNO dentro de OpenOffice.org<br />
* PyUNo fuera de OPenOffice.org<br />
<br />
<br />
Efforts on moving PyUNO to '''Python 2.5''' continue. Liyuan is pushing this initiative and has [http://udk.openoffice.org/servlets/ReadMsg?listName=dev&msgNo=3704 commited the CWS] on the UDK mailing list. The [[CWS]], however, is not ready, and was sent back on issue [http://www.openoffice.org/issues/show_bug.cgi?id=71327 71327].<br />
<br />
=== Python and OpenOffice.org ===<br />
OpenOffice.org ships with the python scripting language, version 2.3.4. This Python distribution comes with the [[Uno]] module, which connects the [[API|UNO API]] to the python scripting language. To run this version of Python on Linux, you can go directly to the OpenOffice.org PATH. And as one would expect with any distribution of Python, OOo-Python can be run from the command line as well.<br />
<br />
==== Where is the IDE ? ====<br />
OpenOffice.org's IDE doesn't support Python, so development has to be done from another editor that does. Any volunteer for a binding is welcomed.<br />
<br />
==== Tips & Tricks ====<br />
<br />
Here is some useful information about using python in OOo.<br />
<br />
===== Debug output =====<br />
<br />
If you launch a python script, any error will silently break the execution, making your extension hard to debug. To change this behaviour, one can change the<br />
'''LogLevel'''<br />
.<br />
<br />
Have a look in <br />
''/path/to/ooo/program/'''pythonscript.py''''' <br />
and replace <br />
''LogLevel.use = LogLevel.'''NONE'''''<br />
with<br />
''LogLevel.use = LogLevel.'''DEBUG'''''<br />
.<br />
<br />
There are also currently-undocumented environment variables that tell the pyUno bridge to log every call. Set the environment variable<br />
''export PYUNO_LOGLEVEL=ARGS''<br />
. The output may be a little hard to read, but helpful nonetheless.<br />
<br />
Note that his applies only to Linux. For Windows, you need some more switches, and the output gets written to files (there is no stdout on windows :-( ).<br />
<br />
There are still some error messages that won't appear in these logs; this will improve in the near future (cws pyunofixes4). Once the cws is integrated, I will document these switches on the official pyuno site. <br />
<br />
''Thanks to Joerg Budischewski''<br />
.<br />
<br />
=== Python specific information for Extension creation ===<br />
To create extensions for python, it is important that you have enough familiarity with the UNO components, as well as with packaging your code for easy distribution through the ''OpenOffice.org package manager''. Please check the tutorials to learn how to component-ize your code, and how to deploy remote scripting through a service implementation.<br />
<br />
To learn to run Python on Windows, visit [[Using Python on Windows| this link]] for more detailed information.<br />
<br />
=== Getting Started ===<br />
*[[Using Python on Windows]] - New to Python? Learn how to use python on Windows<br />
*[[Using Python on Linux]] - A must read for an overview on Python and OOo relations<br />
* [[pyUNO bridge]] - Official page of the PyUNO bridge at the [http://udk.openoffice.org/ UDK site]<br />
* [[Python as a macro language]] in OpenOffice.org 2.x - How to use the Python scripting framework<br />
* [http://lucasmanual.com/mywiki/OpenOffice PyUNO Manual] Lukasz created a pyUNO manual. '''new'''<br />
* [http://www.linuxjournal.com/content/starting-stopping-and-connecting-openoffice-python Starting/Stopping and connecting using Python] From Linux Journal<br />
* Introduction on testing pyUNO programs with [[doctests]]<br />
* Create a [http://codesnippets.services.openoffice.org/Office/Office.MessageBoxWithTheUNOBasedToolkit.snip dialog box] in PyUNO.<br />
* [http://codesnippets.services.openoffice.org/Office/Office.ConnectViaPipe.snip Connect to openoffice.org] from PyUNO<br />
* [[PyUNO samples]] currently shipping with OpenOffice.org and the explanation.<br />
* Enhanced [http://www.oooforum.org/forum/viewtopic.phtml?p=257496#257496 Capitalized.py] script by ''The gray Cardinal'' at OOoforum.<br />
<br />
=== PyUNO Modules ===<br />
*[[Danny's Python Modules]] - Collection guide from DannyB's modules.<br />
*[[PrinttoWriter.py]] - This makes it easy and convenient to print a bunch of text into a Writer document.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=8456 Developing Calc Functions in Python] - Learn how Python can be used to script your spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=56037#56037 Generating a Spreadsheet through Python] - Automatically generate new spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=9115 Python container components]<br />
*[[PyUNOServer]] - The PyUNOServer is a script that works as an XML server for OpenOffice.org Calc<br />
*[[calcParser]] - calcParser is a small parser using the native SAX utilities within the OpenOffice.org python<br />
*[[OoConfig]] - OoConfig is a Python extension that seeks to provide a configuration editing facility similar to Mozilla's about:config<br />
*[[Bibliographic/Hints and Tips/OOoRISExport.py|OOoRISExport.py]] - Exports the bibliographic database in RIS format. Also [http://bibliographic.openoffice.org/files/documents/124/3078/RISImport.py RISImport.py]<br />
*[[Zotero_Plugin |Zotero Plugin]] - The Zotero plugin provides citation and bibliographic table insertion and editing functions for Writer documents.<br />
<br />
=== Hacking Around ===<br />
*[[UNO component packaging]] - How to create UNO components as well as the basics of script componentizing<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=38234#38234 Python component to parse XML] - Python is great to parse XML, PyUNO is also excellent when working with XML<br />
*[[Example of Service in Python]] - Learn how to run Python as a service, this is useful for remote scripting.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=76972#76972 Modify spreadsheet] - Example of storing and retrieving a custom attribute on a spreadsheet cell.<br />
*A simple [[daemon in Python]] - Learn how to run Python as a daemon<br />
*[[Loook.py]] - a simple Python tool that searches for text strings in OpenOffice.org.<br />
*[[odt2txt.py]] - convert ODF to plain text using python (and convert the txt to html).<br />
<br />
=== Python rules OOo (by B. Bois) ===<br />
[[image:python_power_for_OOo.png|Python rules OOo :-)]]<br />
<br />
<br />
<br />
[[Category:Extensions]]<br />
[[Category:Python]]<br />
[[Category:Uno]]</div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=Python_es&diff=156138Python es2010-02-02T08:02:35Z<p>Mauricio: </p>
<hr />
<div>{{Extensions}}<br />
[[image:Py-uno_128.png|PyUNO Logo]] [[image:Pyuno_logo_a.jpg]] <br />
=== Empezando con PyUNO ===<br />
* Que es PyUno ?<br />
* Que necesito saber? <br />
* Donde empiezo ?<br />
** Desde Linux<br />
** Desde Windows<br />
* Donde guardo mis macros ? <br />
* Mi primer macro ?<br />
* PyUNO dentro de OpenOffice.org<br />
* PyUNo fuera de OPenOffice.org<br />
<br />
<br />
Efforts on moving PyUNO to '''Python 2.5''' continue. Liyuan is pushing this initiative and has [http://udk.openoffice.org/servlets/ReadMsg?listName=dev&msgNo=3704 commited the CWS] on the UDK mailing list. The [[CWS]], however, is not ready, and was sent back on issue [http://www.openoffice.org/issues/show_bug.cgi?id=71327 71327].<br />
<br />
=== Python and OpenOffice.org ===<br />
OpenOffice.org ships with the python scripting language, version 2.3.4. This Python distribution comes with the [[Uno]] module, which connects the [[API|UNO API]] to the python scripting language. To run this version of Python on Linux, you can go directly to the OpenOffice.org PATH. And as one would expect with any distribution of Python, OOo-Python can be run from the command line as well.<br />
<br />
==== Where is the IDE ? ====<br />
OpenOffice.org's IDE doesn't support Python, so development has to be done from another editor that does. Any volunteer for a binding is welcomed.<br />
<br />
==== Tips & Tricks ====<br />
<br />
Here is some useful information about using python in OOo.<br />
<br />
===== Debug output =====<br />
<br />
If you launch a python script, any error will silently break the execution, making your extension hard to debug. To change this behaviour, one can change the<br />
'''LogLevel'''<br />
.<br />
<br />
Have a look in <br />
''/path/to/ooo/program/'''pythonscript.py''''' <br />
and replace <br />
''LogLevel.use = LogLevel.'''NONE'''''<br />
with<br />
''LogLevel.use = LogLevel.'''DEBUG'''''<br />
.<br />
<br />
There are also currently-undocumented environment variables that tell the pyUno bridge to log every call. Set the environment variable<br />
''export PYUNO_LOGLEVEL=ARGS''<br />
. The output may be a little hard to read, but helpful nonetheless.<br />
<br />
Note that his applies only to Linux. For Windows, you need some more switches, and the output gets written to files (there is no stdout on windows :-( ).<br />
<br />
There are still some error messages that won't appear in these logs; this will improve in the near future (cws pyunofixes4). Once the cws is integrated, I will document these switches on the official pyuno site. <br />
<br />
''Thanks to Joerg Budischewski''<br />
.<br />
<br />
=== Python specific information for Extension creation ===<br />
To create extensions for python, it is important that you have enough familiarity with the UNO components, as well as with packaging your code for easy distribution through the ''OpenOffice.org package manager''. Please check the tutorials to learn how to component-ize your code, and how to deploy remote scripting through a service implementation.<br />
<br />
To learn to run Python on Windows, visit [[Using Python on Windows| this link]] for more detailed information.<br />
<br />
=== Getting Started ===<br />
*[[Using Python on Windows]] - New to Python? Learn how to use python on Windows<br />
*[[Using Python on Linux]] - A must read for an overview on Python and OOo relations<br />
* [[pyUNO bridge]] - Official page of the PyUNO bridge at the [http://udk.openoffice.org/ UDK site]<br />
* [[Python as a macro language]] in OpenOffice.org 2.x - How to use the Python scripting framework<br />
* [http://lucasmanual.com/mywiki/OpenOffice PyUNO Manual] Lukasz created a pyUNO manual. '''new'''<br />
* [http://www.linuxjournal.com/content/starting-stopping-and-connecting-openoffice-python Starting/Stopping and connecting using Python] From Linux Journal<br />
* Introduction on testing pyUNO programs with [[doctests]]<br />
* Create a [http://codesnippets.services.openoffice.org/Office/Office.MessageBoxWithTheUNOBasedToolkit.snip dialog box] in PyUNO.<br />
* [http://codesnippets.services.openoffice.org/Office/Office.ConnectViaPipe.snip Connect to openoffice.org] from PyUNO<br />
* [[PyUNO samples]] currently shipping with OpenOffice.org and the explanation.<br />
* Enhanced [http://www.oooforum.org/forum/viewtopic.phtml?p=257496#257496 Capitalized.py] script by ''The gray Cardinal'' at OOoforum.<br />
<br />
=== PyUNO Modules ===<br />
*[[Danny's Python Modules]] - Collection guide from DannyB's modules.<br />
*[[PrinttoWriter.py]] - This makes it easy and convenient to print a bunch of text into a Writer document.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=8456 Developing Calc Functions in Python] - Learn how Python can be used to script your spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=56037#56037 Generating a Spreadsheet through Python] - Automatically generate new spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=9115 Python container components]<br />
*[[PyUNOServer]] - The PyUNOServer is a script that works as an XML server for OpenOffice.org Calc<br />
*[[calcParser]] - calcParser is a small parser using the native SAX utilities within the OpenOffice.org python<br />
*[[OoConfig]] - OoConfig is a Python extension that seeks to provide a configuration editing facility similar to Mozilla's about:config<br />
*[[Bibliographic/Hints and Tips/OOoRISExport.py|OOoRISExport.py]] - Exports the bibliographic database in RIS format. Also [http://bibliographic.openoffice.org/files/documents/124/3078/RISImport.py RISImport.py]<br />
*[[Zotero_Plugin |Zotero Plugin]] - The Zotero plugin provides citation and bibliographic table insertion and editing functions for Writer documents.<br />
<br />
=== Hacking Around ===<br />
*[[UNO component packaging]] - How to create UNO components as well as the basics of script componentizing<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=38234#38234 Python component to parse XML] - Python is great to parse XML, PyUNO is also excellent when working with XML<br />
*[[Example of Service in Python]] - Learn how to run Python as a service, this is useful for remote scripting.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=76972#76972 Modify spreadsheet] - Example of storing and retrieving a custom attribute on a spreadsheet cell.<br />
*A simple [[daemon in Python]] - Learn how to run Python as a daemon<br />
*[[Loook.py]] - a simple Python tool that searches for text strings in OpenOffice.org.<br />
*[[odt2txt.py]] - convert ODF to plain text using python (and convert the txt to html).<br />
<br />
=== Python rules OOo (by B. Bois) ===<br />
[[image:python_power_for_OOo.png|Python rules OOo :-)]]<br />
<br />
<br />
<br />
[[Category:Extensions]]<br />
[[Category:Python]]<br />
[[Category:Uno]]</div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=Python_es&diff=156132Python es2010-02-02T07:36:04Z<p>Mauricio: </p>
<hr />
<div>{{Extensions}}<br />
[[image:Py-uno_128.png|PyUNO Logo]] [[image:Pyuno_logo_a.jpg]] <br />
=== Empezando con PyUNO ===<br />
* Que es PyUno ?<br />
* Que necesito saber? <br />
* Donde empiezo ?<br />
** Desde Linux<br />
** Desde Windows<br />
* Donde guardo mis macros ? <br />
* Mi primer macro ?<br />
<br />
<br />
Efforts on moving PyUNO to '''Python 2.5''' continue. Liyuan is pushing this initiative and has [http://udk.openoffice.org/servlets/ReadMsg?listName=dev&msgNo=3704 commited the CWS] on the UDK mailing list. The [[CWS]], however, is not ready, and was sent back on issue [http://www.openoffice.org/issues/show_bug.cgi?id=71327 71327].<br />
<br />
=== Python and OpenOffice.org ===<br />
OpenOffice.org ships with the python scripting language, version 2.3.4. This Python distribution comes with the [[Uno]] module, which connects the [[API|UNO API]] to the python scripting language. To run this version of Python on Linux, you can go directly to the OpenOffice.org PATH. And as one would expect with any distribution of Python, OOo-Python can be run from the command line as well.<br />
<br />
==== Where is the IDE ? ====<br />
OpenOffice.org's IDE doesn't support Python, so development has to be done from another editor that does. Any volunteer for a binding is welcomed.<br />
<br />
==== Tips & Tricks ====<br />
<br />
Here is some useful information about using python in OOo.<br />
<br />
===== Debug output =====<br />
<br />
If you launch a python script, any error will silently break the execution, making your extension hard to debug. To change this behaviour, one can change the<br />
'''LogLevel'''<br />
.<br />
<br />
Have a look in <br />
''/path/to/ooo/program/'''pythonscript.py''''' <br />
and replace <br />
''LogLevel.use = LogLevel.'''NONE'''''<br />
with<br />
''LogLevel.use = LogLevel.'''DEBUG'''''<br />
.<br />
<br />
There are also currently-undocumented environment variables that tell the pyUno bridge to log every call. Set the environment variable<br />
''export PYUNO_LOGLEVEL=ARGS''<br />
. The output may be a little hard to read, but helpful nonetheless.<br />
<br />
Note that his applies only to Linux. For Windows, you need some more switches, and the output gets written to files (there is no stdout on windows :-( ).<br />
<br />
There are still some error messages that won't appear in these logs; this will improve in the near future (cws pyunofixes4). Once the cws is integrated, I will document these switches on the official pyuno site. <br />
<br />
''Thanks to Joerg Budischewski''<br />
.<br />
<br />
=== Python specific information for Extension creation ===<br />
To create extensions for python, it is important that you have enough familiarity with the UNO components, as well as with packaging your code for easy distribution through the ''OpenOffice.org package manager''. Please check the tutorials to learn how to component-ize your code, and how to deploy remote scripting through a service implementation.<br />
<br />
To learn to run Python on Windows, visit [[Using Python on Windows| this link]] for more detailed information.<br />
<br />
=== Getting Started ===<br />
*[[Using Python on Windows]] - New to Python? Learn how to use python on Windows<br />
*[[Using Python on Linux]] - A must read for an overview on Python and OOo relations<br />
* [[pyUNO bridge]] - Official page of the PyUNO bridge at the [http://udk.openoffice.org/ UDK site]<br />
* [[Python as a macro language]] in OpenOffice.org 2.x - How to use the Python scripting framework<br />
* [http://lucasmanual.com/mywiki/OpenOffice PyUNO Manual] Lukasz created a pyUNO manual. '''new'''<br />
* [http://www.linuxjournal.com/content/starting-stopping-and-connecting-openoffice-python Starting/Stopping and connecting using Python] From Linux Journal<br />
* Introduction on testing pyUNO programs with [[doctests]]<br />
* Create a [http://codesnippets.services.openoffice.org/Office/Office.MessageBoxWithTheUNOBasedToolkit.snip dialog box] in PyUNO.<br />
* [http://codesnippets.services.openoffice.org/Office/Office.ConnectViaPipe.snip Connect to openoffice.org] from PyUNO<br />
* [[PyUNO samples]] currently shipping with OpenOffice.org and the explanation.<br />
* Enhanced [http://www.oooforum.org/forum/viewtopic.phtml?p=257496#257496 Capitalized.py] script by ''The gray Cardinal'' at OOoforum.<br />
<br />
=== PyUNO Modules ===<br />
*[[Danny's Python Modules]] - Collection guide from DannyB's modules.<br />
*[[PrinttoWriter.py]] - This makes it easy and convenient to print a bunch of text into a Writer document.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=8456 Developing Calc Functions in Python] - Learn how Python can be used to script your spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=56037#56037 Generating a Spreadsheet through Python] - Automatically generate new spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=9115 Python container components]<br />
*[[PyUNOServer]] - The PyUNOServer is a script that works as an XML server for OpenOffice.org Calc<br />
*[[calcParser]] - calcParser is a small parser using the native SAX utilities within the OpenOffice.org python<br />
*[[OoConfig]] - OoConfig is a Python extension that seeks to provide a configuration editing facility similar to Mozilla's about:config<br />
*[[Bibliographic/Hints and Tips/OOoRISExport.py|OOoRISExport.py]] - Exports the bibliographic database in RIS format. Also [http://bibliographic.openoffice.org/files/documents/124/3078/RISImport.py RISImport.py]<br />
*[[Zotero_Plugin |Zotero Plugin]] - The Zotero plugin provides citation and bibliographic table insertion and editing functions for Writer documents.<br />
<br />
=== Hacking Around ===<br />
*[[UNO component packaging]] - How to create UNO components as well as the basics of script componentizing<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=38234#38234 Python component to parse XML] - Python is great to parse XML, PyUNO is also excellent when working with XML<br />
*[[Example of Service in Python]] - Learn how to run Python as a service, this is useful for remote scripting.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=76972#76972 Modify spreadsheet] - Example of storing and retrieving a custom attribute on a spreadsheet cell.<br />
*A simple [[daemon in Python]] - Learn how to run Python as a daemon<br />
*[[Loook.py]] - a simple Python tool that searches for text strings in OpenOffice.org.<br />
*[[odt2txt.py]] - convert ODF to plain text using python (and convert the txt to html).<br />
<br />
=== Python rules OOo (by B. Bois) ===<br />
[[image:python_power_for_OOo.png|Python rules OOo :-)]]<br />
<br />
<br />
<br />
[[Category:Extensions]]<br />
[[Category:Python]]<br />
[[Category:Uno]]</div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=Python_es&diff=156131Python es2010-02-02T07:34:38Z<p>Mauricio: </p>
<hr />
<div>{{Extensions}}<br />
[[image:Py-uno_128.png|PyUNO Logo]] [[image:Pyuno_logo_a.jpg]] <br />
=== Empezando con PyUNO ===<br />
* Que es PyUno?<br />
* Que necesito saber? <br />
* Donde empiezo ?<br />
** Desde Linux<br />
** Desde Windows<br />
* Donde guardo mis macros ? <br />
<br />
Efforts on moving PyUNO to '''Python 2.5''' continue. Liyuan is pushing this initiative and has [http://udk.openoffice.org/servlets/ReadMsg?listName=dev&msgNo=3704 commited the CWS] on the UDK mailing list. The [[CWS]], however, is not ready, and was sent back on issue [http://www.openoffice.org/issues/show_bug.cgi?id=71327 71327].<br />
<br />
=== Python and OpenOffice.org ===<br />
OpenOffice.org ships with the python scripting language, version 2.3.4. This Python distribution comes with the [[Uno]] module, which connects the [[API|UNO API]] to the python scripting language. To run this version of Python on Linux, you can go directly to the OpenOffice.org PATH. And as one would expect with any distribution of Python, OOo-Python can be run from the command line as well.<br />
<br />
==== Where is the IDE ? ====<br />
OpenOffice.org's IDE doesn't support Python, so development has to be done from another editor that does. Any volunteer for a binding is welcomed.<br />
<br />
==== Tips & Tricks ====<br />
<br />
Here is some useful information about using python in OOo.<br />
<br />
===== Debug output =====<br />
<br />
If you launch a python script, any error will silently break the execution, making your extension hard to debug. To change this behaviour, one can change the<br />
'''LogLevel'''<br />
.<br />
<br />
Have a look in <br />
''/path/to/ooo/program/'''pythonscript.py''''' <br />
and replace <br />
''LogLevel.use = LogLevel.'''NONE'''''<br />
with<br />
''LogLevel.use = LogLevel.'''DEBUG'''''<br />
.<br />
<br />
There are also currently-undocumented environment variables that tell the pyUno bridge to log every call. Set the environment variable<br />
''export PYUNO_LOGLEVEL=ARGS''<br />
. The output may be a little hard to read, but helpful nonetheless.<br />
<br />
Note that his applies only to Linux. For Windows, you need some more switches, and the output gets written to files (there is no stdout on windows :-( ).<br />
<br />
There are still some error messages that won't appear in these logs; this will improve in the near future (cws pyunofixes4). Once the cws is integrated, I will document these switches on the official pyuno site. <br />
<br />
''Thanks to Joerg Budischewski''<br />
.<br />
<br />
=== Python specific information for Extension creation ===<br />
To create extensions for python, it is important that you have enough familiarity with the UNO components, as well as with packaging your code for easy distribution through the ''OpenOffice.org package manager''. Please check the tutorials to learn how to component-ize your code, and how to deploy remote scripting through a service implementation.<br />
<br />
To learn to run Python on Windows, visit [[Using Python on Windows| this link]] for more detailed information.<br />
<br />
=== Getting Started ===<br />
*[[Using Python on Windows]] - New to Python? Learn how to use python on Windows<br />
*[[Using Python on Linux]] - A must read for an overview on Python and OOo relations<br />
* [[pyUNO bridge]] - Official page of the PyUNO bridge at the [http://udk.openoffice.org/ UDK site]<br />
* [[Python as a macro language]] in OpenOffice.org 2.x - How to use the Python scripting framework<br />
* [http://lucasmanual.com/mywiki/OpenOffice PyUNO Manual] Lukasz created a pyUNO manual. '''new'''<br />
* [http://www.linuxjournal.com/content/starting-stopping-and-connecting-openoffice-python Starting/Stopping and connecting using Python] From Linux Journal<br />
* Introduction on testing pyUNO programs with [[doctests]]<br />
* Create a [http://codesnippets.services.openoffice.org/Office/Office.MessageBoxWithTheUNOBasedToolkit.snip dialog box] in PyUNO.<br />
* [http://codesnippets.services.openoffice.org/Office/Office.ConnectViaPipe.snip Connect to openoffice.org] from PyUNO<br />
* [[PyUNO samples]] currently shipping with OpenOffice.org and the explanation.<br />
* Enhanced [http://www.oooforum.org/forum/viewtopic.phtml?p=257496#257496 Capitalized.py] script by ''The gray Cardinal'' at OOoforum.<br />
<br />
=== PyUNO Modules ===<br />
*[[Danny's Python Modules]] - Collection guide from DannyB's modules.<br />
*[[PrinttoWriter.py]] - This makes it easy and convenient to print a bunch of text into a Writer document.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=8456 Developing Calc Functions in Python] - Learn how Python can be used to script your spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=56037#56037 Generating a Spreadsheet through Python] - Automatically generate new spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=9115 Python container components]<br />
*[[PyUNOServer]] - The PyUNOServer is a script that works as an XML server for OpenOffice.org Calc<br />
*[[calcParser]] - calcParser is a small parser using the native SAX utilities within the OpenOffice.org python<br />
*[[OoConfig]] - OoConfig is a Python extension that seeks to provide a configuration editing facility similar to Mozilla's about:config<br />
*[[Bibliographic/Hints and Tips/OOoRISExport.py|OOoRISExport.py]] - Exports the bibliographic database in RIS format. Also [http://bibliographic.openoffice.org/files/documents/124/3078/RISImport.py RISImport.py]<br />
*[[Zotero_Plugin |Zotero Plugin]] - The Zotero plugin provides citation and bibliographic table insertion and editing functions for Writer documents.<br />
<br />
=== Hacking Around ===<br />
*[[UNO component packaging]] - How to create UNO components as well as the basics of script componentizing<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=38234#38234 Python component to parse XML] - Python is great to parse XML, PyUNO is also excellent when working with XML<br />
*[[Example of Service in Python]] - Learn how to run Python as a service, this is useful for remote scripting.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=76972#76972 Modify spreadsheet] - Example of storing and retrieving a custom attribute on a spreadsheet cell.<br />
*A simple [[daemon in Python]] - Learn how to run Python as a daemon<br />
*[[Loook.py]] - a simple Python tool that searches for text strings in OpenOffice.org.<br />
*[[odt2txt.py]] - convert ODF to plain text using python (and convert the txt to html).<br />
<br />
=== Python rules OOo (by B. Bois) ===<br />
[[image:python_power_for_OOo.png|Python rules OOo :-)]]<br />
<br />
<br />
<br />
[[Category:Extensions]]<br />
[[Category:Python]]<br />
[[Category:Uno]]</div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=Python_es&diff=156122Python es2010-02-02T07:23:06Z<p>Mauricio: </p>
<hr />
<div>{{Extensions}}<br />
[[image:Py-uno_128.png|PyUNO Logo]] [[image:Pyuno_logo_a.jpg]] <br />
=== Empezando con PyUNO ===<br />
Efforts on moving PyUNO to '''Python 2.5''' continue. Liyuan is pushing this initiative and has [http://udk.openoffice.org/servlets/ReadMsg?listName=dev&msgNo=3704 commited the CWS] on the UDK mailing list. The [[CWS]], however, is not ready, and was sent back on issue [http://www.openoffice.org/issues/show_bug.cgi?id=71327 71327].<br />
<br />
=== Python and OpenOffice.org ===<br />
OpenOffice.org ships with the python scripting language, version 2.3.4. This Python distribution comes with the [[Uno]] module, which connects the [[API|UNO API]] to the python scripting language. To run this version of Python on Linux, you can go directly to the OpenOffice.org PATH. And as one would expect with any distribution of Python, OOo-Python can be run from the command line as well.<br />
<br />
==== Where is the IDE ? ====<br />
OpenOffice.org's IDE doesn't support Python, so development has to be done from another editor that does. Any volunteer for a binding is welcomed.<br />
<br />
==== Tips & Tricks ====<br />
<br />
Here is some useful information about using python in OOo.<br />
<br />
===== Debug output =====<br />
<br />
If you launch a python script, any error will silently break the execution, making your extension hard to debug. To change this behaviour, one can change the<br />
'''LogLevel'''<br />
.<br />
<br />
Have a look in <br />
''/path/to/ooo/program/'''pythonscript.py''''' <br />
and replace <br />
''LogLevel.use = LogLevel.'''NONE'''''<br />
with<br />
''LogLevel.use = LogLevel.'''DEBUG'''''<br />
.<br />
<br />
There are also currently-undocumented environment variables that tell the pyUno bridge to log every call. Set the environment variable<br />
''export PYUNO_LOGLEVEL=ARGS''<br />
. The output may be a little hard to read, but helpful nonetheless.<br />
<br />
Note that his applies only to Linux. For Windows, you need some more switches, and the output gets written to files (there is no stdout on windows :-( ).<br />
<br />
There are still some error messages that won't appear in these logs; this will improve in the near future (cws pyunofixes4). Once the cws is integrated, I will document these switches on the official pyuno site. <br />
<br />
''Thanks to Joerg Budischewski''<br />
.<br />
<br />
=== Python specific information for Extension creation ===<br />
To create extensions for python, it is important that you have enough familiarity with the UNO components, as well as with packaging your code for easy distribution through the ''OpenOffice.org package manager''. Please check the tutorials to learn how to component-ize your code, and how to deploy remote scripting through a service implementation.<br />
<br />
To learn to run Python on Windows, visit [[Using Python on Windows| this link]] for more detailed information.<br />
<br />
=== Getting Started ===<br />
*[[Using Python on Windows]] - New to Python? Learn how to use python on Windows<br />
*[[Using Python on Linux]] - A must read for an overview on Python and OOo relations<br />
* [[pyUNO bridge]] - Official page of the PyUNO bridge at the [http://udk.openoffice.org/ UDK site]<br />
* [[Python as a macro language]] in OpenOffice.org 2.x - How to use the Python scripting framework<br />
* [http://lucasmanual.com/mywiki/OpenOffice PyUNO Manual] Lukasz created a pyUNO manual. '''new'''<br />
* [http://www.linuxjournal.com/content/starting-stopping-and-connecting-openoffice-python Starting/Stopping and connecting using Python] From Linux Journal<br />
* Introduction on testing pyUNO programs with [[doctests]]<br />
* Create a [http://codesnippets.services.openoffice.org/Office/Office.MessageBoxWithTheUNOBasedToolkit.snip dialog box] in PyUNO.<br />
* [http://codesnippets.services.openoffice.org/Office/Office.ConnectViaPipe.snip Connect to openoffice.org] from PyUNO<br />
* [[PyUNO samples]] currently shipping with OpenOffice.org and the explanation.<br />
* Enhanced [http://www.oooforum.org/forum/viewtopic.phtml?p=257496#257496 Capitalized.py] script by ''The gray Cardinal'' at OOoforum.<br />
<br />
=== PyUNO Modules ===<br />
*[[Danny's Python Modules]] - Collection guide from DannyB's modules.<br />
*[[PrinttoWriter.py]] - This makes it easy and convenient to print a bunch of text into a Writer document.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=8456 Developing Calc Functions in Python] - Learn how Python can be used to script your spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=56037#56037 Generating a Spreadsheet through Python] - Automatically generate new spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=9115 Python container components]<br />
*[[PyUNOServer]] - The PyUNOServer is a script that works as an XML server for OpenOffice.org Calc<br />
*[[calcParser]] - calcParser is a small parser using the native SAX utilities within the OpenOffice.org python<br />
*[[OoConfig]] - OoConfig is a Python extension that seeks to provide a configuration editing facility similar to Mozilla's about:config<br />
*[[Bibliographic/Hints and Tips/OOoRISExport.py|OOoRISExport.py]] - Exports the bibliographic database in RIS format. Also [http://bibliographic.openoffice.org/files/documents/124/3078/RISImport.py RISImport.py]<br />
*[[Zotero_Plugin |Zotero Plugin]] - The Zotero plugin provides citation and bibliographic table insertion and editing functions for Writer documents.<br />
<br />
=== Hacking Around ===<br />
*[[UNO component packaging]] - How to create UNO components as well as the basics of script componentizing<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=38234#38234 Python component to parse XML] - Python is great to parse XML, PyUNO is also excellent when working with XML<br />
*[[Example of Service in Python]] - Learn how to run Python as a service, this is useful for remote scripting.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=76972#76972 Modify spreadsheet] - Example of storing and retrieving a custom attribute on a spreadsheet cell.<br />
*A simple [[daemon in Python]] - Learn how to run Python as a daemon<br />
*[[Loook.py]] - a simple Python tool that searches for text strings in OpenOffice.org.<br />
*[[odt2txt.py]] - convert ODF to plain text using python (and convert the txt to html).<br />
<br />
=== Python rules OOo (by B. Bois) ===<br />
[[image:python_power_for_OOo.png|Python rules OOo :-)]]<br />
<br />
<br />
<br />
[[Category:Extensions]]<br />
[[Category:Python]]<br />
[[Category:Uno]]</div>Mauriciohttps://wiki.openoffice.org/w/index.php?title=Python_es&diff=156118Python es2010-02-02T07:17:02Z<p>Mauricio: Created page with '{{Extensions}} PyUNO Logo image:Pyuno_logo_a.jpg === News === Efforts on moving PyUNO to '''Python 2.5''' continue. Liyuan is pushing this initiati…'</p>
<hr />
<div>{{Extensions}}<br />
[[image:Py-uno_128.png|PyUNO Logo]] [[image:Pyuno_logo_a.jpg]] <br />
=== News ===<br />
Efforts on moving PyUNO to '''Python 2.5''' continue. Liyuan is pushing this initiative and has [http://udk.openoffice.org/servlets/ReadMsg?listName=dev&msgNo=3704 commited the CWS] on the UDK mailing list. The [[CWS]], however, is not ready, and was sent back on issue [http://www.openoffice.org/issues/show_bug.cgi?id=71327 71327].<br />
<br />
=== Python and OpenOffice.org ===<br />
OpenOffice.org ships with the python scripting language, version 2.3.4. This Python distribution comes with the [[Uno]] module, which connects the [[API|UNO API]] to the python scripting language. To run this version of Python on Linux, you can go directly to the OpenOffice.org PATH. And as one would expect with any distribution of Python, OOo-Python can be run from the command line as well.<br />
<br />
==== Where is the IDE ? ====<br />
OpenOffice.org's IDE doesn't support Python, so development has to be done from another editor that does. Any volunteer for a binding is welcomed.<br />
<br />
==== Tips & Tricks ====<br />
<br />
Here is some useful information about using python in OOo.<br />
<br />
===== Debug output =====<br />
<br />
If you launch a python script, any error will silently break the execution, making your extension hard to debug. To change this behaviour, one can change the<br />
'''LogLevel'''<br />
.<br />
<br />
Have a look in <br />
''/path/to/ooo/program/'''pythonscript.py''''' <br />
and replace <br />
''LogLevel.use = LogLevel.'''NONE'''''<br />
with<br />
''LogLevel.use = LogLevel.'''DEBUG'''''<br />
.<br />
<br />
There are also currently-undocumented environment variables that tell the pyUno bridge to log every call. Set the environment variable<br />
''export PYUNO_LOGLEVEL=ARGS''<br />
. The output may be a little hard to read, but helpful nonetheless.<br />
<br />
Note that his applies only to Linux. For Windows, you need some more switches, and the output gets written to files (there is no stdout on windows :-( ).<br />
<br />
There are still some error messages that won't appear in these logs; this will improve in the near future (cws pyunofixes4). Once the cws is integrated, I will document these switches on the official pyuno site. <br />
<br />
''Thanks to Joerg Budischewski''<br />
.<br />
<br />
=== Python specific information for Extension creation ===<br />
To create extensions for python, it is important that you have enough familiarity with the UNO components, as well as with packaging your code for easy distribution through the ''OpenOffice.org package manager''. Please check the tutorials to learn how to component-ize your code, and how to deploy remote scripting through a service implementation.<br />
<br />
To learn to run Python on Windows, visit [[Using Python on Windows| this link]] for more detailed information.<br />
<br />
=== Getting Started ===<br />
*[[Using Python on Windows]] - New to Python? Learn how to use python on Windows<br />
*[[Using Python on Linux]] - A must read for an overview on Python and OOo relations<br />
* [[pyUNO bridge]] - Official page of the PyUNO bridge at the [http://udk.openoffice.org/ UDK site]<br />
* [[Python as a macro language]] in OpenOffice.org 2.x - How to use the Python scripting framework<br />
* [http://lucasmanual.com/mywiki/OpenOffice PyUNO Manual] Lukasz created a pyUNO manual. '''new'''<br />
* [http://www.linuxjournal.com/content/starting-stopping-and-connecting-openoffice-python Starting/Stopping and connecting using Python] From Linux Journal<br />
* Introduction on testing pyUNO programs with [[doctests]]<br />
* Create a [http://codesnippets.services.openoffice.org/Office/Office.MessageBoxWithTheUNOBasedToolkit.snip dialog box] in PyUNO.<br />
* [http://codesnippets.services.openoffice.org/Office/Office.ConnectViaPipe.snip Connect to openoffice.org] from PyUNO<br />
* [[PyUNO samples]] currently shipping with OpenOffice.org and the explanation.<br />
* Enhanced [http://www.oooforum.org/forum/viewtopic.phtml?p=257496#257496 Capitalized.py] script by ''The gray Cardinal'' at OOoforum.<br />
<br />
=== PyUNO Modules ===<br />
*[[Danny's Python Modules]] - Collection guide from DannyB's modules.<br />
*[[PrinttoWriter.py]] - This makes it easy and convenient to print a bunch of text into a Writer document.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=8456 Developing Calc Functions in Python] - Learn how Python can be used to script your spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=56037#56037 Generating a Spreadsheet through Python] - Automatically generate new spreadsheets<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?t=9115 Python container components]<br />
*[[PyUNOServer]] - The PyUNOServer is a script that works as an XML server for OpenOffice.org Calc<br />
*[[calcParser]] - calcParser is a small parser using the native SAX utilities within the OpenOffice.org python<br />
*[[OoConfig]] - OoConfig is a Python extension that seeks to provide a configuration editing facility similar to Mozilla's about:config<br />
*[[Bibliographic/Hints and Tips/OOoRISExport.py|OOoRISExport.py]] - Exports the bibliographic database in RIS format. Also [http://bibliographic.openoffice.org/files/documents/124/3078/RISImport.py RISImport.py]<br />
*[[Zotero_Plugin |Zotero Plugin]] - The Zotero plugin provides citation and bibliographic table insertion and editing functions for Writer documents.<br />
<br />
=== Hacking Around ===<br />
*[[UNO component packaging]] - How to create UNO components as well as the basics of script componentizing<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=38234#38234 Python component to parse XML] - Python is great to parse XML, PyUNO is also excellent when working with XML<br />
*[[Example of Service in Python]] - Learn how to run Python as a service, this is useful for remote scripting.<br />
*[http://www.oooforum.org/forum/viewtopic.phtml?p=76972#76972 Modify spreadsheet] - Example of storing and retrieving a custom attribute on a spreadsheet cell.<br />
*A simple [[daemon in Python]] - Learn how to run Python as a daemon<br />
*[[Loook.py]] - a simple Python tool that searches for text strings in OpenOffice.org.<br />
*[[odt2txt.py]] - convert ODF to plain text using python (and convert the txt to html).<br />
<br />
=== Python rules OOo (by B. Bois) ===<br />
[[image:python_power_for_OOo.png|Python rules OOo :-)]]<br />
<br />
<br />
<br />
[[Category:Extensions]]<br />
[[Category:Python]]<br />
[[Category:Uno]]</div>Mauricio