Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


Hi :)  

If the documentation is available but needs pulling together and de-geekifying then the Docs Team 
are a good place to do that.  If it needs writing from scratch (scuse the pun) then some devs 
probably need to be involved too.  


Writing code and writing documentation for technical readers is a radically different skill-set 
from writing so that the rest of us can understand it.  

Regards from
Tom :)  





________________________________
From: Joel Madero <jmadero.dev@gmail.com>
To: awilliam@whitemice.org 
Cc: users@global.libreoffice.org 
Sent: Sunday, 24 February 2013, 19:56
Subject: Re: [libreoffice-users] Re: Looking for PyUno Contributor(s)

On 02/24/2013 11:32 AM, Adam Tauno Williams wrote:
On Sun, 2013-02-24 at 16:56 +0100, Wolfgang Keller wrote:
If I'm incorrect, please let me know what is correct - but I'm pretty
sure that someone with some PyUno skills will be needed.
I would guess that those are rare, since PyUNO is at about the best
kept secret of LO(/OO).
+1 +1 +1

I've even attempted to make several runs at it.  The documentations is a
*@(^&@*$^&@*# crime.   There are silly trivial "Hello World" examples,
and there is the dump of the API.  And nothing in between.

If someone implements this as a contribution to the project *PLEASE
PLEASE PLEASE* do a step-by-step BLOG article/series of it.  I'll send
them a six-pack;  just let me know the URL.

There really seems to be an *AMAZING* amount of power just sitting there
to be used - but it is completely obscured to anyone not aleady familiar
with UNO's syntax and vocabulary.

Especially with the introduction of CMIS support it really seems a great
time to facilitate real automation via LibreOffice.

This seems to be a general consensus and it sucks for my purposes at 
least :-/

Another option is just going straight python and at least compiling the 
necessary numbers, then manually doing the charts and what not.

Anyone able to do this?

Maybe we need to get doc team involved at some point with PyUno to see 
if they can start getting decent documentation together.


Best,
Joel

-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted




-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.