Hi Charles, There's no *easy* answer, unfortunately. Here's how I'd do it. 1. Get an *idea* of how you'd like it to be arranged, IF possible to do. But.... 2. Wait to get the CD before finalizing your plan. 3. Visit the Fayette Co PAGenWeb -- they have a large cemetery photo database. See if you like their design. If you do, Click View Source and save it as a TXT file. 4. When you get the CD, browse through them in the Details view of Windows Explorer - gives size. As you browse, note if you'll have to crop sides and bottom BEFORE deciding on a uniform size. 5. I'd arrange by -- Cemetery first ---By Surname second (By date or by cemetery row is just too hard). 6. Copy all the pics to a backup drive. Work on them on the backup drive. Do all cropping first--- keep in mind what size you want for all photos. 7. Decide on a uniform width x height and begin revising each photo to that size. At the end of each filename put something like _d for "done" OR move each to a "done re-sizing" folder. 8. Decide how many you want per folder. Move sets into separate folders. 9. Make thumbnails using EasyThumbnails free program. Make sure to do a test on 1 photo. use the settings tab to set your height and width for thumb size 10 decide how many thumbs you can put on a horizontal line... make your table for all the "A" names... 1 for "B" names, etc. On some alphabet letters (C, L, M, Mc, R, S, T, V, W) you will likely need several pages (s_names_1.html and keep numbering each till the last one) 11. Make 1 html page of thumbnails. 12. Label each thumbnail. 13. Go back to the large photos. Decide how you want to present them. It is MUCH harder to do one html page for each larger photo. It is much EASIER to just link a thumbnail directly to its corresponding big picture, without it being on a web page (not one you make). But you won't be able to add a title under the picture. So if you have photoshop, you could add text to each photo, like maybe the cemetery name? Or a copyright and phototaker name? Visitors will see the deceased's info on the tombstone. A pic without an html page just opens on a white rootsweb page. 15. If you do the pic-no page route, just link each thumb to its bigger picture. 16. upload after doing 1 folder of pics-- makes it easier and faster to upload. 17. If you don't want others to have access to a folder of pics (as a directory only), put an index.htm page in that folder. On the page, just have navigation back to the site's main page AND the A-B-C-D navigation to the cemetery photos, or at least to the cemetery/index.htm (the main index page for the whole project) 18. I forgot, do a navigation table of A, B, C, D for each surname letter. If one letter has 2 pages, llink to a "Main page for the Letter A" for example. But instead of a "page" for this table, put it in an _include. Much easier to link to one _include, rather than have to manually put the nav table on every page. Other people might do it differently. I've never found an easy way to do a huge pic project. Take it one section at a time. And, good luck-- you'll be working for many months. Judy PS I use Frontpage too. On Fri, Jan 1, 2010 at 4:10 PM, Charles Barnum <jcnreno@charter.net> wrote: > Good New Year to you All, > Cemetery Survey: > A lady is sending me 500 headstone photos on disk and sending me the > names in a special format I asked her to use. > Name; date one; date two; comments. > I usually convert that to a table in MS Word using the ";" as the column > separator. (The lady does not have Excel.) Then, I usually convert that > to Excel and then decide if I want a table or <pre> text form for the > web page. However, I have discovered a way to convert a Word file > directly into a <pre> format for using Expression Web 3. (Expression Web > 3 is a glorified program of FrontPage that has massive flaws when it > comes to tables.) > What is the best way to display a 500 name cemetery file with linked > photos? How do you do it? I use EW3 but often fall back to using > FrontPage because it is easier to use and does not crash like EW3 does. > > Happy New Year, all is well that ends well. > Charles

On behalf of other dial-up users can I ask -- what's wrong with a table that has only three columns -- the NAME of the deceased (as a link to the full photo), birth-date, and death-date. That way, if I-the-user want to see all 500 of 'em I can, but if I only want the Zickaman entry, I don't /have/ to wait for the other 499 thumnails to load. And incidentially, Charles-the-webmaster doesn't have to spend time resizing photos, d/l a new program and figuring out how to use it. Even working on local, off your HD, pulling up and displaying 40 or 50 thumbnails takes a measurable length of time. I get more and more discouraged browsing even the GenWeb these days, as more and more webmasters lean to fancier and more elaborate displays of less and less data. For myself and others I know, so long as the data is presented coherently and legibly, what color the background is, or which image is used for the background on the side-bar is a matter of indifference. There's a site I use fairly often that insists on using a beige calico print as background, thus causing every 3rd or 4th letter of the text to vanish. Cheryl J.A. Florian wrote: > Hi Charles, > > There's no *easy* answer, unfortunately. > > Here's how I'd do it. > > 1. Get an *idea* of how you'd like it to be arranged, IF possible to do. > But.... > 2. Wait to get the CD before finalizing your plan. > 3. Visit the Fayette Co PAGenWeb -- they have a large cemetery photo > database. See if you like their design. > If you do, Click View Source and save it as a TXT file. > 4. When you get the CD, browse through them in the Details view of Windows > Explorer - gives size. > As you browse, note if you'll have to crop sides and bottom BEFORE deciding > on a uniform size. > 5. I'd arrange by > -- Cemetery first > ---By Surname second > (By date or by cemetery row is just too hard). > 6. Copy all the pics to a backup drive. Work on them on the backup drive. > Do all cropping first--- keep in mind what size you want for all photos. > 7. Decide on a uniform width x height and begin revising each photo to that > size. At the end of each filename put something like _d for "done" OR move > each to a "done re-sizing" folder. > 8. Decide how many you want per folder. Move sets into separate folders. > 9. Make thumbnails using EasyThumbnails free program. Make sure to do a > test on 1 photo. use the settings tab to set your height and width for > thumb size > 10 decide how many thumbs you can put on a horizontal line... make your > table for all the "A" names... 1 for "B" names, etc. On some alphabet > letters (C, L, M, Mc, R, S, T, V, W) you will likely need several pages > (s_names_1.html and keep numbering each till the last one) > 11. Make 1 html page of thumbnails. > 12. Label each thumbnail. > 13. Go back to the large photos. Decide how you want to present them. It > is MUCH harder to do one html page for each larger photo. > It is much EASIER to just link a thumbnail directly to its corresponding big > picture, without it being on a web page (not one you make). But you won't > be able to add a title under the picture. So if you have photoshop, you > could add text to each photo, like maybe the cemetery name? Or a copyright > and phototaker name? Visitors will see the deceased's info on the > tombstone. A pic without an html page just opens on a white rootsweb page. > 15. If you do the pic-no page route, just link each thumb to its bigger > picture. > 16. upload after doing 1 folder of pics-- makes it easier and faster to > upload. > 17. If you don't want others to have access to a folder of pics (as a > directory only), put an index.htm page in that folder. On the page, just > have navigation back to the site's main page AND the A-B-C-D navigation to > the cemetery photos, or at least to the cemetery/index.htm (the main index > page for the whole project) > 18. I forgot, do a navigation table of A, B, C, D for each surname letter. > If one letter has 2 pages, llink to a "Main page for the Letter A" for > example. But instead of a "page" for this table, put it in an _include. > Much easier to link to one _include, rather than have to manually put the > nav table on every page. > > Other people might do it differently. I've never found an easy way to do a > huge pic project. Take it one section at a time. And, good luck-- you'll > be working for many months. > > Judy > PS I use Frontpage too. > > > > > On Fri, Jan 1, 2010 at 4:10 PM, Charles Barnum <jcnreno@charter.net> wrote: > > >>Good New Year to you All, >>Cemetery Survey: >>A lady is sending me 500 headstone photos on disk and sending me the >>names in a special format I asked her to use. >>Name; date one; date two; comments. >>I usually convert that to a table in MS Word using the ";" as the column >>separator. (The lady does not have Excel.) Then, I usually convert that >>to Excel and then decide if I want a table or <pre> text form for the >>web page. However, I have discovered a way to convert a Word file >>directly into a <pre> format for using Expression Web 3. (Expression Web >>3 is a glorified program of FrontPage that has massive flaws when it >>comes to tables.) >>What is the best way to display a 500 name cemetery file with linked >>photos? How do you do it? I use EW3 but often fall back to using >>FrontPage because it is easier to use and does not crash like EW3 does. >> >>Happy New Year, all is well that ends well. >>Charles

Hi Cheryl, I agree with your thoughts on this subject. Here is a cemetery selected at random from my RW site. http://www.rootsweb.ancestry.com/~nma/catron/seventhday_adventist.html When I first started putting cemetery photos online, I used thumbnails because that was the rave at the time. I dropped that long ago. I now have one photo per headstone not two--a thumbnail plus the regular photo. I originally thought exactly like you, three columns or even one liked to the photo is suffuicuent. The problem I ran into was most submitters want all of their work placed online. I understand that. So, I place online everything they send to me, name date and added headstone information, like military or other info. Some submitters even get into who the deceased married and their children. So I add that to a column too. As for resizing, I have two programs for that. Also a program to rename photos. I used to crop all photos but that also irritates some submitters. They do not like their beautiful photos cropped. So I normally resize too 500 or 488 pixels wide and go from there. About dial up users. I struggled with that for a long time. I finally decided I could do little to help them other than to reduce the size of the photos, and not use thumbnails. I also use extremely simple web pages. In my recent converting to xhtml using EW3, I eliminated all stuff that was window dressing. The fanciest thing I have is the BG color <body style="background-color: #FFFFCC"> *Your observation, "I get more and more discouraged browsing even the GenWeb these days, as more and more webmasters lean to fancier and more elaborate displays of less and less data." Goodness, I agree with you 100%. We should be about data and not show. But alas, I know many people are in love with the code and the wonderful layout. I am not. The fanciest page on my site is the main page, *http://www.rootsweb.ancestry.com/~nma/index.htm. But even there, I tried to simplify it as much as possible and still remain competitive with genweb.( I use no BG images. They increase load time and server space.) Also, this site on RW loads very fast. I recently switched from 1and1 to directNic for my other site for better speed; but RW is about three times faster than directNic. When I upload photos to RW I can load three in about the same time it takes to upload one on my other server. RW has always been faster than any other server I've used. I'm truly sorry about not being more sensitive about dial up users, but there are practical limits what I can do. Charles On behalf of other dial-up users can I ask -- > what's wrong with a table that has only three columns -- the > NAME of the deceased (as a link to the full photo), > birth-date, and death-date. That way, if I-the-user want to > see all 500 of 'em I can, but if I only want the Zickaman > entry, I don't /have/ to wait for the other 499 thumnails to > load. And incidentially, Charles-the-webmaster doesn't have > to spend time resizing photos, d/l a new program and > figuring out how to use it. > > Even working on local, off your HD, pulling up and > displaying 40 or 50 thumbnails takes a measurable length of > time. > > I get more and more discouraged browsing even the GenWeb > these days, as more and more webmasters lean to fancier and > more elaborate displays of less and less data. For myself > and others I know, so long as the data is presented > coherently and legibly, what color the background is, or > which image is used for the background on the side-bar is a > matter of indifference. There's a site I use fairly often > that insists on using a beige calico print as background, > thus causing every 3rd or 4th letter of the text to vanish. > > Cheryl > > > > > J.A. Florian wrote: > >> Hi Charles, >> >> There's no *easy* answer, unfortunately. >> >> Here's how I'd do it. >> >> 1. Get an *idea* of how you'd like it to be arranged, IF possible to do. >> But.... >> 2. Wait to get the CD before finalizing your plan. >> 3. Visit the Fayette Co PAGenWeb -- they have a large cemetery photo >> database. See if you like their design. >> If you do, Click View Source and save it as a TXT file. >> 4. When you get the CD, browse through them in the Details view of Windows >> Explorer - gives size. >> As you browse, note if you'll have to crop sides and bottom BEFORE deciding >> on a uniform size. >> 5. I'd arrange by >> -- Cemetery first >> ---By Surname second >> (By date or by cemetery row is just too hard). >> 6. Copy all the pics to a backup drive. Work on them on the backup drive. >> Do all cropping first--- keep in mind what size you want for all photos. >> 7. Decide on a uniform width x height and begin revising each photo to that >> size. At the end of each filename put something like _d for "done" OR move >> each to a "done re-sizing" folder. >> 8. Decide how many you want per folder. Move sets into separate folders. >> 9. Make thumbnails using EasyThumbnails free program. Make sure to do a >> test on 1 photo. use the settings tab to set your height and width for >> thumb size >> 10 decide how many thumbs you can put on a horizontal line... make your >> table for all the "A" names... 1 for "B" names, etc. On some alphabet >> letters (C, L, M, Mc, R, S, T, V, W) you will likely need several pages >> (s_names_1.html and keep numbering each till the last one) >> 11. Make 1 html page of thumbnails. >> 12. Label each thumbnail. >> 13. Go back to the large photos. Decide how you want to present them. It >> is MUCH harder to do one html page for each larger photo. >> It is much EASIER to just link a thumbnail directly to its corresponding big >> picture, without it being on a web page (not one you make). But you won't >> be able to add a title under the picture. So if you have photoshop, you >> could add text to each photo, like maybe the cemetery name? Or a copyright >> and phototaker name? Visitors will see the deceased's info on the >> tombstone. A pic without an html page just opens on a white rootsweb page. >> 15. If you do the pic-no page route, just link each thumb to its bigger >> picture. >> 16. upload after doing 1 folder of pics-- makes it easier and faster to >> upload. >> 17. If you don't want others to have access to a folder of pics (as a >> directory only), put an index.htm page in that folder. On the page, just >> have navigation back to the site's main page AND the A-B-C-D navigation to >> the cemetery photos, or at least to the cemetery/index.htm (the main index >> page for the whole project) >> 18. I forgot, do a navigation table of A, B, C, D for each surname letter. >> If one letter has 2 pages, llink to a "Main page for the Letter A" for >> example. But instead of a "page" for this table, put it in an _include. >> Much easier to link to one _include, rather than have to manually put the >> nav table on every page. >> >> Other people might do it differently. I've never found an easy way to do a >> huge pic project. Take it one section at a time. And, good luck-- you'll >> be working for many months. >> >> Judy >> PS I use Frontpage too. >> >> >> >> >> On Fri, Jan 1, 2010 at 4:10 PM, Charles Barnum <jcnreno@charter.net> wrote: >> >> >> >>> Good New Year to you All, >>> Cemetery Survey: >>> A lady is sending me 500 headstone photos on disk and sending me the >>> names in a special format I asked her to use. >>> Name; date one; date two; comments. >>> I usually convert that to a table in MS Word using the ";" as the column >>> separator. (The lady does not have Excel.) Then, I usually convert that >>> to Excel and then decide if I want a table or <pre> text form for the >>> web page. However, I have discovered a way to convert a Word file >>> directly into a <pre> format for using Expression Web 3. (Expression Web >>> 3 is a glorified program of FrontPage that has massive flaws when it >>> comes to tables.) >>> What is the best way to display a 500 name cemetery file with linked >>> photos? How do you do it? I use EW3 but often fall back to using >>> FrontPage because it is easier to use and does not crash like EW3 does. >>> >>> Happy New Year, all is well that ends well. >>> Charles >>> > > > > > > > ------------------------------- > To unsubscribe from the list, please send an email to ROOTSWEB-HELP-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 9.0.725 / Virus Database: 270.14.124/2597 - Release Date: 01/02/10 00:22:00 > >

At 11:03 AM 1/3/2010, you wrote: >On behalf of other dial-up users can I ask -- > >what's wrong with a table that has only three columns -- the >NAME of the deceased (as a link to the full photo), >birth-date, and death-date. That way, if I-the-user want to >see all 500 of 'em I can, but if I only want the Zickaman >entry, I don't /have/ to wait for the other 499 thumnails to >load. And incidentially, Charles-the-webmaster doesn't have >to spend time resizing photos, d/l a new program and >figuring out how to use it. Nothing at all wrong with it and I think many website designers especially those who work with genealogy often forget that. One way of doing it is http://dewitt.ilgenweb.net/halsey-hougham-cemetery.htm but this page has no links to photos although it would be easy enough to do Depending on the number of names you could use a table or a list. And the miniature tombstone that is used instead of a circle or square is styled with the style sheet and not inserted for each entry. pat Pat Geary Expression Web Xmas/NY Giveaway 23rd Dec - 15th Jan http://www.frontpage-to-expression.com/expression-web-giveaway.html EW Christmas Template Gift http://www.expression-web-tutorials.com/christmas/

Cheryl, What I had suggested was to break up the 500 files to church, then surname. Each letter should have an index page to browse. I also said if there were many photos per letter, then to add more pages per surname. I never suggested --nor did anyone else suggest-- placing 500 thumbnails on one page. Any large number can't be put on one page, even if it is just a list with a link. So I always use the A, B or A-B break-down to split up the volume. I do understand the frustrations of dial-up users. I was on dial-up until just a few years ago. Judy On Sun, Jan 3, 2010 at 11:03 AM, singhals <singhals@erols.com> wrote: > On behalf of other dial-up users can I ask -- > > what's wrong with a table that has only three columns -- the > NAME of the deceased (as a link to the full photo), > birth-date, and death-date. That way, if I-the-user want to > see all 500 of 'em I can, but if I only want the Zickaman > entry, I don't /have/ to wait for the other 499 thumnails to > load. And incidentially, Charles-the-webmaster doesn't have > to spend time resizing photos, d/l a new program and > figuring out how to use it. > > Even working on local, off your HD, pulling up and > displaying 40 or 50 thumbnails takes a measurable length of > time. > > I get more and more discouraged browsing even the GenWeb > these days, as more and more webmasters lean to fancier and > more elaborate displays of less and less data. For myself > and others I know, so long as the data is presented > coherently and legibly, what color the background is, or > which image is used for the background on the side-bar is a > matter of indifference. There's a site I use fairly often > that insists on using a beige calico print as background, > thus causing every 3rd or 4th letter of the text to vanish. >