That is exactly why i wondered if Andreas' points could be worked on while leaving the existing package, Base, as it stands.
That way the database functionality could be moved forwards while leaving the kludgy mess (ok, it
might not be a kludge from a coders pov) to get sorted 'later'.
The trees outside my window have been severely pruned back but i know that by the summer the leaves will be out in full force. The trees look a lot healthier already as they are not groaning under their own weight.
--- On Wed, 18/4/12, Alexander Thurgood<firstname.lastname@example.org> wrote:
From: Alexander Thurgood<email@example.com>
Subject: [libreoffice-users] Re: Problems importing an OO database into LO
Date: Wednesday, 18 April, 2012, 10:05
Le 17/04/12 18:14, Andreas Säger a écrit :
The easiest improvements in my honest opinion:
- Wipe out the .odb container all together and get back to the
configuration of database access in OOo 1. Back to external databases
with configuration data in configuration files, forms and reports in
stand-alone office documents. More speed more safety, security,
accessibility and transparency. People who do not understand how to
connect separated software tools do not understand the .odb container
neither (as we can read in all the mail merge topics).
- Remove all the half done wizards. Do not improve them. Remove! No
database developer nor interface designer needs all this stinky rubbish.
There are graphical tools to compose forms and reports within office
documents. There is SQL for all the rest, including all the things we
can not do in the current graphical interface. There are plenty of SQL
editors to produce valid SQL for various databases. SQL text can be
pasted into any database configuration.
- Add native database queries, so the current "direct SQL mode" returns
editable row sets and the (useless or even harmful) graphical query
designer can be removed as well.
- Having removed all the wizards (they are Java components) without
losing any functionality at all, extensions could substitute .odb
packages. When you open the extension, the database gets installed
_permanently_ (rather than _temporarily_ like the .odb) into the
configuration tree together with the forms and reports documents. The
database will be registered and all the tables, queries, forms and
reports are accessible form the data source window, hyperlinks and
desktop links just like it used to be in OOo 1.
Ah, nostalgia those were halcyon days ;-)
+1 (not that that means anything in our "user land".
Unfortunately, as I was told quite a while ago either on the dev-list or
IRC dev channel, or bugzilla, "no-one wants to go back to 10 year old
technology", i.e. the LO devs are not interested in undoing what Sun it
its infinite wisdom thought would be a good idea when it "re-invented
OOo-Base", so we are stuck with what we have until someone steps up and
decides to either unravel it all or improve it - a mammoth task by
Impressum (Legal Info)
: 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