Gordon,
Given the little glitches in Legacy's webpages, in particular the Pedigree
format, both tedious and very time-consuming. However, after producing the
webpages with several gen-apps, I must say that Legacy's are as good or
perhaps better than any of the others. As you've probably seen on my
http://zelltree.com, it's presently used to present my gen-data in several
formats, but it's all getting to be too much work and, for various reasons,
I'm now going to "lean out" the website and use only one gen-data-format,
which will probably be Legacy's Pedigree format. Because of eternal data
transfer problems with GEDCOM, I gave up long ago trying to use anything but
Legacy. So when I request that Legacy clean up it's html code to allow
borders and remove other little glitches, there's good reason.
The first step, of course, is getting good (satisfactory to you) Legacy
webpage output. If I fumble during the output, it is far faster and better
to do it over again (and again) until one gets the Legacy output as
satisfactory as possible. Yes, it takes some time, but is much faster that
reprocessing later.
I'm old, failing memory, and absolutely not a programmer, so writing html is
not for me. I've been doing websites/webpages for years, and Frontpage is
the only app I've ever been able to grasp and utilize. M$ managed to screw
up Frontpage thru several versions but finally has it halfway right with
FP2003. While reprocessing webpages using FP does work, but it's horribly
slow, often taking an hour or more on any process which involves rewriting
all my now-4200-plus Pedigree webpages.
The reprocessing involves several steps:
* Each time Legacy outputs a new data-set to my zelltree/pedigrees/ folder,
Frontpage will then need several hours to load/open. Meanwhile I guess it's
reprocessing everything, but that's hardly complete. I don't use Frontpage
Server Extensions anymore, nor have I attempted to migrate to it's
Sharepoint Services, which I assume (not certain) has replaced FPSE.
* RE-Applying a theme to set colors, fonts, backgrounds, borders, etc etc.
* RE-Adding borders, which contain icons and links to many other internal
URLS, and gives uniformity to my website. As my website's left border
contains the bulk of those links, it becomes a real problem when the Legacy
output becomes screwed up just because of adding a left border, so this is a
priority item on my Legacy WishList! As things stand at present, I forgo
using my standard left border because of this. Perhaps on this thread we'll
discover how to correct this, then hand Millennia the solution and ask them
to fix their programming on html output. It's strange that this occurs only
on Legacy's Pedigree output format!
* At last one gets to spend the usual hours checking the new set of
webpages, and fine-tuning.
* Finally it's time to republish, which Frontpage does very nicely now.
Frontpage has a search/replace tool which can (usually) be used to
mass-rewrite segments of the html to all pages (provided it's unique, of
course!). While that does require more processing time, it's not difficult.
My point here is that such would be unnecessary if the Legacy output were
correct in the first place.
The entire process takes 2-3 days, and most of that isn't what I call fun.
Thus everything that can be done within Legacy will help speed the process
and ease the pain. However, I'm just glad that gen-apps have evolved to
producing webpages, which must always be "secondary" to it's basic task of
being a database designed to contain, preserve and view our genealogies.
I would personally prefer that Legacy (or any other gen-app, to which I
would switch in a heartbeat) be a true database using standard database
formats, tools and outputs, but enhanced for genealogy-specific needs such
as *est* dates and the many other good abilities within Legacy. This could
simply be uploaded to a website and presented on webpages showing data
extracted from the database (e.g. phpGedview, but avoiding GEDCOM). It
could also be maintained and/or posted online, avoiding an upload of
thousands of webpages merely to update only as little as a single word! But
I would suppose that today it is once again "all about marketing", huh?
RonKZ
----- Original Message -----
From: "Gordon Small" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, 26 May, 2005 09:33
Subject: Re: [LegacyUG] Pedigree webpages.
Ron, I'm very interested in this discussion because I am thinking of doing
a
complete redesign of my site using the software suggestions on your site
as
a guide. So I have a couple questions.
After you create the Legacy pages, do you have to manually go back and
edit
each one? Or, is this just something that can be ignored until it's fixed
in
Legacy?
If the pages have to be edited, how do you do thousands of pages? I
figure
you must have a way.
Gordon
----- Original Message -----
From: "Ron Ferguson" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, May 26, 2005 9:23 AM
Subject: Re: [LegacyUG] Pedigree webpages.
Hi Ron,
Very sorry but I made two errors in my last email. As you may have noticed
form my code in my suggestions 1) and 2) the <./tr>m should be replaced by
<.table> and *not* <./table>
Ron Ferguson
____________________________________
For Genealogy, Software and Social visit:
http://myweb.tiscali.co.uk/fergys/
----- Original Message -----
From: "Ron Klotz Zellhoefer" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: 26 May 2005 14:11
Subject: Re: [LegacyUG] Pedigree webpages.
Thank you, Ron
I have messed around with Legacy's html code in the past, but didn't
succeed with curing the problem of Legacy's webpages "coming apart" when
adding a *left* border using FP2003. I don't know how other web-apps
work, but FP2003 borders are not tables, altho' tables can be inserted
within the borders (and I do use such), so I'm not sure we're quite on
the
same wavelength with this, but I'll test your suggestion today and report
back.
I'll comment that your website looks good; particularly like what you've
done for your top border.
RonKZ
NM, USA
----- Original Message -----
From: "Ron Ferguson" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, 26 May, 2005 01:56
Subject: Re: [LegacyUG] Pedigree webpages.
Hi Ron,
There seems to be 3 main changes to the Legacy source code which need to
be made when it is wrapped in another table and from what you have
observed it also seems to apply in other circumstances.
These are difficult to identify in words but I will have a go working
from the bottom up!
1) Just above the line <.td width="590"......> and below the line
<./table> there is a <./tr>. This should be changed to <./table>
2) Moving up: Just above the line <.td width="580"......> and below the
line <./table> there is a <./tr>. This should be changed to <./table>
3) Between there and the arrows there are two lines:
<.tr>
<./tr>
Both should be deleted.
These changes have to be made on every page. I cannot promise that this
makes the code absolutely correct but at least it works for me. You can
have a look at the alterations on any pedigree page on my web site (cf.
with the Legacy code)
Ron Ferguson
Hello;
.
#3. After Legacy-outputting the pedigree webpages, I always run them
thru Frontpage in order to add my own custom borders. My website uses
borders top, left and bottom, and I find that something within the
Legacy html causes a real mess when one adds a left border. I've asked
before that Legacy modify it's html so that adding borders will not
trigger this problem, but never got a response, so that's my
WISHLIST#3.
I'm in the midst of a major update to my website, so there may be more
later. Thanks, LUG.
RonKZ
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.322 / Virus Database: 266.11.16 - Release Date: 24/05/2005
Legacy User Group Etiquette guidelines can be found at:
http://www.LegacyFamilyTree.com/Etiquette.asp
To find past messages, please go to our searchable archives at:
http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
To unsubscribe please visit:
http://www.legacyfamilytree.com/LegacyLists.asp
Legacy User Group Etiquette guidelines can be found at:
http://www.LegacyFamilyTree.com/Etiquette.asp
To find past messages, please go to our searchable archives at:
http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
To unsubscribe please visit:
http://www.legacyfamilytree.com/LegacyLists.asp
Legacy User Group Etiquette guidelines can be found at:
http://www.LegacyFamilyTree.com/Etiquette.asp
To find past messages, please go to our searchable archives at:
http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
To unsubscribe please visit:
http://www.legacyfamilytree.com/LegacyLists.asp
