--- a/Image.st Thu Aug 24 17:56:07 2017 +0200
+++ b/Image.st Thu Aug 24 17:58:06 2017 +0200
@@ -54,7 +54,7 @@
but may be associated to a device (i.e. getting a device-specific version of it).
The data held keeps all information which was originally present,
even if the display-device has lower resolution.
- Therefore, it is possible to process and manipulate images without loosing
+ Therefore, it is possible to process and manipulate images without losing
color information.
Images may be created manually (by providing a pixel array),
@@ -73,10 +73,10 @@
'monochromeOn:aDevice'.
As this class is very old and originated at times when typical graphic diplays only
- supported a limited number of colors (16 or 256), or where even monochrome b&w or grayscale
+ supported a limited number of colors (16 or 256), or were even monochrome b&w or grayscale
(NeXTCube or 4-plane NeXTStation).
- You will find a lot of code which deals with color allocation optimizations and dithering.
- Nowadays, these are hardly ever needed, and most of the time,
+ You will find a lot of code which deals with color allocation optimizations and dithering.
+ Nowadays, these are hardly ever needed, and most of the time,
images will be converted to 24bit (8x8x8) or 16bit (5x5x6) truecolor, when converted to a device representation.
(see examples_dithering for this old code in action)
@@ -86,8 +86,8 @@
(and using specialized colorMaps for b&w / greyScale images).
This may change in future versions for more application compatibility.
- To convert pictures from/to external file-formats, image readers are used
- which have the file-format knowledge built in.
+ To convert pictures from/to external file formats, image readers are used
+ which have the file format knowledge built in.
There are readers for most common formats available
(see ImageReader and especially subclasses such as TIFFReader, GIFReader etc.).
@@ -111,7 +111,7 @@
Much more work is needed if you plan to do heavy image processing and will
(may) be done in the future if there is a demand for it ...
- Dithering (read sectin above) can be controlled by the DitherAlgorithm classVariable:
+ Dithering (read section above) can be controlled by the DitherAlgorithm classVariable:
DitherAlgorithm:
@@ -128,8 +128,8 @@
Notice:
the set of attributes and the way they are stored originated initially
- from the need to represent tiff images.
- These turned out to use a relatively large set of atributes,
+ from the need to represent tiff images.
+ These turned out to use a relatively large set of attributes,
of which many are unused in other image formats. (so it was sufficient).
Later, some VisualWorks compatibility protocol was added (mapped palettes, for
example), and some stuff could well be redefined in simpler ways.
@@ -156,10 +156,10 @@
device using standard colors.
monoDeviceForm <Form> the device form which gives a monochrome
- aproximation of the image on device.
+ approximation of the image on device.
fullColorDeviceForm <Form> the device form which gives the best
- possible aproximation of the image on
+ possible approximation of the image on
device using private colors.
(not yet implemented)
@@ -184,7 +184,7 @@
bitsPerPixel obsolete - not used in ST/X (kept for a while for subclasses)
depth - these have been added in instVar-slots
maxPixelValue - according to the ST-80's image class.
- rowByteSize - to allow loading of st-80 images
+ rowByteSize - to allow loading of ST-80 images
- (which are stored as instVarAt:put: expressions)
[class variables:]