[Pharo-project] About the icons
Regarding the icons, i would like to spend some time during ESUG ( or the spring) merging what i have in Gaucho. Based on the previous work in MenuIcons and ThemeIcons, i've created an icon family importer, where all the icon contents are stored as methods in the corresponding subclass of GMIconFamily. A brief introduction, Object subclass: #GMIconFamily instanceVariableNames: 'iconsGroups aliases' classVariableNames: '' poolDictionaries: '' category: 'GauchoGUI-Morphic-ImagesAndIcons' Where each GMIconFamily has the corresponding IconFamilyBuilder, that imports the external files from icon specs. IconsFamilyBuilder>>build | specs secs | specs := self iconsSpecs . specs do:[:each| each resourcesFolderName: self resourcesFolderName ]. ^ GMIconFamily createFamilyNamed: self iconFamilyName specs: specs . For example, IconsFamilyBuilder subclass: #GauchoIconsBuilder GauchoIconsBuilder>>iconsSpecs ^ self definedInSpecs , self bugSpecs, self accessorsSpec, .... GauchoIconsBuilder>>build . Will produce a bunch of methods in the GMIconFamiliyGaucho, that will hold the contents and provide access to the icons ( and also act as a form cache) then you can do icon := IconMorph named: 'apply' size: 16 familyNamed: 'gaucho'. I think that it wouldn't be hard to integrate this into Pharo1.2, to have a standardized manner of requesting icons, managing the forms, and easily importing external icon-families. I would be willing to work on this during the sprint. Fernando
For completeness when it comes to resources, I also have a port of the Assets package found in VisualWorks :) (Not performing very well without the once caching not working though) Cheers, Henry On Aug 31, 2010, at 10:38 35AM, Fernando olivero wrote:
Regarding the icons, i would like to spend some time during ESUG ( or the spring) merging what i have in Gaucho.
Based on the previous work in MenuIcons and ThemeIcons, i've created an icon family importer, where all the icon contents are stored as methods in the corresponding subclass of GMIconFamily.
A brief introduction,
Object subclass: #GMIconFamily instanceVariableNames: 'iconsGroups aliases' classVariableNames: '' poolDictionaries: '' category: 'GauchoGUI-Morphic-ImagesAndIcons'
Where each GMIconFamily has the corresponding IconFamilyBuilder, that imports the external files from icon specs.
IconsFamilyBuilder>>build | specs secs | specs := self iconsSpecs . specs do:[:each| each resourcesFolderName: self resourcesFolderName ]. ^ GMIconFamily createFamilyNamed: self iconFamilyName specs: specs .
For example,
IconsFamilyBuilder subclass: #GauchoIconsBuilder
GauchoIconsBuilder>>iconsSpecs ^ self definedInSpecs , self bugSpecs, self accessorsSpec, ....
GauchoIconsBuilder>>build .
Will produce a bunch of methods in the GMIconFamiliyGaucho, that will hold the contents and provide access to the icons ( and also act as a form cache)
then you can do
icon := IconMorph named: 'apply' size: 16 familyNamed: 'gaucho'.
I think that it wouldn't be hard to integrate this into Pharo1.2, to have a standardized manner of requesting icons, managing the forms, and easily importing external icon-families. I would be willing to work on this during the sprint.
Fernando
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
icon := IconMorph named: 'apply' size: 16 familyNamed: 'gaucho'.
I think that it wouldn't be hard to integrate this into Pharo1.2, to have a standardized manner of requesting icons, managing the forms, and easily importing external icon-families. I would be willing to work on this during the sprint.
yes would be great!
participants (3)
-
Fernando olivero -
Henrik Johansen -
Stéphane Ducasse