Smalltalk ui icons iconNamed: #protocolExtension. Still ugly, but I’m not happy with the idea of a selector-per-icon… they will never be enough and well… is like a monolithic vision. Not that what we have is much better, but you can consider it an iteration :)
Esteban > On 04 Feb 2016, at 16:19, Aliaksei Syrel <[email protected]> wrote: > > Hi > > For ages to access an icon we used: > Smalltalk ui icons protocolPrivateIcon > > Smalltalk ui icons returns an instance of ThemeIcons. > After refactoring (case https://pharo.fogbugz.com/f/cases/16651 > <https://pharo.fogbugz.com/f/cases/16651>) all methods to access icon (for > example protocolPrivateIcon) were removed. > > ThemeIcons>>#doesNotUnderstand: aMessage converts message sent to iconNamed: > aMessage selector which works. > > BUT we have this all over the image: > <Screen Shot 2016-02-04 at 16.13.03.png> > > So, what is the best practice to access icons to use in application? > > Cheers, > Alex >
