On Jun 5, 2007, at 11:17 AM, Uwe Grauer wrote:
> Are you saying, that if you would have integrated them as python
> properties, it should get handled in dFormMixin the same way as it
> works
> in CD forms?
> For what is that code in dFormMixin.__init__() (check of CxnFile,
> CxnName) good for? Is it for nonstandard usage of the framework?
>
> I still don't understand why CD forms get different handling than
> coded
> forms.
Uwe, you have to remember that the original design for dForm was
done 3-4 years ago, and the Class Designer was not even thought about
at the time. These properties were only added a few months ago in
order to enable the Class Designer to work with saved connection
info, rather than forcing users to write code to establish connections.
The reason it works differently is that this is still a work in
progress. I'm sure that if I had a second set of eyes reviewing all
of the changes made to the Class Designer such discrepancies would be
much rarer. But Paul has been too busy to become involved with the
whole Class Designer/IDE process, so things like this happen.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
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/dabo-dev/[EMAIL PROTECTED]
