python scripting dialog.

Hi is there a reason why the Python dialog of OOo doesn't
let you create a  
new library while the Javascript and Beanshell does. I read
the UDK Python  
framework (http://udk.openoffice.org/python/scriptingframewor
k/index.html)  
arond the Script coding, however the instructions seem a bit
confusing.

If I want to get a macro within the document area and then
editing with  
the Python syntaxis, how does the software recognized is a
python module.  
So i went to the 'Run macro' dialog generate an empty file
but I couldnt  
get how to get actual content in the files.

I did an ediditn gon what it seemed like a defualt basic
file, and put the  
code from a module however the definitions were not showed
on their macro  
selection dialog.

-- 
Alexandro Colorado
Grupo de Usuarios Linux Tabasco
http://www.gultab.org

OpenOffice.org
Community Contact // Mexico
http://www.openoffice.org

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeudk.openoffice.org
For additional commands, e-mail: dev-helpudk.openoffice.org

On Thu, 28 Dec 2006 12:44:45 -0600, Alexandro Colorado  
<jzaopenoffice.org> wrote:

> Hi is there a reason why the Python dialog of OOo
doesn't let you create  
> a new library while the Javascript and Beanshell does.
I read the UDK  
> Python framework  
> (http://udk.openoffice.org/python/scriptingframewor
k/index.html) arond  
> the Script coding, however the instructions seem a bit
confusing.
>
> If I want to get a macro within the document area and
then editing with  
> the Python syntaxis, how does the software recognized
is a python  
> module. So i went to the 'Run macro' dialog generate an
empty file but I  
> couldnt get how to get actual content in the files.
>
> I did an ediditn gon what it seemed like a defualt
basic file, and put  
> the code from a module however the definitions were not
showed on their  
> macro selection dialog.
>

Thanks to santiago I could understand the documentation a
bit better.  
however I have tried to test a 'document-based' python
script and end up  
wiht a corrupted document which OOo could ignore.

The process is to unzip/zip the odt inserting and declaring
the  
Script/python/<script.py>

And delcaring it under the manifest xml with the following
lines:

  <manifest:file-entry manifest:media-type=""  
manifest:full-path="Scripts/python/PrintToWriter.py&quo
t;/>
  <manifest:file-entry
manifest:media-type="application/binary"  
manifest:full-path="Scripts/python/"/>
  <manifest:file-entry
manifest:media-type="application/binary"  
manifest:full-path="Scripts/"/>

My questions is of course, did I missed anything here?
Should I have just  
used lowercase? is the XML malformed? Any comments?

-- 
Alexandro Colorado
Grupo de Usuarios Linux Tabasco
http://www.gultab.org

OpenOffice.org
Community Contact // Mexico
http://www.openoffice.org

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeudk.openoffice.org
For additional commands, e-mail: dev-helpudk.openoffice.org