Speaking of that, one will notice that the class comment of UITheme has the examples list:
Common superclass for User Interface themes. Provides methods for creating new morphs in a standard way, various "services" like a file dialog, message dialogs etc. and also methods for customising aspects of the appearance of various morphs. Though conceptually abstract, no code is "missing". Subclasses, therefore, should override the aspects they wish to change. UITheme exampleBasicControls UITheme exampleBuilder UITheme exampleColorControls UITheme exampleDialogs UITheme exampleGroups UITheme exampleOtherControls UITheme exampleWindowWithToolbars But in 3.0 it is not in there, it moved to Widgets in 'Morphic-Examples-Widgets' with: ExampleBuilderMorph WidgetExamples Maybe worth a change in the class comment. Phil On Sat, Mar 22, 2014 at 10:42 AM, Sven Van Caekenberghe <[email protected]>wrote: > The theme stuff is really hard and complex. It is impossible to maintain > multiple ones, especially if those are seldom used. Maybe it would have > been better to remove all those that are not properly maintained. But that > would not have made you happy either I guess. > > It is really simple: with the limited resources that we have, we cannot > maintain all of them. > > On 22 Mar 2014, at 09:33, Hilaire Fernandes <[email protected]> > wrote: > > > Hello, > > > > <bitter> > > In Pharo3, the UITheme hierarchy seems to have been hit by random > > refactoring (it really looks like that) because it is broken in so many > > place[1][2][3] and in such obvious way (very visible). > > > > It will be nice the random refactorers take(s) full responsibility to do > > the job from A to Z, and not only from A to H. > > </bitter> > > > > [1] https://pharo.fogbugz.com/f/cases/12554/Broken-Watery-theme > > [2] https://pharo.fogbugz.com/f/cases/13112/Broken-Vistary-theme > > [3] https://pharo.fogbugz.com/f/cases/13114/Broken-PharoTheme > > > > Thanks > > > > Hilaire > > > > > > -- > > Dr. Geo http://drgeo.eu > > >
