I am here to write for the Leah-man. I am not professionally trained to design websites or program in any certain programming language. I was brought on to Ameronix to help with the selling of services aspect. I was a salesman of sporting goods once and I got pretty good at it after a couple of months. Most sporting goods are not that complicated. So then, in comparison, I am now selling computer programming and web design services. There is quite a learning curve when attempting to sell something this complex and complicated. There are so many different variations and options within this industry and knowing everything about it would almost be impossible, but helpful none the less. As a salesman, you are always trying to satisfy the customer and tell he or she that anything is possible. “Yes, we can do that” I always say, irregardless of truth. But the truth in web design and computer programming is that most everything is possible. And there are a million different ways to do the same thing. A hundred lines of code and ten lines of code can produce the same result and this is key when quoting a project. So in my finite wisdom, I just want to tell those salesmen and women out there that are selling web design and computer programming services, that unless you have an extraordinary amount of knowledge concerning this subject and you have studied for many years at a reputable university, please do not hesitate to ask your lead programmer and developer on advise for how long and how complicated a certain project is. Trust me, you will see the difference in the quotes and hopefully in the profits at the end of the fiscal year. Best of luck.

There are two schools of thought when it comes to the structuring of a web page via HTML. First there is the method that uses tables to position everything on the page. On more complicated layouts this often leads to tables nested within other tables. The second methodology takes advantage of the <div> tag. Everything that can be accomplished with one can be accomplished with the other, so it really comes down to a preference of which methodology do you prefer to “think in”.

What follows is a very simple “Hello World” example. Both code snippets produce the same page when viewed through a web browser. The code for both methodologies is provided (tables first, followed by the div style).

As you can see in the example the div code is much simpler and more elegant. Again, this is not always the case but was in this case since it was written first. While both of these examples have been very simple and straightforward it is not hard to take the concepts and apply them to much larger and more complicated structures.

<table>
  <tr>
     <td>
       Hello World!
     </td>
     <td>
       Hello World!
     </td>
   </tr>
</table>

<div style="float:left; margin:0px 119px 0px 3px;">Hello World!</div>
<div style="float:left;">Hello World!</div>

We will step through the code that utilizes tables first. The table was created with a fixed width however the table data elements were not given widths and thus defaulted to 50%. This provides the large amount of whitespace between the two “Hello Worlds”. The div code appears to be a bit more complex upon first inspection but is very simple as well. Within the style declarations in both div tags we encounter “float:left;”, this code puts both “Hello Worlds” on the same line. The closing div tag will automatically put all code below it on a new line. Therefore it is necessary to float the elements to get them on the same line. The white space between the two “Hello Worlds” is then created by the margin declarations.

The previous example may give the impression that it easier and more elegant to code using the table structure. The code appears much cleaner and has less attributes need to achieve the same output. However that is not the truth. I merely appear that way since I coded the table version first and then had to play with the div version to make it match. To illustrate this point I will do it the opposite way for the next example; code the div version first and then make a table version match it.

<div style="width:350px;">
  <div>
    Hello Earth!
  </div>
  <div style="float:right;">
    Hello Earth!
  </div>
</div>

<table width="356px" style="margin-left:-3px;">
  <tr>
    <td colspan="2">
      Hello Earth!
    </td>
   </tr>
  <tr>
    <td style="text-align:right;" colspan="2">
      Hello Earth!
    </td>
  </tr>
</table>

As you can see in the example the div code is much simpler and more elegant. Again, this is not always the case but was in this case since it was written first. While both of these examples have been very simple and straightforward it is not hard to take the concepts and apply them to much larger and more complicated structures.