[Seaside] html images
dan at shafermedia.com
Sat Jul 8 23:52:18 UTC 2006
Turns out this may have been a false alarm. My colleague was using an
old Squeakland.org image. When he moved to the newest Squeak.org
image, the PNG stuff, at least, cleared up right away. He's now very
Not sure about ImageReadWriter in all of that but PNGReadWriter seems
fine, according to him.
I'm still muddling about in the middle of the Seaside doing basic
stuff, so I'm not in a position to test any of that.
On Jul 8, 2006, at 3:45 PM, Dan Shafer wrote:
> I'm no expert, but I can share the experiences of a colleague who
> has been evaluating Squeak primarily from the perspective of its
> usefulness for building a graphically intense application.
> He experimented with PNGReadWriter and with ImageReadwriter and
> reported both of them distorted images pretty badly. (His
> characterization). He concluded after some effort that Squeak
> cannot be used for the kind of app he had in mind. I've seen/heard
> rumblings from time to time on the main Squeak list that the
> graphics engine in Squeak doesn't lend itself well to antialiased
> rendering of text and images but I've had zero experience of my own
> with it.
> On Jul 8, 2006, at 1:22 PM, Frank Sukhu wrote:
>> I have some code that generates html with an embedded image
>> <IMG>. I have
>> tried two ways of doing this:
>> Option 1. html imageWithForm: (ImageReadWriter
>> formFromFileNamed: fn).
>> Option 2. html image: fn.
>> where 'fn' is the pathname of the jpg file in my filesystem, e.g.,
>> When I use Option 1, the resulting image is very grainy - almost
>> Option 2 produces good results. I am trying to figure out why
>> this is the
>> Why is it that ImageReadWriter produces such a poor image when
>> compared to
>> the exact file being served by the httpserver?
>> I would appreciate any clues or pointers.
>> Seaside mailing list
>> Seaside at lists.squeakfoundation.org
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
More information about the Seaside