From: Benny M. <ben...@gm...> - 2008-01-23 15:21:26
|
Looks nice too. A pedigree is however pretty too. I'm not worried about how the html looks if the page looks ok. Looking at eg http://genealogy.finlayfamily.org/pedigree.php, I do not think semantic markup is a design tool there... Note that you will only have pictures for people after 1900 or so, and before you only have perhaps scanned in documents, so to make a pedigree depend too much on pictures is not such a good choice (in my opinion). Benny 2008/1/23, Jason Simanek <jsi...@gm...>: > > Everybody, > > I haven't fixed up yesterday's CSS file yet, but I did come up with what > I think is a more elegant solution for the Ancestor Tree. Yesterday some > printing problems of the current tree came up. After looking into it, I > realized how clever, but crude the existing Ancestor Tree was > structured. Yes, it uses divs and styles, but it's got a lot of > meaningless markup included to create the boxes, borders and shadows > that could be avoided. > > My solution is to structure the ancestor tree as an ordered list with > nested ordered lists. It's very straight forward. Styling it can be > tricky, but now the entire presentation can be altered with CSS alone. > It's very printer friendly, especially considering specific print styles > as we discussed yesterday. > > It is also a more appropriate and semantic markup. If you turn off > styles with the current tree all you get is a list of names with no > indication to their relationship to one another. > > http://bohemianalps.com/dev-GRAMPS/Ancestor.html > > As usual, let me know what you think. > > -Jason > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |