Re: [Libreoffice] [GSOC] how to call python code from the menu

Caolán McNamara <caolanm -AT- redhat.com>
Wed, 07 Sep 2011 11:24:01 +0100

On Tue, 2011-09-06 at 19:49 +0200, Xisco Faulí wrote:

Hello,


I've tried to follow your steps but placing the code in
wizards/com/sun/star/wizards/fax/CallWizard.py. So far I haven't been
able to build it successfully. It complains and says: ERROR: File not
found: CallWizard.py


I see that wizards has been converted to gmake in the meantime, so it no
longer uses dmake makefile.mk stuff, we need some gbuild support for
copying .py files into their final locations with some form of
pyuno .component file support support.

C.

Context

[Libreoffice] [GSOC] how to call python code from the menu · Xisco Faulí
- Re: [Libreoffice] [GSOC] how to call python code from the menu · Caolán McNamara
  - Re: [Libreoffice] [GSOC] how to call python code from the menu · Xisco Faulí
    - Re: [Libreoffice] [GSOC] how to call python code from the menu · Caolán McNamara
      - Re: [Libreoffice] [GSOC] how to call python code from the menu · Caolán McNamara
        
        Re: [Libreoffice] [GSOC] how to call python code from the menu · Xisco Faulí
        
        Re: [Libreoffice] [GSOC] how to call python code from the menu · Caolán McNamara
        
        Re: [Libreoffice] [GSOC] how to call python code from the menu · Caolán McNamara
        Re: [Libreoffice] [GSOC] how to call python code from the menu · Xisco Faulí

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.