Eric Scharff a écrit :

>Putting the images into methods is intriguing for my small
>images.  That way the images would even be managed by Monticello
>version control.  There are already 48K worth of images (when
>represented as method source) in my application, and there are
>likely to be more.
>
>The problem with this scheme is that for extremely large images
>(background images, for example), this scheme would not work
>because the resulting uncompressed images (which is returned by
>Form>>storeOn:) are immense.  I could base64 the large jpgs,
>perhaps, but that wouldn't be efficient either.
>
>Is there an example of using SAR for this?  Or is SAR not the
>preferred method of doing it?
>
>-Eric
>
>  
>
In tamaris, all icons are stored into files and
loaded on install (they are all kept into Tamaris.sar).

----- postscript ------
(self membersMatching: 'forms/*.*')
    do: [:f | TamIcons
            importFormFromStream: f contentStream
            path: (f fileName copyFrom: 7 to: f fileName size)
            index: TamIcons formsIndex].
....
--------------------------------

see TamIcons class, I think it does what you want.
for example, after loading,
TamIcons mimeIcon: '10x10/mimetypes/class'
return a form which was stored into "forms/10x10/mimetypes/class.png"  file

alain

>	
>		
>__________________________________ 
>Yahoo! Mail - PC Magazine Editors' Choice 2005 
>http://mail.yahoo.com
>
>
>
>  
>