On Jun 30, 2004, at 5:22 PM, Anthony Testi wrote:
> is it not possible that a developer would want to work with more then
> one of
> these 'widgets' at a time. Having them all the same name would make
> that a
> problem. I'm not sure it is a good long term idea to have a framework
> 'force' external widgets to conform to the frameworks naming scheme.
First, the reason for this discussion is that there might be
developers who have a different adapter installed, and don't want to
install another. Technically, if they are all written correctly, there
should only be *one* line that changes in the Backend scripts: the line
that contains the module's name. Everything else should be exactly the
same, since they should be implementing the same interface against the
same database.
In practice, though, there may be things that one adapater doesn't do
correctly and thus will need some additional coding to circumvent. So
it is possible that there will be more than a single line's difference
between the scripts for each adapter.
Developers are not going to need to switch these scripts in and out
constantly - they'll use the one that matches their setup. Therefore I
see no need to complicate things by making the choice of adapter a
dynamic process. We can include the various adapter scripts with Dabo,
and if someone wants to use one of those, she will simply rename that
to the common adapter's name, and all will work fine.
___/
/
__/
/
____/
Ed Leafe
http://leafe.com/
http://dabodev.com/
©2004 Ed Leafe |
