Janko Mivšek wrote:
>
>> how does one work with resources (e.g. image files (GIFs, ...)) used
>> in the application when working with Monticello and in general?
>
> Due to lack of decent resource management in all Smalltalks we usually
> put such resources directly into methods, usually as lit
Janko Mivšek wrote:
>
> Pretty easy. We have a tool method which reads a file and converts it
> into such a method. Such method just returns a file content as byte
> literal array. Concrete instance from DefaultWebStyle in Aida:
>
Thanks for the reply. I was actually asking about using Montic
Bert Freudenberg wrote:
>
> Typically, they don't. Usually packages only have code. Small things (like
> icons) are converted to source code.
>
I think that's where I'll start, but I'm not quite there. This is what I
did so far, cobbling together things from old posts:
stream := ReadWriteStre
Thanks. That's exactly what I wanted to know.
Sean DeNigris
s...@clipperadams.com
--
View this message in context:
http://n4.nabble.com/Resources-with-Monticello-tp112895p1840677.html
Sent from the Squeak - Beginners mailing list archive at Nabble.com.
Hi Sean,
On 09. 04. 2010 23:03, Sean P. DeNigris wrote:
>>> how does one work with resources (e.g. image files (GIFs, ...)) used
>>> in the application when working with Monticello and in general?
>> Due to lack of decent resource management in all Smalltalks we usually
>> put such resources di
On 14.04.2010, at 17:41, Sean P. DeNigris wrote:
>
>
> I'm sure this must be a common goal: how do package developers, who use
> Monticello, distribute non-code things, like files (such as image files)
> with their packages?
Typically, they don't. Usually packages only have code. Small things (l
On 14.04.2010, at 19:20, Sean P. DeNigris wrote:
>
>
>
> Bert Freudenberg wrote:
>>
>> Typically, they don't. Usually packages only have code. Small things (like
>> icons) are converted to source code.
>>
> I think that's where I'll start, but I'm not quite there. This is what I
> did so far,
