Re: [Perfparse-devel] Summary work.

[Yves M. <yme...@li...>]

Hi all :)

I answer only where my comments are needed :)


> Next, the --no-raw-data flag.
>
> Yves suggested this could be another callback to store the summary data=
.
>   This worries me:
> 1. The call back will be identical to the existing one.
> 2. As we add more ways of analyzing data, more and more callbacks will
> be needed.
>
> I wonder as a an alternate option with one callback:  Whether the
> attached modules should have their own option set, which is added to th=
e
> main option set and displayed together when --help is shown, set by the
> same code.  But this is complex for a small problem :)

I have not followed the whole discussion about summary data. Maybe a new =
callback is not
necessary.

> In the short term, I suggest making the option array visible to modules=
.

This is already the case. Check where the DB_user and DB_pwd come from :)

>    Sorry, another global variable.  They can read them and action them
> as they see fit.  In this case we can now have two flags:
> 	--no-raw-data
> 	--no-raw-summary-data
> Which can be viewed in the function to store lines of data.
>
> What do you all think?

This is maybe the good way to do it. I just say "maybe" because I have no=
t followed the
whole discussion :)

> This is one for my self or Yves to hack.

config_file.c and libpp_common.h
And one additionnal line in perfparsed.c and perfparse-log2any.c to say t=
hat we use it
(used only when printing help)


> -----------------------------------
>
> Finally the display of data.  I can think of various ways of displaying=
:
>
> -	Report of activity for a day with summary.
> -	Line graph showing percentage activity of each state.
> -	Pie chart of summary....
> -	Exported CSV or XML reports.
>
> Tim, what do you want to see?

About displaying, in the far future (I hope to be there anyways), I sugge=
st a library to
compute the data, and binaries that use the library to produce files (com=
mand line
tools), html (CGI), and other good things.
This is for the far future, probably after perfparse-1.0.
The reason why I say it is if you can code with that if mind, it will may=
be be easier to
move the existing code in that library one day ?

Yves
--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- Perfparse   - http://perfparse.sf.net/                           -