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

Hi :)
The divergence has resulted in at least a doubling of the numbers of people working on the 
project(s).  The projects do have a lot of overlap and share a lot.  People that were colleagues 
working alongside each other may find themselves split into different projects but still chatting 
and helping each other.  

Taking just LibreOffice alone, it has famously already had a vast amount of devs join in.  The 
"Easy hacks" initiative has made it far easier to get devs that are familiar with other projects 
familiarised with programming for LibreOffice.  It's helped draw in students and other people that 
have never really done any programming before or left programming years ago and "Google's Summer of 
Code" has helped draw people into programming for LO too.  

Under Sun the infrastructure had all grown quite tangled so it was good to get a fresh start under 
TDF  maximising the usefulness of  modern technology that simply wasn't around when Sun's 
infrastructure was originally planned.  

The Apache Foundation is quite large and IBM can support their developments but would fidn it 
difficult to support a truly and fully OpenSource project such as LibreOffice.  Apparently Apache 
Licensing allows a mix of some fairly proprietary chunks of code alongside OpenSource ones.  

If OOo had just carried on under Sun then it wouldn't have had the resources of either Apache nor 
TDF let alone both!!  

Plus about half the community would have been unhappy about not being fully OpenSource and 
therefore never gaining the backing of the "Free Software Foundation" which has led to a greater 
range of distros being comfortable using LO.  The other half might have wanted to pull us more in 
the direction of corporate secrecy such as IBM seem to want.  This way both sides are happier and 
growing faster.  

Regards from
Tom :)

--- On Wed, 18/4/12, Alexander Thurgood <> wrote:

From: Alexander Thurgood <>
Subject: [libreoffice-users] Re: Problems importing an OO database into LO
Date: Wednesday, 18 April, 2012, 10:17

Le 17/04/12 11:28, Ian Whitfield a écrit :

Hi Ian,

While I might agree with your statements with regard to the integrated
use of HSQLDB, I would differ with regard to hooking up Base to various
server backends, which in my experience do work rather well on the
whole, albeit with tweaking, and are multi-OS compatible.

LONG story short........ I have now moved my (re-built) Database on to
Kexi - and what a difference!!!! It's like getting out of an old
broken-down VW (or other make) of car and getting into a brand new
Jaguar and driving down the highway at 100mph!! And I know what that
feels like as I did just that last year in the UK!! Yes there is a lot
to learn and work out but the overall effect is like Chalk and Cheese!!

For anyone interested I can recommend this DB - some of the more fancy
options are only due out in future releases but for a basic DB job it
"just works"!!

Is it multi-OS ? Can you create a db/form/query in Kexi and give it to a
Windows, Mac or Solaris user  and then have that work ? If not, then it
is no better than Access, or Lotus Approach.


For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.