johnf wrote:
> I think you are right. But mostly in Larry's form. We have issues of long
> loads and other issues. The thinking was some of the load issues had to do
> with Dabo. So in an effort to increase performance I believe we tried direct
> calls. Larry's form is extremely complex and and we need it to work so
> he/we do what ever it takes. But I think it's also true that Larry has not
> always used the best approch to getting the job done. But that is not the
> main cause of the issues the form has. Larry's is always pushing the edge.
> And rather than reporting the problems he runs into he attempts to program
> around them. For example when the addWhere did not work for him he decided
> to use a temp cursor. Yes it works but it avoids the framework and all the
> features available from the framework. So at each level (feature of the
> form) we see work arounds.
Complexity at the UI level is a sign of trouble. The UI level should mostly
consist of:
+ 75%: instantiating and laying out of controls.
+ 20%: catching events and directing to appropriate biz-level methods
for processing.
+ 5%: other/misc.
Form complexity implies a ton of input fields. Not necessarily a bad thing: in
one of
my forms I have about 30 input fields and they are all needed.
But code complexity is a bad thing. BTW I don't have any wx-specific calls in
my
code, except to interact with FloatCanvas, which Dabo hasn't wrapped.
And if these temp cursors occur in the UI layer instead of the biz layer, that
would
seem to be a sign of trouble, at least in my opinion.
Paul
_______________________________________________
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]
