Columns

[dreamsonthefly]

I have a newsletter that I would like to make two columns in. The letter is written in JS and I can not for the life of me figure out the columns. any advise?

Thanks so much.

this is what I have so far, but I want the We Provide and You learn on the same line, with the text for each under the title.

<MULTICOL COLS=2 GUTTER=20 WIDTH 75%>
<U>WE PROVIDE</U>
<LI TYPE=disc> Accommodations
<LI TYPE=disc>Meals
<LI TYPE=disc>Rods
<LI TYPE=disc>Reels
<LI TYPE=disc>All Flies
<LI TYPE=disc>Lines
<LI TYPE=disc>Leaders
<LI TYPE=disc>Tippet
<LI TYPE=disc>Float Tubes
<LI TYPE=disc>Fins, Waders & boots
<LI TYPE=disc>Nets
<LI TYPE=disc>Professional instruction
<MULTICOL COLS=2 GUTTER=20 WIDTH 75% aling="right">

<UL><UL><UL><UL><U> YOU LEARN</u><U> YOU LEARN</u>
<LI TYPE=disc>Fly Casting
<LI TYPE=disc>Knots
<LI TYPE=disc>Entomology
<LI TYPE=disc>Fly Selection
<LI TYPE=disc>Fish Species
<LI TYPE=disc>Tackle Selection
<LI TYPE=disc>Catch & Release
<LI TYPE=disc>Streamside Ethics
<LI TYPE=disc>Wading Safety
<LI TYPE=disc>Fly Tying
<LI TYPE=disc>Float Tube Fishing</MULCOL>

[Willy Duitt]

Hi Rhonda;

Tables are good to use for tabular data.

Try this:

<table align="center" cellpadding="5" cellspacing="15" border="0">
  <tr id="headerRow_1">
   <th><U>WE PROVIDE</U></th>
   <th><U>YOU LEARN</U></th>
 </tr id="headerRow_1Close">
  <tr id="listRow_1">
   <td id="listLeft_1" valign="top">
    <MULTICOL COLS=2>
     <LI TYPE=disc> Accommodations</LI>
     <LI TYPE=disc>Meals</LI>
     <LI TYPE=disc>Rods</LI>
     <LI TYPE=disc>Reels</LI>
     <LI TYPE=disc>All Flies</LI>
     <LI TYPE=disc>Lines</LI>
     <LI TYPE=disc>Leaders</LI>
     <LI TYPE=disc>Tippet</LI>
     <LI TYPE=disc>Float Tubes</LI>
     <LI TYPE=disc>Fins, Waders & boots</LI>
     <LI TYPE=disc>Nets</LI>
     <LI TYPE=disc>Professional instruction</LI>
    </MULCOL>
  </td id="listLeft_1Close">
   <td id="listRight_1" valign="top">
    <MULTICOL COLS=2>
     <LI TYPE=disc>Fly Casting</LI>
     <LI TYPE=disc>Knots</LI>
     <LI TYPE=disc>Entomology</LI>
     <LI TYPE=disc>Fly Selection</LI>
     <LI TYPE=disc>Fish Species</LI>
     <LI TYPE=disc>Tackle Selection</LI>
     <LI TYPE=disc>Catch & Release</LI>
     <LI TYPE=disc>Streamside Ethics</LI>
     <LI TYPE=disc>Wading Safety</LI>
     <LI TYPE=disc>Fly Tying</LI>
     <LI TYPE=disc>Float Tube Fishing</LI>
    </MULCOL>
  </td id="listRight_1Close">
 </tr id="listRow_1Close">
</table>

.....Willy

[Choopernickel]

Willy, I have to ask, what is this craziness:

</tr id="listRow_1Close">

That not only is completely invalid, it doesn't make any sense. There is a better way to mark associations of closing tags with opening tags, and should be taught, especially now that standards are starting to become the norm.

<tr id="listRow_1">
  <td>...</td>
</tr><!-- id="listRow_1" -->

Dreamsonthefly, the <!-- --> you see above are commenting marks - anything between them will be completely ignored by the browser. Some people use these to denote, for example, which row or table is closing with the current tag, just like above. It's entirely optional, but a very good practice, to comment your code. And please try to make your code both readable and meaningful: use an HTML reference book or website to guarantee that you're not breaking any of the rules of HTML.

[dreamsonthefly]

Will y Du it Again. Thanks!

[Willy Duitt]

Originally posted by Choopernickel
Willy, I have to ask, what is this craziness:
</tr id="listRow_1Close">

That not only is completely invalid, it doesn't make any sense. There is a better way to mark associations of closing tags with opening tags, and should be taught, especially now that standards are starting to become the norm.

Choopernickel;

There is nothing invalid about what I did. Perhaps for this example, it was overkill, but I have been trying to teach Rhonda coding techniques which look towards the future standards.

FWIW: It is not invalid to apply an ID to any element. And although it may add to the overall document size (whitespace). The practice of assigning ID's will allow you to more easily go thru the DOM to make changes to a document without actually editing the content.

.....Willy

BTW: I do use descriptive ID's to aide in editing if I do need too.

[Choopernickel]

Willy, part of the problem is that a closing tag is not an element, and may contain no attributes, as evidenced in w3 Recommendations going back at least to HTML 4.01:

3.2.2 Attributes

Elements may have associated properties, called attributes, which may have values (by default, or set by authors or scripts). Attribute/value pairs appear before the final ">" of an element's start tag. Any number of (legal) attribute value pairs, separated by spaces, may appear in an element's start tag. They may appear in any order.

Comments are valid anywhere in any SGML document, so long as they're not nested. Using comments after closing tags is just as readable as your manner -- with the added benefit of validity.