Talk:Nematode/Archive 1

Archive 1

I think the left-aligned image is a bad idea, it means that the actual text is squished into the middle rather than starting at the top-left as is typical. I think that if the picture is going to placed beside the text, it should go on the right, beneath the classification, so for the moment I've incorporated it into the table. This increases the width throughout, which may or may not be ok, but I don't know of any easy way to place one table beneath another.

One thing which occurs to me: thanks to the one vertical divider, I've had to say colspan="2" for nearly every cell in the table. If we like the extended table, then, or if we think we might ever want to extend it for something else, I think we should get rid of the divider. --Josh Grosse

Fair enough -- it would be squished on low res screens. I like the idea of having the image in the table itself -- so long as it is not below the list of children (sometimes this list can be very long). The width of this particular image isn't that big of a deal, but some other images would have to be downsized and a link provided to the larger image. Also, as I said in talk:Hominid, the table isn't 100 percent done yet -- my table powers have been exhuasted on it and I have differed the matter to user:Bryan Derksen who is the resident table expert. I too want a table that does what we want while still being easy to code. You are right, having to state colspan=2 all over tthe place isn't a great solution. But then having to use hard spaces everywhere isn't too elegant either. --maveric149, Saturday, July 13, 2002

Well, potentially there could be many images too, and if the classification is excessive the table may not be the best format anyways, but I wouldn't worry too much. It occurs to me now: one possible way to do the divider without affecting other cells would be nesting tables, and that sort of approach would add flexibility to any other entries made later on, though it wouldn't be helping simplicity. Bryan may indeed have a better idea.--Josh Grosse

I say put a table inside a table cell. That'll get rid of the divider (or put horizontal dividers if you make the inner table have a border) while still keeping KPCOFG neatly aligned. -phma

Yep, that's what I asked Bryan to do -- I simply don't know how to have a table with a nested table in the first cell. (Of course, the nested table would not have any border so the verticle line would not be visible. The children part of the this table is about as simple as it probably is going to get. The br tags are now in front of the hard spaces -- this will make conversion of current children lists as easy as a find and replace. --maveric149