Why not on SM?

A. Don’t know how and where to start looking.
B. It is no way near finished. I wanted to get feedback.

Have a look. I haven't really made anything new, what I have done is pull
together a whole bunch of work already in Squeak.

It means I should be able to have a file name that IS portable and a
portable way of accessing files and codecs. Because Resources are chained
together you can remove and replace the resource at the start of the chain
and expect the same result.

If you want to hook into the framework (premature at the moment) basically a
Resource is just a consumer of a stream (FileResource is a consumer of a
File URI). So ImageReadWriter codecs slot in very easily indeed.

Russell

> -----Original Message-----
> From: squeak-dev-bounces at lists.squeakfoundation.org [mailto:squeak-dev-
> bounces at lists.squeakfoundation.org] On Behalf Of goran.krampe at bluefish.se
> Sent: Tuesday, 25 May 2004 8:52 PM
> To: The general-purpose Squeak developers list
> Subject: Re: [ENH] Resources
> 
> "Russell Penney" <russell.penney at tincanct.com> wrote:
> > Attached are the beginnings of the Resource framework I threatened to =
> > do.
> 
> Kinda interesting. As you may now I am fumbling with resources in SM
> too. Will take a look.
> 
> Why don't you publish it on SM btw? :)
> 
> regards, Göran