At 09:35 AM 6/7/2001 +1000, Cees Hek wrote:
>On Tue, 5 Jun 2001, Stephen Adkins wrote:
>
> > I originally thought that every attribute should be required to be
> > configured from the config file.
> > Now I think that every configurable attribute should be *able* to be
> > configured from the config file, but that it should also be *able* to
> > be overridden by the constructor parameters.
>
>Excellent. That's exactly how I see it.
>
> > I actually would like to create data-bound controls as well,
> > where the SQL to populate the controls can be configured into the
> > config file and the values are populated at run time.
>
>I really like the sounds of that
Yup, although I don't want it lose that that I believe this logic belongs
in a container for the widgets with an API to change the widget values as
stated previously using the GPC paradigm of PHP. But adding session,
database(s), and other data sources as necessary.
ie DB Logic itself probably should not go into the widgets themselves. And
furthermore, by providing the appropriate mutator methods in the widgets
and the DBAwareness in a container, then all widgets will be DBAware.
Later,
Gunther
|
