Gunther Birznieks <[EMAIL PROTECTED]> wrote:
>At 12:15 PM 5/28/01 -0400, Stephen Adkins wrote:
>>The rendering of this widget as HTML requires at least the following
>>
>> * config information (Widget::Config)
[snip]
>> >Also will we require XML to configure? Or is this also an optional feature
>> >that you more or less want for yourself but others can choose to not use?
>>
>>Configuration data is read in via the Widget::Config class, and this class
can
>>be replaced with a class which reads config data from any other source, as
>>long as
>>it conforms to the same calling interface.
>>
>>I was under the impression that XML was your desired means of writing a
>>config file.
>>Do you have a preference to use something different?
>
>I like XML for Config files, we use that in our Java stuff all the time.
>But Perl is one of the nicest and flexible config file languages out there.
>IE My config file is Perl.
>
>Anyway, I think it is weird to think of configuring just widgets. Usually
>you configure an application and widgets are a part of that. But everyone
>here will have a different way of preferring to write their application
>config whether it's XML or Perl and what features of these that are used
>(eg just a set of scalars or references to hashes or ... ?) or in the case
>of XML using attributes versus subtags...
IMHO, having a configuration API is much better than requiring a particular
way to do configuration. If the backend configuration is done via Perl code,
then any configuration file format can be supported with an appropriate module
handling it.
These widget configurations will need to be flexible enough that I can
construct a page with them without any knowledge of how they will look -- the
configurations should be tie-able to an overall theme for the site. I've
always been a champion of themes for websites. I should be able to select a
configuration at run-time without a lot of trouble.
--
James Smith <[EMAIL PROTECTED]>, 979-862-3725
Texas A&M CIS Operating Systems Group, Unix
