I have adopted the convention of always putting the modification date and time near the top of each page. This can be seen directory above this page. The date/time is usually the first thing changed on each page and sometimes the last thing updated. The problem that I have been trying to fix is that when I see a file, from my ISP, I can not be sure that it is the most recent page. My computer, and my tablet, both like to keep data in local cache and often these are old and inaccurate data.
I have made an effort to indicate when files are in
JPG format. The reason that I have made an effort to indicate
JPG encoded files load reasonably quickly.
I used two, or three, sizes of picture data in the main document. These were:
6,733 KBfor E1 and
6,454 KBfor E11. Note how bad the merge process was. When I can get better merge software I'll give it a try. I used the
InfanView. Clicking on the
mergepictures will not bring up a more individual detailed views.
I have reduced the file size of each image to make the loading as fast as possible. I used the
InfanView program to do this. The source picture files are called fullsize files.
InfanView program involves selecting the
Batch Conversion/Rename.. option in the
File menu line.
InfanView compresses images as much as I am doing here the resultant image has many artifacts that are just plain wrong. The colors are messed up, but the overall shape is correct. When a "correct" version of an image is desired, it may be displayed by clicking on it.
As a test I made the medium size for pictures. I used a maximum file size of 200.00 Kb per picture.
InfanView to use a maximum of 60.00 Kb per image when I generated the smaller picture files. These are usually considered to be the "thumbnail" pictures. For unknown reasons
InfanView sometimes creates files that are larger that requested.
For example data I used
InfanView with a maximum size of 200.00 Kb per image. These are called the medium pictures. None of these are in the final document.
I have two "typical" saw files here for use as examples. The first is
E1 which is a typical one man bucking saw which is about 4 feet long. The second is
E11 a typical two man bucking saw which is about 5 feet, 6 inches long.
Something that interests me is "How long does it take to download and display a set of pictures?" Here to help find out what the durations are with the pictures compressed by differed factors, I have compressed them three times, always starting with the original file (fullsize). I then used MS-DOS to print out the file sizes of each picture in a file set. Note that the files in fullsize are the largest of each file set and the file dates on the individual pictures are significantly different. This is because I had to rotate one of the pictures and when it was rewritten its date/time tag changed but its name did not change. For the pictures in the other file sets each picture file has the approximate same date/time stamp due to being generated by the
InfanView program in the same batch operation.
If the calls to the different file sets are selected, note the time that it takes before the full set of pictures is displayed. Since the smaller picture set loads the fastest it is the default when a file set is displayed. Behind each smaller picture there is a fullsize picture of the same image. Thus if something of interest is noted on the smaller picture a fullsize version of the picture may be immediately displayed by "clicking" on the smaller displayed version.
I want to make "merged" versions of the pictures, however the only program that I have that will make a "merged" image is
InfanView and its results are poor.
Files used with fullsize size saw E1 pictures
fullsize pictures of E1
fullsize merged picture of E1
Files used with medium size saw E1 pictures
medium pictures of E1
Files used with smaller size saw E1 pictures
smaller pictures of E1
Files used with fullsize size saw E11 pictures
fullsize pictures of E11
fullsize merged picture of E11
Files used with medium size saw E11 pictures
medium pictures of E11
Files used with smaller size saw E11 pictures
smaller pictures of E11
As of "11:16 AM 7/31/2022" the "Properties" of the "inventory" tree is:
And at the same time the entire "0 SawDataBase" file system is like this:
Please note that the full set of files is frequently updated and its file count and size changes on an unknown/unpredictable/unplanned rate.
The "standard" method of displaying almost any of the pictures is by using minor variations on this code fragment:
The most common changes involve the
filename being displayed and the
width fields. Since almost all the photos were taken with the same cell phone, normally only the
filename changes. The pictures in the older CD series of images were taken with several different cameras and the arguments for displaying the images changes on an as needed basis.
When a photo will be displayed in portrait mode instead of landscape mode the
rect coords field values are usually swapped.
Note that the
filename is the same in both the
The typical tree, produced with the MSDOS
tree /a command, is like this for the saw data section:
A semi-full directory tree as of 10:17 AM 8/1/2022 is quite long changes, usually additions are common. After deleting subsections about the HSVTC and other parts that are not a direct part of the
SawDataBase.com site. The full tree is quite long and I have dumped the redundant parts of it. The reduced list is about 150, or so, lines long. Even after the deletions, it is too long to include here.
A reduced version of the tree set is in two parts:
First level directories
Second level directories
For almost all pictures here I used one of my two Samsung S10e 128 GB cell phone named CELL 6. The other identical one is named Cell 5 which I only used for a few pictures. For all of these pictures, if they are clicked on will result in a large clearer picture.
Current (9:54 AM 9/24/2022) problem is that I can not get from "
SawDetails/Handles/2 Stud Connector" to "
SawTools/Handles/HC48.html" or "
SawTools/Handles/HC49.html" from my ISP, but both calls work from Windows.
Fix for the above problem
Note: Under windows the triple slash "
///" does not work as an address, but it is required for working with my ISP. Thus I am using single slashes "
/" for Windows and triple slashes "
///" for the ISP. Happy debugging! (11:02 AM 10/5/2022).
Stack Exchange was not helpful in getting this information.
As a result of this problem of cross tree links, and the fact that I have developed this web site under Windows, I have had to generate two sets of calls.
This message means that the referenced HTML file is not found. Note that it does not indicate the file that requested the HTML file.
Missing HTML file.