wxMimeTypesManager demo replacement

Since you also asked about one of the issues on wxPython-dev I'll CC this message there.

Jeff Grimmett wrote:

Robin,

Here's the first draft of the replacement for the wx.MimeTypesManager demo.
I've also improved a bit on it.

o Entering an ext or MIME type in the text ctrl will
  select the corresponding value in the listbox
o Added EVT_TEXT_ENTER binding to text ctrl

Now for the issues:

o As noted, the lowest TextCtrl goes off the window instead
  of forcing a resize or getting itself resized, or whatever.
  Reducing the border sizes helped some, but there are still
  issues when it's run from the main demo.

The problem is that the default size of the multi-line textctrl happened to be bigger than the size available, and so since it is a sibling to the static box it was allowed to overflow it. I changed the initial size of the control and then set that row to be growable and it works fine now.

o I am seeing error (debugging) errors in this version
  that I was not seeing in the old wxPython-based version.
  The same code is used to extract info, so I'm a bit at
  a loss to explain this.

Looks like wxMimeTypesManager needs to be fixed to recognize -- or at least ignore -- the additional parameter fields in some of the commands...

o If I enter 'tif' or 'tiff' as a file type in the text
  box and search for extension, the whole wx App freezes
  up. This does not happen in the old one. Again, same
  code, so I'm not sure what that means.

Works fine here. What app do you have associated with TIF files?

Good first start, though. If the code meets with your approval, you can get
rid of mimetypes.wdr and mimetypes_wdr.py in the demo dir.

I'm going to check it in, but if you have time to work on it a little more please try to do it without so many wxStaticBoxes. Two reasons for this: first the static lines are not subtle on GTK as they are on Windows (especially XP) and so it looks a little too "busy" and ugly on wxGTK, secondly, it is possible that the problem that caused us to enforce items within a staticbox to be siblings of it will be fixed and allow the more logical child relationship instead, (in fact, at least one possible new platform will require it to be that way) so the fewer static boxes in this already complex layout the easier it will be to convert if/when that change happens.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!