(patch) percentages in chart tooltip

[Holger-24]

Hi,

attached is a very small patch that adds percentages to the tooltip in
chart view.

What I actually would want to have in this tooltip (or somewhere on the
screen) is a brief list of the most important transactions corresponding
to that data point. This way, if I saw a strange bump in my captial
chart, I could hover on the bump and be reminded of the fact that it was
just the washing mashine that I bought two months ago.

Unfortunately I noticed that the class KReportChartView is completely
oblivious of the actual transactions underlying the KDChartTableData
object it has access to. This is sad. I guess the classes
KReportChartView and PivotTable require a major refactoring before that
tooltip can display what I want. In particular, I think PivotTable
should instead of a method 'drawChart' have a method 'prepareChartTable'
that returns an object of a new class, say KReportChartTable, that is
derived from KDChartTableData. This object should then be given to
KReportChartView, which in turn can use the object like a
KDChartTableDataBase object to draw the chart. In addition to the
KDChartTableData functionality, KReportChartTable should provide access
to the corresponding transactions as well as to the chart settings that
KReportChartView needs (am I a pie chart, line chart? what line width
shall I use?, etc).

A different approach would be to make KReportChartTable derived from
both PivotTable and KDChartTableData. I don't know whether that would be
a good idea, though.

Is it worth working on that or should it be postponed until after the
first more confident kde4 builds?

-- Holger.


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
KMyMoney2-developer mailing list
KMyMoney2-developer@...
https://lists.sourceforge.net/lists/listinfo/kmymoney2-developer

I'm working on the charts of the KDE4 version.  

If you want to help with it, you are welcome.

I won't be making any big changes to the KDE3 version, particularly to reports or charts, because the changes are huge and not portable. 

Regards,

Alvaro

On Sat, Oct 10, 2009 at 6:08 PM, Holger <yllohy@...> wrote:

Hi,

attached is a very small patch that adds percentages to the tooltip in
chart view.

What I actually would want to have in this tooltip (or somewhere on the
screen) is a brief list of the most important transactions corresponding
to that data point. This way, if I saw a strange bump in my captial
chart, I could hover on the bump and be reminded of the fact that it was
just the washing mashine that I bought two months ago.

Unfortunately I noticed that the class KReportChartView is completely
oblivious of the actual transactions underlying the KDChartTableData
object it has access to. This is sad. I guess the classes
KReportChartView and PivotTable require a major refactoring before that
tooltip can display what I want. In particular, I think PivotTable
should instead of a method 'drawChart' have a method 'prepareChartTable'
that returns an object of a new class, say KReportChartTable, that is
derived from KDChartTableData. This object should then be given to
KReportChartView, which in turn can use the object like a
KDChartTableDataBase object to draw the chart. In addition to the
KDChartTableData functionality, KReportChartTable should provide access
to the corresponding transactions as well as to the chart settings that
KReportChartView needs (am I a pie chart, line chart? what line width
shall I use?, etc).

A different approach would be to make KReportChartTable derived from
both PivotTable and KDChartTableData. I don't know whether that would be
a good idea, though.

Is it worth working on that or should it be postponed until after the
first more confident kde4 builds?

-- Holger.

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
KMyMoney2-developer mailing list
KMyMoney2-developer@...
https://lists.sourceforge.net/lists/listinfo/kmymoney2-developer

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
KMyMoney2-developer mailing list
KMyMoney2-developer@...
https://lists.sourceforge.net/lists/listinfo/kmymoney2-developer

I will write a little more on this, as to give you an idea of context, and perhaps where we are headed with reports in later versions.

On Sat, Oct 10, 2009 at 6:08 PM, Holger <yllohy@...> wrote:

Hi,

attached is a very small patch that adds percentages to the tooltip in
chart view.

What I actually would want to have in this tooltip (or somewhere on the
screen) is a brief list of the most important transactions corresponding
to that data point. This way, if I saw a strange bump in my captial
chart, I could hover on the bump and be reminded of the fact that it was
just the washing mashine that I bought two months ago.

For this you need to add drill-down capabilities. Your analysis is correct in that the charts need to be refactored and become more integrated with KMM. In fact, I just finished a refactoring of the charts in the KDE4 version, to keep the existing functionality, but at the same time use the new features provided by the KDE4 charts.
However, there is an underlying problem in that PivotTable does not have detailed transaction info, so you have to solve that problem first. My view here is to provide a capability to be able to click a cell of a summary report and that will create a transaction report with the detail you are looking for. Only when that is done, we can talk about being able to access that info from the charts.

As you can see, there is a long road ahead, and help is always welcome.

 

Unfortunately I noticed that the class KReportChartView is completely
oblivious of the actual transactions underlying the KDChartTableData
object it has access to. This is sad. I guess the classes
KReportChartView and PivotTable require a major refactoring before that
tooltip can display what I want. In particular, I think PivotTable
should instead of a method 'drawChart' have a method 'prepareChartTable'
that returns an object of a new class, say KReportChartTable, that is
derived from KDChartTableData. This object should then be given to
KReportChartView, which in turn can use the object like a
KDChartTableDataBase object to draw the chart. In addition to the
KDChartTableData functionality, KReportChartTable should provide access
to the corresponding transactions as well as to the chart settings that
KReportChartView needs (am I a pie chart, line chart? what line width
shall I use?, etc).

A different approach would be to make KReportChartTable derived from
both PivotTable and KDChartTableData. I don't know whether that would be
a good idea, though.

Is it worth working on that or should it be postponed until after the
first more confident kde4 builds?

There is work in progress to refactor the KDE4 charts, maintaining existing functionality. I hope most details will be ironed out over the next few weeks, in a way that most chart-specific functionality will be provided by KReportChartView and its underlying classes, and the PivotTable class can handle the report itself, thus simplifying maintenance.

Regards,
Alvaro

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
KMyMoney2-developer mailing list
KMyMoney2-developer@...
https://lists.sourceforge.net/lists/listinfo/kmymoney2-developer