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


On 02/13/2013 09:01 PM, Michael Meeks wrote:
Hi Stephen,

On Wed, 2013-02-13 at 07:59 +1100, Stephen Morris wrote:
        Out of interest do you have a bug or two you want to hack on there ?
the Pivot table code is in:
        sc/source/ui/dbgui/dpgroupdlg.cxx

One of the issues I have with pivot tables in calc is that calc won't
allow input variables to be renamed at pivot table creation time, it
only allows renaming variables after table creation by editing the data
in the header cells. Calc also doesn't allow renaming of variables in
the page section of the pivot table. Calc doesn't allow the
specification of formats for the variables being added at creation time,
or at a later date via the menus as excel does, Calc only provides the
ability to do it after creation of the table by applying formats to the
cells in the table, hence if cells are re-arranged the formatting gets
out of whack, and if the source data changes such that more rows are
added on refresh, the additional rows won't have the format applied.
        Oh - interesting. So the formats thing sounds like a useful core
feature you'd want to add to the pivot rendering; and the other bits are
UI features. Certainly you'd be most welcome to work on this - Kohei is
prolly the best contact here.

        The first thing to do is to get a build:

        http://www.libreoffice.org/developers-2/

        When you have a working build of master, then we can get going with
some more code reading & pointers,

        How does that sound ? in general it's great to include the developers
list too (no subscription required) just CC libreoffice-dev
<libreoffice@lists.freedesktop.org>

        All the best,

                Michael.

Hi,
I am having all sorts of problems with the source code in Eclipse. I have created a new blank C++ project in Eclipse and imported the entire sc directory into that project. Subsequently I have opened dpgroupdlg.cxx in the editor (I'm also not sure why Eclipse displays all directories duplicated) and Eclipse is displaying errors on just about every statement in that file. I think the first thing I need to do is to find all the include files and add those directories into the include file path in the project properties. One of the problems I have is that the statement "com::sun::star::sheet::DataPilotFieldGroupBy::SECONDS," is producing an error complaining that symbol SECONDS is not found. In the include list there is an include of "<com/sun/star/sheet/DataPilotFieldGroupBy.hpp>" and I have found a directory of that name in the offapi subdirectory of libreoffice, but that path does not contain DataPilotFieldGroupBy.hpp it contains instead DataPilotFiedlGroupBy.idl which contains a definition of SECONDS and the other time symbols specific in the code. How I configure eclipse to consider the idl file to be the same as the hpp file so that these symbols get resolved? I am also having difficulty determining which dp module equates to the dialog that gets displayed for variables that are dragged to the pivot table layout areas, to specify the attributes of those variables. Is there any documentation anywhere that explains what each module within the suite actually does and how they relate to what is actually displayed by Libreoffice for each function it performs?

regards,
Steve


begin:vcard
fn:Stephen Morris
n:Morris;Stephen
email;internet:samorris@netspace.net.au
x-mozilla-html:TRUE
version:2.1
end:vcard


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.