> I don't see a way that is fundamentally better than what you're doing
> there, but one minor tweak is that you could turn the images into
> something like this
>
> (make-an-image #"...image's bytes go here")
>
> instead of a url, where make-an-image builds the image from the bytes.
> But maybe y
On Tue, Aug 9, 2011 at 3:57 PM, Robby Findler
wrote:
> Oh, I see. Thanks for clarifying.
>
> As best I understand it, then, you're adding the ability to have image
> (and other snip) constants in compiled code, something that elsewhere
> in the system we skirt around by just not compiling things (
Oh, I see. Thanks for clarifying.
As best I understand it, then, you're adding the ability to have image
(and other snip) constants in compiled code, something that elsewhere
in the system we skirt around by just not compiling things (eg when
building an executable if there is a file with an image
On Tue, Aug 9, 2011 at 3:50 PM, Robby Findler
wrote:
> I think you should be working with the wxme library, not with image
> snips directly. Did you investigate that?
Implicitly, that's being done for me. I'm depending
read-accept-reader to do the right thing when I read wxme-encoded
source prog
I think you should be working with the wxme library, not with image
snips directly. Did you investigate that?
Robby
On Tue, Aug 9, 2011 at 2:39 PM, Danny Yoo wrote:
> I'm trying to support image snips in Whalesong. I think I have
> something working, but wanted to run it by folks on the list to
I'm trying to support image snips in Whalesong. I think I have
something working, but wanted to run it by folks on the list to make
sure I haven't done something incredibly silly.
One of the problems that comes up is due to architecture: Whalesong
uses compiler/zo-parse, and compiler/zo-parse on
6 matches
Mail list logo
