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


Bonjour

Pour info et si vous avez un avis éclairé n'hésitez pas :)

À bientôt
Sophie
-------- Original Message --------
Subject: Pivot Table data provider extension framework (removal possibility)
Date: Tue, 12 Mar 2013 11:41:32 -0400
From: Kohei Yoshida <kohei.yoshida@gmail.com>
To: libreoffice-dev <libreoffice@lists.freedesktop.org>,  ux-advise
<libreoffice-ux-advise@lists.freedesktop.org>

Hi there,

I'd like to ask whether someone actually uses this Pivot Table data
provider extension framework, because I'd like to remove this if nobody
is using it, or only few people are using it.

Currently, Calc's pivot table supports 4 different backends.  They are:

1. cell range on sheet
2. named range on sheet
3. database (registered via database manager)
4. extension acting as a data provider.

The 4th one is what I'd like to get rid of.  When creating a pivot table
via Data > Pivot Table > Create..., you'll get a dialog with these 4
choices.  The 4th one, labeled "External source/interface" is usually
disabled *unless* you have extension installed that implements all pivot
table interfaces necessary to act as a data provider.  These are UNO
interfaces that are recently *un*-published in the 4.0 release.

On this page:

https://wiki.documentfoundation.org/ReleaseNotes/4.0

All UNO services/interfaces/etc starting with

com.sun.star.sheet.DataPilotSource

and below are the ones that are relevant for this data provider
functionality.

I believe the same functionality can be achieve via database
connectivity, by having such external data provider register as a
database, and use it to act as a data provider for pivot tables.  So, I
don't see a reason why we need to keep this as a separate data source
category.

The way it is currently implemented also makes it *extremely* difficult
for us to optimize the pivot table engine, because all its functionality
has to go through the UNO API which forces us to do data conversion
*twice* for every single transaction.  That's very very expensive
especially as the data size grows (and it always does).

So, I'd *love* to get rid of this sooner rather than later, and I'd like
to know whether there are people who would absolutely need this
functionality, and if so why.  As I said above, I believe the same
functionality could be achieved via the database connectivity backend
even if we remove the extension backend.

Thanks,

-- 
Kohei Yoshida, LibreOffice hacker, Calc
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice



-- 
Envoyez un mail à qa+help@fr.libreoffice.org pour savoir comment vous désinscrire
Les archives de la liste sont disponibles à http://listarchives.libreoffice.org/fr/qa/
Tous les messages envoyés sur cette liste seront archivés publiquement et ne pourront pas être 
supprimés

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.