On Aug 31, 2011, at 11:13 AM, Paul McNett wrote:
> I also think that the XML spec for .cnxml could be relaxed to allow for
> non-generic
> (backend-specific) keys/values to be added to it. The CxnEditor could, at a
> minimum,
> discover these extra keys in the cnxml and allow editing of them. Moving
> forward from
> there, it could ask each backend for the list of supported keys and default
> values
> specific to that backend.
We already have backend-specific editing: sqlite is handled separately
from all the server-based backends. Each ODBC backend may have different keys,
but they are a very small finite set. My suggestion would be to define the set
of keys for mssql, vfp, etc., and then have the CxnEditor display those keys
when that backend type is selected. What I don't want to see is a generic
"extra stuff" key with free-form text.
I also don't think that "discovering" keys is a good approach. There
are just too many ways for that to go wrong. The set of keys for a backend
should be defined.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message:
http://leafe.com/archives/byMID/[email protected]
