On Feb 3, 2011, at 11:47 AM, Ed Leafe wrote:

>> Any chance that this can get fixed as I think this wxPython tool is 
>> really very useful.
> 
>       This is an example of a wrapping candidate. I'm sure that this tool 
> (not terribly familiar with it except for the fact that it exists) makes 
> assumptions about every item in the wx.Frame; these assumptions are not 
> always true for Dabo objects. Many times we have an external object that has 
> a reference to the underlying wx object; this would prevent the inspection 
> tool from accessing what it needs.
> 
>       There are two possibilities:
> 
> 1) a simple wrapper that intercepts the exceptions and massages the 
> references so that the wx tool works correctly
> 
> 2) re-creating the tool in native Dabo.
> 
>       I would try the former initially, and if the differences are too 
> difficult to manage, try re-creating in Dabo. From what I see, most of what 
> would be needed is already present in Dabo (e.g., the Class Designer property 
> sheet does exactly this); it's simply a matter of creating the UI.

        I've gone the second route, as the former had way too much wx-level 
stuff to be useful to a Dabo developer. I've just committed my first pass at 
the tool, so if you could grab the latest svn commit and let me know what you 
think, I would appreciate the feedback.



-- Ed Leafe



_______________________________________________
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/[email protected]

Reply via email to