As noted in the Smalltalk Tidbits, Industry Rants blog item: Cincom Smalltalk Product Direction: UI blog, Widgetry is being put to bed.

It is only appropriate though to make a final official update of the code base.

Version 1.33 of Widgetry, and Version 1.10 of WidgetryTesting are now published to the public repository.

Here are the changes from 1.12 of Widgetry:

• Center align input/display for InputField
• Grid resizes cause the recreation of columns (and thus rows and cells) over and over
• WordWrapped TextEdit can scroll instead of wrap if close to right edge insertion
• Flicker in Grid header row when resizing
• Resizer in Form doesn't update panes outside the edge of Resizer
• Hitting navigation keys while in TreeView edit, moves instead of accepts edit.
• ScheduledWindow closeEvent: announces twice
• Sorting announces SelectionChanged when it shouldn't
• Consistent Grid rows and columns accessors
• Resizing TabControl has display errors external and internal
• Row headers as buttons look bad and display no interior decoration
• GridHeader label not displaying when scrolled
• Displaying Images in Buttons in A Sub-form in a scrolled Form and Resizing Problems
• Removing columns does not reset maximum item width
• Bad comparisons in RelationalFrame
• Bad comment in #exitTabStyle
• Widgets in scrolled forms don't react to mouse events properly
• Panes in a Form in a Scrolled Form (double nesting) don't react to clicks or display correctly
• Setting barColor: on ProgressBar causes DNU
• GridAgent can answer itself instead of pane for handlerForMouseEvent:
• ResizingSplitter problem when there is a Toolbar

Version 1.10 of WidgetryTesting has as a prerequisite a new package named WidgetryTestExtensions. This package is a special version of RBSunitExtensions and effectively replaces that version. It is not Widgetry specific. What it does is it allows a Bundle to be run one Package at a time. This is important for Widgetry's test since each test case in each package used a common resource to set the look policy.

Without this package, in order to run Widgetry's tests, you had to select each package in the testing bundle, and run it, then select the next and so on. If you tried to run the bundle as a whole, it could take as long as seven hours, and the tests wouldn't be guaranteed to complete.

Also this final version of the tests have been somewhat optimized, and the overall time to complete them has improved by up to 25%. On my admittedly fast machine, that still takes about 45-50 minutes though.

It's Good To Be The King

I have one more Widgetry posting to make this later week before I say goodbye to this blog.

While I won't be out here talking about GUI any more, I am still a member of the VisualWorks engineering team. I will be moving on to lead the Store project come next week.

Let us raise our glasses one last time, and join me in one final salute: