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


Hi :)
The issue about what to use instead of Java is something that would be good to discuss on the devs 
list and perhaps with other people that might have a better idea.  Mostly it seems that java really 
wasn't needed and can be just written out comlpetely.  At a guess that's not always going to work 
in Base.  I was wondering if Gtk or Python or Ruby or C++ but i'm probably showing just how little 
i know about this type of thing just by saying that.  Devs will have a far better idea of what is 
viable.  
Regards from
Tom :)


--- On Wed, 14/9/11, Robert Ryley <rryley1976@gmail.com> wrote:

From: Robert Ryley <rryley1976@gmail.com>
Subject: Re: [libreoffice-marketing] Recruitment for Base (Was Re: [steering-discuss] Base - a new 
mailing list?)
To: marketing@global.libreoffice.org
Date: Wednesday, 14 September, 2011, 21:40

Hello David,

Thanks for the info.  I'm willing to do a few jobs, but I'm trying to
wrap my head around the different aspects of the project.  I am
considering pitching the use of a customized version Libre Office, and
hopefully they might be interested in funding some development.  But
that is all very preliminary.

If there is a move away from java, that is going to make a significant
portion of that documentation obsolete.  Is there anything
specifically related to the move away from java documented anywhere?
Any idea what the API is going to be to replace it?

Robert


On Wed, Sep 14, 2011 at 4:34 PM, David Nelson <lists@traduction.biz> wrote:
Hi Robert,

On Wed, Sep 14, 2011 at 11:19 PM, Robert Ryley <rryley1976@gmail.com>
Where can I find more info about this?

Actually, Tom's been doing some very nice organizational work on the
docs team's wiki:

On Wed, Sep 14, 2011 at 11:08 PM, Tom Davies <tomdavies04@yahoo.co.uk> wrote:

There is a guide for general programmers
http://wiki.documentfoundation.org/Documentation#Other_Documentation_and_Resources
but it probably completely misses some of the key curved balls that Base devs will have to dodge 
or use.  Oh, and it was written for OOo

And you can also browse the current content on
http://media.libreoffice.org (click the CMIS Repository link).

You could also write to the docs team mailing list if you'd like to join us! :-)

http://www.libreoffice.org/get-involved/documenters/

--
David Nelson

--
Unsubscribe instructions: E-mail to marketing+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/marketing/
All messages sent to this list will be publicly archived and cannot be deleted



-- 
Unsubscribe instructions: E-mail to marketing+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/marketing/
All messages sent to this list will be publicly archived and cannot be deleted


-- 
Unsubscribe instructions: E-mail to marketing+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/marketing/
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.