Ho Torsten, No, it is not broken. As I said, is an ongoing change: https://pharo.fogbugz.com/f/cases/16651 ThemeIconPack is finally renamed as ThemeIcons and all external packages extending it will be able to use. Now, some thing will not be backward compatibility: - if you used directly ThemeIcons children - it you used outside the class some of the private methods (like *IconContents, etc.) - if you extended ThemeIcons children instead ThemeIcons they will need to be adapted. I hope there are not so many because those issues were never recommended anyway :) (but even if not recommended, I needed to change a lot of miss-uses in some packages⦠I would like to have a monkey rule to forbid this kinds of integrations into the image :S) I started this change last friday, in commit 50357⦠it is tuesday and we are in commit 50366. Itâs been just 4 days and 9 builds⦠(and btw SLICE is not integrated because some weird monkey issues, not because is not ready). so, please⦠be patient! ;) Esteban
On 06 Oct 2015, at 09:54, Torsten Bergmann <astares@gmx.de> wrote:
Hi Esteban,
It's broken: "Smalltalk ui icons" now returns an instance of ThemeIconPack instead of the usual ThemeIcons/subclass.
But most external packages extended ThemeIcons or subclasses with own icons as this is/was up to the change the default way to do it. It's not possible to access these extensions anymore using
Smalltalk ui icons myIcon
now. I understand that you needed a "break" - but it is not fun if you "break" ;)
Bye T.