On Sunday 30 September 2007 09:01, Ed Leafe wrote:
>Non-issue. Nothing I have suggested requires this, and it is counter- 
>productive to keep repeating this as an item for discussion.

Repeated for others who may not have followed the earlier discussion.  Since I 
am opening a new thread.

>         Why not use the alternatives I proposed? Why limit yourself to  
> considering only these two options?

Ed, I asked for help because I thought something was wrong with Larry's 
approach.   I believe I got the same two suggestions I offered.  Today was 
the first time you offered something different - at least I understand it 
differently.

> I must say it seems frustrating when I've offered several possible  
>solutions that were never tried, even after I explained your  
> misconceptions about what I was proposing.

In correct, we did try what we understood to be your suggestions.  I did not 
follow Larry's lead without protest and without other attempts.  And I spent 
time attempting what you were suggesting.  I could have been me but then 
again it was also Larry that mis-understood.   And in the end both of us were 
un-successful.   You said it yourself in your last email to Larry - we didn't 
understand.

> A call to a method is just as fast when that method is doing the  
>same thing. Calling a method in the table is no faster than calling  
>the exact same method in the bizobj. 

Yes I agree but that is not issue with bizobj's.  As explained by Larry other 
baggage is included with bizobj's.  Such as having Dabo review the bizobj for 
every update.  But I believe the DataSet approach should have worked although 
I did not make it happen (at least not easily).

 >Again, dGridDataTable is a wxPython-specific implementation detail,  
>and should not be used unless a) you want to always use wxPython and  
>b) you know what you're doing.

We don't want to and no we don't know what we are doing with respect to 
wxPython.

>self contained code.
> IMO, this is a serious drawback. Should there be any other place in  
>the app that requires similar formatting, you have to re-create the  
>code again. The whole point of consolidating formatting logic in a  
>central place is to avoid this sort of duplication.

Exactly!


BTW :
Everything you have responded to was just a "lead in" into the real question.  
What about creating a way to define a function for a cell?  

So what do you think of providing an easy interface to defining a cell with a 
function???  I think your last suggestion to Larry should work but it's 
requires that developer have insight (training).  So I'd like your thoughts 
(or others can add their .02) on making it easier.  



-- 
John Fabiani


_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]

Reply via email to