On Wed, 07 Mar 2001 00:31:09 -0500, Glenn McCorkle wrote:

> On Mon, 05 Mar 2001 21:53:26 -0500, Clarence Verge wrote:

>> L.D. Best wrote:

>>> Hey fellahs!!!!

>>> I need a definition of what you mean by "resize!"

>>> If you mean it can be made to fit the dimensions put into an html page,
>>> then my response is   Duhhhhhhhhhhhhhh, George!

>> Duuuuuuuh Nancy, wut duz that mean ?

>>> If you mean Arachne itself can take a 640x200 bmp and turn it into a
>>> 310x100 bmp that we can save at the new size, then tell us just HOW NL
>>> it is done!

>> Seems that:
>> <IMG SRC="file://strobo.gif" WIDTH=320 HEIGHT=240>
>> works to re-size .GIFs (as announced) where the nums are pixels and
>> you can use any nums you want pretty much. <G>

>> Seems also that you can specify .BMPs, .JPGS and .ZBMs the same way for
>> image sources cuz what she resizes is the final .BMP anyway. :-S~

> Just so there's no confusion on this point.

> This bit of code simply determines the size of the display area set-aside
> for that image.
> <IMG SRC="file://strobo.gif" WIDTH=320 HEIGHT=240>

> If the width and height are not specified. Arachne uses the width and
> height from inside the file itself.

> No alterations are done to the file.

Hmmmm.
I don't understand why anyone would think there might be something
done to the file.

And that bit of code results in MUCH more than just setting aside space
for the image. If it was THAT simple, then the requirement that it fit a
"window" is satisfied if you just show the upper left 1/4 of it.

But instead, Arachne PROCESSES the image by throwing away certain pixels
(for downsizing) or duplicating certain pixels (for upsizing) and then
puts ONLY the selected pixels in the "window" - effectively resizing
the image as shown on the screen. I think this is pretty easy to grasp.

You just have to remember that a pixel is a pixel and you CANNOT change
a pixel's size without switching video modes. (640x480 --> 800x600) 
So the ONLY option is to drop/add FULL pixels - or averaged values for 
full pixels if one spends more processor time on it than Arachne does.

The resultant bitmap in video memory is a resized image, occupying no
more data space than necessary and in the above example, that's 1/4 of 
the data space of the original file. 
The only thing missing is our ability to save ONLY THAT PORTION of the
video memory.


- Clarence Verge
- Still using Arachne V1.62 ....

Reply via email to