reportspecs
Francis J. Lacoste
flacoste at logreport.org
Wed Jul 9 03:08:03 CEST 2003
On dim, 2003-07-06 at 11:59, Wessel Dankers wrote:
>
> > Another enhancements would be to use the Lire Configuration
> > Specification Language in place of the custom <param> elements in the
> > report specification language. Thus, report specifications would use
> > elements from two namespaces (LRSML and LCSML).
>
> There is an additional complication: the config file currently determines
> where to look for reportspecs. If we'd use an lr_install and we would need
> configspec files to be generated from reportspecs, there's not much point
> in having the reportspec path as a variable anymore. Personally I feel that
> the variable can go but you may not agree. When those paths are static
> there's nothing against just parsing reportspecs to pick out the
> interesting configspec nuggets. Good use of XML namespaces too.
No, I can agree that most directory search lists be configured from a
"pseudo-static list". "Pseudo" because those lists wouldn't be
initialized from the XML configuration files. Byt they would be runtime
configurable variables (it would really only be modified by unit tests).
So the lr_reports_path, lr_filters_path (and even lr_converters_path)
could be removed from the config-spec and become used through a pattern
similar to the one used by the Lire::Config object itself to find where
to load the specifications from.
Reading the XML specifications directly from the report specifications
XML file seems like a good idea overall! With that, we don't really need
a lr_install tool. It could still be useful to run checks though, but it
would be less urgent.
Kind regards,
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/20030708/5b7e47e6/attachment.bin
More information about the Development
mailing list