about DataPilot

[Kohei Yoshida-2]

On Wed, 2009-06-10 at 14:51 +0000, Michael Meeks wrote:
> I've asked Kohei to create a CWS and whack the
> patches in there

Ok.  All my changes related to DataPilot are now in koheidatapilot03
cws.  I'm also working on specs on the wiki.  They are at:

http://wiki.services.openoffice.org/wiki/Calc/Features/DataPilot_enhanced_field_popup_window
http://wiki.services.openoffice.org/wiki/Calc/Features/DataPilot_custom_display_names

The first spec is pretty much complete, while the second one is still
being worked on.

Also, FYI, I'll be on vacation for the entire next week.  So, whatever
change still needs to be done will be done after I get back.

Kohei

--
Kohei Yoshida - OpenOffice.org Engineer - Novell, Inc.
<kyoshida@...>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Zhi Yu Yue]

Struggled a little with the wiki editing, and here is the performance part. Thanks, Xu Ming!http://wiki.services.openoffice.org/wiki/Calc/Proposal_DataPilot_byIBM

Not completed, but should be OK to start some discussion. We will then turn to the UX spec.

Best Regards,
Helen Yue
_________________________________________________________
Yue Zhi Yu  |  Manager of User Experience & Applications, Lotus Symphony |  yuezhiyu@...

From:	Niklas Nebel <Niklas.Nebel@...>
To:	dev@...
Date:	06/19/2009 05:12 PM
Subject:	Re: [sc-dev] about DataPilot
Sent by:	Niklas.Nebel@...

---

On 06/19/09 10:58, Zhi Yu Yue wrote:
> It spent a little more time than I thought to organize it. Where should
> I post it? should I create a new wiki page? Thanks.

Yes, a wiki page would be good.

Niklas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Niklas Nebel]

On 06/23/09 17:24, Zhi Yu Yue wrote:
> Struggled a little with the wiki editing, and here is the performance
> part. Thanks, Xu
> Ming!http://wiki.services.openoffice.org/wiki/Calc/Proposal_DataPilot_byIBM

Great, thanks. Some comments:

- The data in the Quantify screenshot looks strange. For any larger
calculation, screen output (OutputDevice::DrawLine) shouldn't play a
significant role.

- "Data Source buffer" sounds interesting. Now it would of course be
helpful to see the actual code changes for it.

- The allocation for all members (B1,B2,B3) is what issue 55266 is
about. In the "Solution Description" section, there's only the heading.
Do you have a solution for that?

> Not completed, but should be OK to start some discussion. We will then
> turn to the UX spec.

For the UI features, note that Kohei's changes are now available, with a
description at
http://wiki.services.openoffice.org/wiki/Calc/Features/DataPilot_enhanced_field_popup_window 
and
http://wiki.services.openoffice.org/wiki/Calc/Features/DataPilot_custom_display_names.
You should take a look at that and see where your proposed changes are
different.

Niklas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Xu Ming Wang]

Hi all,

I am Wang Xu Ming, the dev lead of DataPilot of Lotus Symphony.
I did not write some details because it is too detail and do not know if it is proper.
Here answer Niklas's mail below in blue:

- The data in the Quantify screenshot looks strange. For any larger
calculation, screen output (OutputDevice::DrawLine) shouldn't play a
significant role.
   It maybe relate to Quantify environment - drawing is very slow.
   Actually, ScAttrArray::ApplyBlockFrame is a low performance function.
   If the output table about 10000 rows, ScDPOutput::Output() used 8-10 seconds in our test environment.
   Current solution, to data area in the table:
   Case 1:  all cells need set border, then setting block frame border only once is ok.    
   Case 2:  otherwise, set block frame border like this



- "Data Source buffer" sounds interesting. Now it would of course be
helpful to see the actual code changes for it.
   It is something like Excel's PivotCache, and better to save it in the document file.
   If that, we need the approval of the ODF format proposal relate it.
- The allocation for all members (B1,B2,B3) is what issue 55266 is
about. In the "Solution Description" section, there's only the heading.
Do you have a solution for that?
   I have a solution in LateInitFrom. To row data, only new ScDPResultMember when find it.

Sincerely,
Xu Ming Wang


Lotus Symphony
China Software Development Laboratory,Beijing
Phone: [phone]
E-mail : wangxum@...

Niklas Nebel ---2009-06-24 00:55:50---On 06/23/09 17:24, Zhi Yu Yue wrote:

Niklas Nebel <Niklas.Nebel@...>
Sent by: Niklas.Nebel@...

2009-06-24 00:51

Please respond to
dev@...

To	dev@...
cc
Subject	Re: [sc-dev] about DataPilot

On 06/23/09 17:24, Zhi Yu Yue wrote:
> Struggled a little with the wiki editing, and here is the performance
> part. Thanks, Xu
> Ming!http://wiki.services.openoffice.org/wiki/Calc/Proposal_DataPilot_byIBM

Great, thanks. Some comments:

- The data in the Quantify screenshot looks strange. For any larger
calculation, screen output (OutputDevice::DrawLine) shouldn't play a
significant role.

- "Data Source buffer" sounds interesting. Now it would of course be
helpful to see the actual code changes for it.

- The allocation for all members (B1,B2,B3) is what issue 55266 is
about. In the "Solution Description" section, there's only the heading.
Do you have a solution for that?

> Not completed, but should be OK to start some discussion. We will then
> turn to the UX spec.

For the UI features, note that Kohei's changes are now available, with a
description at
http://wiki.services.openoffice.org/wiki/Calc/Features/DataPilot_enhanced_field_popup_window 
and
http://wiki.services.openoffice.org/wiki/Calc/Features/DataPilot_custom_display_names.
You should take a look at that and see where your proposed changes are
different.

Niklas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Xu Ming Wang]

Sorry, the Notes' table was not converted well.
Put the table as a picture:


Sincerely,
Xu Ming Wang


Lotus Symphony
China Software Development Laboratory,Beijing
Phone: [phone]
E-mail : wangxum@...

Xu Ming Wang---2009-06-24 11:10:37---Hi all,

Xu Ming Wang/China/IBM@IBMCN

2009-06-24 11:00

Please respond to
dev@...

To	dev@...
cc	dev@..., Niklas.Nebel@...
Subject	Re: [sc-dev] about DataPilot

Hi all,

I am Wang Xu Ming, the dev lead of DataPilot of Lotus Symphony.
I did not write some details because it is too detail and do not know if it is proper.
Here answer Niklas's mail below in blue:

- The data in the Quantify screenshot looks strange. For any larger
calculation, screen output (OutputDevice::DrawLine) shouldn't play a
significant role.
  It maybe relate to Quantify environment - drawing is very slow.
  Actually, ScAttrArray::ApplyBlockFrame is a low performance function.
  If the output table about 10000 rows, ScDPOutput::Output() used 8-10 seconds in our test environment.
  Current solution, to data area in the table:
  Case 1:  all cells need set border, then setting block frame border only once is ok.    
  Case 2:  otherwise, set block frame border like this


- "Data Source buffer" sounds interesting. Now it would of course be
helpful to see the actual code changes for it.
  It is something like Excel's PivotCache, and better to save it in the document file.
  If that, we need the approval of the ODF format proposal relate it.
- The allocation for all members (B1,B2,B3) is what issue 55266 is
about. In the "Solution Description" section, there's only the heading.
Do you have a solution for that?
  I have a solution in LateInitFrom. To row data, only new ScDPResultMember when find it.

Sincerely,
Xu Ming Wang


Lotus Symphony
China Software Development Laboratory,Beijing
Phone: [phone]
E-mail : wangxum@...

Niklas Nebel ---2009-06-24 00:55:50---On 06/23/09 17:24, Zhi Yu Yue wrote:

Niklas Nebel <Niklas.Nebel@...>
Sent by: Niklas.Nebel@...

2009-06-24 00:51

Please respond to
dev@...

To	dev@...
cc
Subject	Re: [sc-dev] about DataPilot

On 06/23/09 17:24, Zhi Yu Yue wrote:
> Struggled a little with the wiki editing, and here is the performance
> part. Thanks, Xu
> Ming!http://wiki.services.openoffice.org/wiki/Calc/Proposal_DataPilot_byIBM

Great, thanks. Some comments:

- The data in the Quantify screenshot looks strange. For any larger
calculation, screen output (OutputDevice::DrawLine) shouldn't play a
significant role.

- "Data Source buffer" sounds interesting. Now it would of course be
helpful to see the actual code changes for it.

- The allocation for all members (B1,B2,B3) is what issue 55266 is
about. In the "Solution Description" section, there's only the heading.
Do you have a solution for that?

> Not completed, but should be OK to start some discussion. We will then
> turn to the UX spec.

For the UI features, note that Kohei's changes are now available, with a
description at
http://wiki.services.openoffice.org/wiki/Calc/Features/DataPilot_enhanced_field_popup_window 
and
http://wiki.services.openoffice.org/wiki/Calc/Features/DataPilot_custom_display_names.
You should take a look at that and see where your proposed changes are
different.

Niklas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Niklas Nebel]

On 06/24/09 05:00, Xu Ming Wang wrote:

> - The data in the Quantify screenshot looks strange. For any larger
> calculation, screen output (OutputDevice::DrawLine) shouldn't play a
> significant role.
>    It maybe relate to Quantify environment - drawing is very slow.
>    Actually, ScAttrArray::ApplyBlockFrame is a low performance function.
>    If the output table about 10000 rows, ScDPOutput::Output() used 8-10
> seconds in our test environment.
>    Current solution, to data area in the table:
>    Case 1:  all cells need set border, then setting block frame border
> only once is ok.    
>    Case 2:  otherwise, set block frame border like this

Applying the frames takes some time in a large output table, that's right.

> - "Data Source buffer" sounds interesting. Now it would of course be
> helpful to see the actual code changes for it.
>    It is something like Excel's PivotCache, and better to save it in the
> document file.
>    If that, we need the approval of the ODF format proposal relate it.

OOo 3.x has a cache (ScDPCacheTable), but it isn't saved, and the
results are still created using ScDPItemData. We'll have to see how we
can put these things together. Also, you're right, we'll have to clarify
the file format handling.

> - The allocation for all members (B1,B2,B3) is what issue 55266 is
> about. In the "Solution Description" section, there's only the heading.
> Do you have a solution for that?
>    I have a solution in LateInitFrom. To row data, only new
> ScDPResultMember when find it.

Excellent. I had something like that in mind for issue 55266, but never
found the time to actually try it.

All three changes you mention still seem to be valid and useful for 3.x.
How big are the individual changes, is it possible to extract them, so
we can try to update them to the 3.x code base?

Niklas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Xu Ming Wang]

We are migrating our work to 3.x code base now. If need, we can extract these parts. "Data buffer" may need some refactoring work with the class ScDPCacheTable.

Sincerely,
Xu Ming Wang


Lotus Symphony
China Software Development Laboratory,Beijing
Phone: [phone]
E-mail : wangxum@...

Niklas Nebel ---2009-06-25 00:16:56---On 06/24/09 05:00, Xu Ming Wang wrote:

Niklas Nebel <Niklas.Nebel@...>
Sent by: Niklas.Nebel@...

2009-06-25 00:16

Please respond to
dev@...

To	dev@...
cc
Subject	Re: [sc-dev] about DataPilot

On 06/24/09 05:00, Xu Ming Wang wrote:
> - The data in the Quantify screenshot looks strange. For any larger
> calculation, screen output (OutputDevice::DrawLine) shouldn't play a
> significant role.
>    It maybe relate to Quantify environment - drawing is very slow.
>    Actually, ScAttrArray::ApplyBlockFrame is a low performance function.
>    If the output table about 10000 rows, ScDPOutput::Output() used 8-10
> seconds in our test environment.
>    Current solution, to data area in the table:
>    Case 1:  all cells need set border, then setting block frame border
> only once is ok.    
>    Case 2:  otherwise, set block frame border like this

Applying the frames takes some time in a large output table, that's right.

> - "Data Source buffer" sounds interesting. Now it would of course be
> helpful to see the actual code changes for it.
>    It is something like Excel's PivotCache, and better to save it in the
> document file.
>    If that, we need the approval of the ODF format proposal relate it.

OOo 3.x has a cache (ScDPCacheTable), but it isn't saved, and the
results are still created using ScDPItemData. We'll have to see how we
can put these things together. Also, you're right, we'll have to clarify
the file format handling.

> - The allocation for all members (B1,B2,B3) is what issue 55266 is
> about. In the "Solution Description" section, there's only the heading.
> Do you have a solution for that?
>    I have a solution in LateInitFrom. To row data, only new
> ScDPResultMember when find it.

Excellent. I had something like that in mind for issue 55266, but never
found the time to actually try it.

All three changes you mention still seem to be valid and useful for 3.x.
How big are the individual changes, is it possible to extract them, so
we can try to update them to the 3.x code base?

Niklas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Niklas Nebel]

On 06/25/09 10:17, Xu Ming Wang wrote:
> We are migrating our work to 3.x code base now. If need, we can extract
> these parts. "Data buffer" may need some refactoring work with the class
> ScDPCacheTable.

Extracting smaller parts from your changes would make it much easier to
integrate the changes. Especially the performance improvements don't
need any User Experience discussion and could be integrated quickly.

Niklas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Zhi Yu Yue]

As I said previously in this mail list, we did some enhancements on DataPilot, and are willing to contribute the code. Here is one simple UX design written by my colleague, http://wiki.services.openoffice.org/wiki/User_Experience/Proposal_DataPilot_byIBM. Any comments are welcome!

Once you agree on the UX design, we will start the code contribution. Thanks!
 
Best Regards,
Helen Yue
_________________________________________________________
Yue Zhi Yu  |  Manager of User Experience & Applications, Lotus Symphony |  yuezhiyu@...

[Niklas Nebel]

On 06/20/09 02:38, Kohei Yoshida wrote:

> Ok.  All my changes related to DataPilot are now in koheidatapilot03
> cws.  I'm also working on specs on the wiki.  They are at:
>
> http://wiki.services.openoffice.org/wiki/Calc/Features/DataPilot_enhanced_field_popup_window
> http://wiki.services.openoffice.org/wiki/Calc/Features/DataPilot_custom_display_names
>
> The first spec is pretty much complete, while the second one is still
> being worked on.
>
> Also, FYI, I'll be on vacation for the entire next week.  So, whatever
> change still needs to be done will be done after I get back.

In addition to the visual comments on the ux-discuss list, some
technical remarks (I haven't looked through all of it yet, expect more
to come):

- Extensions to the DataPilotSource API must be done in a compatible way
(see the handling of the "Filter" property).

- We have to pay attention to keyboard accessibility (obvious key
choice: Ctrl-D, as for page fields).

- The popup window has to implement accessibility API. Generally the
easiest way for that is to use existing controls, like SvxCheckListBox
for the item selection. For the menu entries a new control would have to
be implemented, including the accessibility functions. Perhaps it's also
possible to extend the VCL popup menu with an extra window, but I can't
guarantee that's even possible without running into new problems.

Niklas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Kohei Yoshida-2]

On Fri, 2009-06-26 at 17:19 +0200, Niklas Nebel wrote:
> In addition to the visual comments on the ux-discuss list

Which I assume is this one:
http://ux.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=3658

I was not subscribed to that list, so I need to rely on the archive.
Let me leave the link here so that I can find it easily.

Kohei


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Niklas Nebel]

Kohei Yoshida wrote:
> On Fri, 2009-06-26 at 17:19 +0200, Niklas Nebel wrote:
>> In addition to the visual comments on the ux-discuss list
>
> Which I assume is this one:
> http://ux.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=3658

Yes, that's what I meant.

Niklas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Kohei Yoshida-2]

On Fri, 2009-06-26 at 17:19 +0200, Niklas Nebel wrote:

> On 06/20/09 02:38, Kohei Yoshida wrote:
> > Ok.  All my changes related to DataPilot are now in koheidatapilot03
> > cws.  I'm also working on specs on the wiki.  They are at:
> >
> > http://wiki.services.openoffice.org/wiki/Calc/Features/DataPilot_enhanced_field_popup_window
> > http://wiki.services.openoffice.org/wiki/Calc/Features/DataPilot_custom_display_names
> >
> > The first spec is pretty much complete, while the second one is still
> > being worked on.
> >
> > Also, FYI, I'll be on vacation for the entire next week.  So, whatever
> > change still needs to be done will be done after I get back.
>
> In addition to the visual comments on the ux-discuss list, some
> technical remarks (I haven't looked through all of it yet, expect more
> to come):
>
> - Extensions to the DataPilotSource API must be done in a compatible way
> (see the handling of the "Filter" property).

I've reviewed my change against the baseline, and my only addition to
the UNO API is two new constant values to MemberResultFlags.  It's my
understanding that adding new constant values to the existing constant
set is considered binary compatible.

Having said that, it's entirely possible that I'm misunderstanding the
intent of your comment here, so could you please clarify on this point?

Also, I'd like to see how the "Filter" property was handled in a
compatible way.  Could you point me to the place to look for?  I did my
own search, but I couldn't find what may look like the code you are
referring to.

> - We have to pay attention to keyboard accessibility (obvious key
> choice: Ctrl-D, as for page fields).

This is now implemented in koheidatapilot03.

> - The popup window has to implement accessibility API. Generally the
> easiest way for that is to use existing controls, like SvxCheckListBox
> for the item selection. For the menu entries a new control would have to
> be implemented, including the accessibility functions. Perhaps it's also
> possible to extend the VCL popup menu with an extra window, but I can't
> guarantee that's even possible without running into new problems.

I've switched to using SvxCheckListBox for the member list control.  So,
that should take care of that part of the accessibility, I assume.

Also, I'd like to know more about the accessibility function
requirements.  Could you give me some pointers, please?  I'm not that
familiar with accessibility requirements, as that subject always sounded
too abstract to me...  Any details would be great.

In addition to this, the "All" check box, and the two single-selection
buttons are now implemented as well, though I still need to have the
official images made for the single-selection buttons.  Right now, I
just use two ugly place holder images as a temporary replacement.

Anyway, it's still in progress.

Kohei

--
Kohei Yoshida - OpenOffice.org Engineer - Novell, Inc.
<kyoshida@...>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Niklas Nebel]

On 07/31/09 16:28, Kohei Yoshida wrote:

>> - Extensions to the DataPilotSource API must be done in a compatible way
>> (see the handling of the "Filter" property).
>
> I've reviewed my change against the baseline, and my only addition to
> the UNO API is two new constant values to MemberResultFlags.  It's my
> understanding that adding new constant values to the existing constant
> set is considered binary compatible.
>
> Having said that, it's entirely possible that I'm misunderstanding the
> intent of your comment here, so could you please clarify on this point?

An extension can supply its own implementation of the DataPilotSource
service, which can then be used with the "External source/interface"
option (see
http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Spreadsheets/DataPilot_Sources).
To maintain compatibility with such extensions, Calc must not rely on
the presence of new, added properties. This is different from services
which are only implemented in Calc.

> Also, I'd like to see how the "Filter" property was handled in a
> compatible way.  Could you point me to the place to look for?  I did my
> own search, but I couldn't find what may look like the code you are
> referring to.

For the "Filter" property, ScDPSaveDimension::WriteToSource just has to
be prepared for an exception from setPropertyValue, because it's not an
error if that property isn't supported.

> I've switched to using SvxCheckListBox for the member list control.  So,
> that should take care of that part of the accessibility, I assume.
>
> Also, I'd like to know more about the accessibility function
> requirements.  Could you give me some pointers, please?  I'm not that
> familiar with accessibility requirements, as that subject always sounded
> too abstract to me...  Any details would be great.

It has to work. :-)
See http://wiki.services.openoffice.org/wiki/Accessibility for some more
information and which tools can be used.

Niklas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Kohei Yoshida-2]

On Fri, 2009-07-31 at 17:05 +0200, Niklas Nebel wrote:

> On 07/31/09 16:28, Kohei Yoshida wrote:
> >> - Extensions to the DataPilotSource API must be done in a compatible way
> >> (see the handling of the "Filter" property).
> >
> > I've reviewed my change against the baseline, and my only addition to
> > the UNO API is two new constant values to MemberResultFlags.  It's my
> > understanding that adding new constant values to the existing constant
> > set is considered binary compatible.
> >
> > Having said that, it's entirely possible that I'm misunderstanding the
> > intent of your comment here, so could you please clarify on this point?
>
> An extension can supply its own implementation of the DataPilotSource
> service, which can then be used with the "External source/interface"
> option (see
> http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Spreadsheets/DataPilot_Sources).
> To maintain compatibility with such extensions, Calc must not rely on
> the presence of new, added properties. This is different from services
> which are only implemented in Calc.

Gotcha.

>
> > Also, I'd like to see how the "Filter" property was handled in a
> > compatible way.  Could you point me to the place to look for?  I did my
> > own search, but I couldn't find what may look like the code you are
> > referring to.
>
> For the "Filter" property, ScDPSaveDimension::WriteToSource just has to
> be prepared for an exception from setPropertyValue, because it's not an
> error if that property isn't supported.

Now I understand.  It appears that I was looking at the wrong place
(offapi).  Anyway, I've made changes so that optional properties are
treated as such.

>
> > I've switched to using SvxCheckListBox for the member list control.  So,
> > that should take care of that part of the accessibility, I assume.
> >
> > Also, I'd like to know more about the accessibility function
> > requirements.  Could you give me some pointers, please?  I'm not that
> > familiar with accessibility requirements, as that subject always sounded
> > too abstract to me...  Any details would be great.
>
> It has to work. :-)

My goodness...

I haven't looked into this yet, but this could be a big hurdle to
overcome depending on what level of change is required to get it work
fully.

Any chance we can integrate this feature without accessibility, by
leaving the accessibility a known issue for future work? :-)

> See http://wiki.services.openoffice.org/wiki/Accessibility for some more
> information and which tools can be used.

Thanks.  This is useful, though I have to say I'm stepping into an area
where I have no prior expertize.

Kohei

--
Kohei Yoshida - OpenOffice.org Engineer - Novell, Inc.
<kyoshida@...>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Niklas Nebel]

On 08/03/09 17:32, Kohei Yoshida wrote:
> Any chance we can integrate this feature without accessibility, by
> leaving the accessibility a known issue for future work? :-)

No, accessibility is considered an acceptance criteria by QA.

Niklas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Niklas Nebel]

On 06/24/09 18:16, Niklas Nebel wrote:

> On 06/24/09 05:00, Xu Ming Wang wrote:
>> - "Data Source buffer" sounds interesting. Now it would of course be
>> helpful to see the actual code changes for it.
>>    It is something like Excel's PivotCache, and better to save it in
>> the document file.
>>    If that, we need the approval of the ODF format proposal relate it.
>
> OOo 3.x has a cache (ScDPCacheTable), but it isn't saved, and the
> results are still created using ScDPItemData. We'll have to see how we
> can put these things together. Also, you're right, we'll have to clarify
> the file format handling.

A little update on the file format part:

The current plan is to extend the "ODF format version" list box in the
options dialog with an additional entry, to select between "1.2" and
"extended 1.2" ("extended" in the ODF 1.2 sense).

If "1.2" is selected, nothing is saved that is not in ODF 1.2.
If "1.2 extended" is selected (the default), extensions are saved as
"foreign" elements/attributes (this means, in a different namespace -
but accept both namespaces when loading).

Also, we want to use extensions sparingly, and generally only if a new
feature is really used. This is difficult with the cache table, where
the obvious approach is to always write it.

File format extensions are also needed for shapes in charts and notes in
Impress, so the UI and configuration change will probably be implemented
for one of these features (details will be sorted out next week, but
then I will be on vacation).

Niklas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Kohei Yoshida-2]

On Mon, 2009-08-03 at 11:32 -0400, Kohei Yoshida wrote:
> I haven't looked into this yet, but this could be a big hurdle to
> overcome depending on what level of change is required to get it work
> fully.

And I'm still working on this.  First of all, accessibility was
explicitly disabled in vcl for floating window instances, which my new
popup filter window is.  Enabling it was rather simple, but it took me a
while to figure that out.

Now, I'm working on implementing the accessibility functionality for my
popup window, but because all of this is new to me, progress is being
made rather slowly.

None of this has been checked in yet since a large part of my change is
still a bit of a hack.  But I'll start checking my code in once I
organize my code and clean it up a bit.

Kohei

--
Kohei Yoshida - OpenOffice.org Engineer - Novell, Inc.
<kyoshida@...>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Xu Ming Wang]

Find a critical issue:
The field items list in Hide/Show items or Display value options use the source data's original strings.
But some items' string maybe become same if they are float values or date values and use some special formats.
Then we can not identify them. I think need use the field item index to identify the field items and need redefine the ODF format about this.
There is the same problem in fields' name.

Attach a sample file:
(See attached file: issue.ods)


Sincerely,
Xu Ming Wang


Lotus Symphony
China Software Development Laboratory,Beijing
Phone: [phone]
E-mail : wangxum@...

Kohei Yoshida ---08/17/2009 08:44:40 PM---On Mon, 2009-08-03 at 11:32 -0400, Kohei Yoshida wrote:

Kohei Yoshida <kyoshida@...>

08/17/2009 08:44 PM

Please respond to
dev@...

To	dev@...
cc
Subject	Re: [sc-dev] about DataPilot

On Mon, 2009-08-03 at 11:32 -0400, Kohei Yoshida wrote:
> I haven't looked into this yet, but this could be a big hurdle to
> overcome depending on what level of change is required to get it work
> fully.

And I'm still working on this.  First of all, accessibility was
explicitly disabled in vcl for floating window instances, which my new
popup filter window is.  Enabling it was rather simple, but it took me a
while to figure that out.

Now, I'm working on implementing the accessibility functionality for my
popup window, but because all of this is new to me, progress is being
made rather slowly.

None of this has been checked in yet since a large part of my change is
still a bit of a hack.  But I'll start checking my code in once I
organize my code and clean it up a bit.

Kohei

--
Kohei Yoshida - OpenOffice.org Engineer - Novell, Inc.
<kyoshida@...>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...






---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Kohei Yoshida-2]

Hello Xu Ming,

On Tue, 2009-08-18 at 15:06 +0800, Xu Ming Wang wrote:

> Find a critical issue:
> The field items list in Hide/Show items or Display value options use
> the source data's original strings.
> But some items' string maybe become same if they are float values or
> date values and use some special formats.
> Then we can not identify them. I think need use the field item index
> to identify the field items and need redefine the ODF format about
> this.
> There is the same problem in fields' name.
>
> Attach a sample file:
> (See attached file: issue.ods)

Can you send me the file directly?  The mailing list has stripped your
attachment, so I don't see the file you attached.

Thanks.

Kohei

--
Kohei Yoshida - OpenOffice.org Engineer - Novell, Inc.
<kyoshida@...>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...