Hello, Well, if you can't do it, don't. I mean there is no obligation to refactor working stuff if you don't have the resource to go from A to Z. It is ok.
Then I *don't* understand something else: why so many new themes? It is ridiculous to see PharoTheme, BlueTheme, OrangeTheme, Pharo3Theme. Some are not even working properly. May be there is a logic, but I don't get it. For the broken Vistary theme, I identified the problem, and I'll let Ben apply the fix as it seems appropriate to him[1]. Thanks Hilaire [1] https://pharo.fogbugz.com/f/cases/13112/Broken-Vistary-theme Le 22/03/2014 10:42, Sven Van Caekenberghe a écrit : > 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 > > > -- Dr. Geo http://drgeo.eu
