having problems with s1ms reporting

[Francis J. Lacoste]

On lun, 2003-06-23 at 13:20, Lire wrote:
>     my problem arise with informs tables that have more that one columns of
> names:
> 
>     (ex:           Host     Ip       Num_Connections   %Num_Connection)
> 
>     that graph paint always the first column, therefore the numeric results
> dont appear very well. i submit an example of inform.

Yes, that is limitation of the current graphing tool. It wasn't updated
for the multi-column report.

> 
>     about your solution, i worked with ReportParser and PloticusChartWriter
> and i think how runs, but i have doubts:
> 
>             - how adds adds new attributes/elements to the report
> specification XML format? i want adds new parameter of chart
>                 that indicates the name of column that i want to paint in
> the graph.

Adding an attribute would be a lot simpler than adding new elements. In
all case, the steps involved will be :

1- Add the new attribute/elements to the LRSML DTD
(all/lib/xml/dtd/lrsml.xml). That document is a DocBook XML document in
which the programlisting elements contain the actual DTD. The DTD and
its documentation are automatically generated by the Makefile

This step is actually optional, since we aren't using a validating
parser.

2- Add the new attributes/elements to the parser
(Lire::XMLSpecContainer). It could also be added to the ReportSpec
object model (Lire::ReportSpec)

3. Since the attributes needs to be available to the generated report,
you'll need to repeat step 1 and 2 for the LRML DTD and the
Lire::ReportParser and Lire::Report::Subreport class.

In your use case, it would probably be simpler to create a new tool
which process the existing XML report and would take its configuration
from the command line or configuration variables stored in the standard
configuration framework. With this new framework, it is surprinsgly easy
to add new configuration variables.


> 
>             - moreover, this changes affects to others informs (like
> sendmail what i uses like you define by default), doesnt it?
> 

*Adding* (not modifying) new attribtues/elements or configuration
variables should have no impact on existing code. If you install the
patched copy of Test::Unit, you can run the unit tests more certainty.


Francis J. Lacoste

-- 
Francis J. Lacoste              . .           http://www.logreport.org
/^LogReport$/               . .               flacoste at logreport.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.logreport.org/pipermail/development/attachments/20030625/7ecbd2ee/attachment.bin