I've just finished splitting out my wxPython property editor into three packages:
basicproperty (Python 2.2 property classes),
wxoo (object-oriented wxPython controls and events), and
wxprop (property editing framework & controls).
I'll package those up shortly and re-release. Now, I'm working on rounding out the data-type editing controls. In particular, I'm looking for suggestions for polished (preferably BSD-licensed) versions of the following:
time-of-day editor -- visualised using an analogue clock (anyone have such a beast), set using combo-box, constrained to 00:00 through 23:59:59.999. I have a basic one, but it just does hour:min and doesn't do a good job of bounds checking.
duration editor -- text control able to take something like " 2d 6h 5m 3 s" (have that) and convert it to a (RelativeDateTime or) delta-seconds, + spin controls to increase/decrease (have it, but doesn't work very well, and is mx.DateTime-specific)
colour editor -- should I just use the wxPython dialogue? wxPyColours is overkill, but gives what I consider the nicest set of selections. Would be nice to have a colour-database browser available within the control as well.
style-set editor -- likely either use Ryan's or my own I suppose, but neither really fits into the aesthetic of the property-editing mechanisms...
style editor -- alternately, provide a property-based mechanism for changing the properties of styles (for instance, the font is a property of a given style, the colour, the size, the bold/italics/strikeout, etceteras). Provide the preview window below the property table and edit the styles in the table.
file/directory selection controls -- preferably ones that automatically support such things as "ensure the directory exists", "query on attempt to select existing file". FileBrowseButton should work with some sub-classing I think.
icon choice/edit -- sketch/load/cut/copy/paste of icons/small images. Not looking for photoshop, just something that would let a user customise their icons in-app.
Also wondering if there are any other suggestions for primitive (standard) data types that I should be considering.
Have fun,
Mike
···
_______________________________________
Mike C. Fletcher
http://members.rogers.com/mcfletch/