Hi,
I have submitted some problems with MultiByteFileStream in 3.8 not being able to open on an image (.png).
However if one reverts FileStream class>>concreteStream to StandardFileStream then the FileList cannot be used to open files as StandardFileStream does not implement #converter: and friends.
This is a critical bug.
Brent
On Wednesday 02 February 2005 1:46 am, Brent Pinkney wrote:
I have submitted some problems with MultiByteFileStream in 3.8 not being able to open on an image (.png).
However if one reverts FileStream class>>concreteStream to StandardFileStream then the FileList cannot be used to open files as StandardFileStream does not implement #converter: and friends.
This is a critical bug.
Where are you noticing it?
I can, for instance, open PNGs from the FileList.
If you're reading from a stream of your own, you should call
(some stream) converter: Latin1TextConverter new
to kill off the text conversion.
Yes, this is a pain.
Have you looked for my various changes regarding this?
I have recommended that we have a distinct set of open methods that do this:
readOnlyBinaryFileNamed: oldBinaryFileNamed: newBinaryFileNamed:
etc.
Hi,
On Wednesday 02 February 2005 1:46 am, Brent Pinkney wrote:
I have submitted some problems with MultiByteFileStream in 3.8 not being able to open on an image (.png).
However if one reverts FileStream class>>concreteStream to StandardFileStream then the FileList cannot be used to open files as StandardFileStream does not implement #converter: and friends.
This is a critical bug.
Where are you noticing it?
I can, for instance, open PNGs from the FileList. If you're reading from a stream of your own, you should call (some stream) converter: Latin1TextConverter new to kill off the text conversion. Yes, this is a pain. Have you looked for my various changes regarding this? I have recommended that we have a distinct set of open methods that do this: readOnlyBinaryFileNamed: oldBinaryFileNamed: newBinaryFileNamed:
etc.
I am noticing this if I set up Comanche to serve static pages and then try open a .png in a browser.
Brent
Brent,
I am noticing this if I set up Comanche to serve static pages and then try open a .png in a browser.
In what browser?
The binary/text distinction is more important in 3.8 than previous versions. PNG file is a binary data, therefore any attempt to read the file as text potentially screw things up. Sending #binary to the file stream at right timings is the way to go. (changing its converter is not necessary.)
Ned's new protocols are good, too.
-- Yoshiki
squeak-dev@lists.squeakfoundation.org