#left {
position: absolute;
left: 2%;
width: 19%;
top: 106px;
background-color: #ffffff;
}

#middleleft {
position: absolute;
left: 22%;
width: 28%;
top: 106px;
background-color: #ffffff;
}

#middleright {
position: absolute;
left: 51%;
width: 28%;
top: 106px;
background-color: #ffffff;
}

#right,#middleright,#middleleft,#left{
border: 1px solid #564b47;
padding:0px;
margin:0px;
}

p,h1, h3, pre {
padding: 5px 15px;
margin: 0px;
}

#right {
position: absolute;
left: 80%;
width: 18%;
top: 106px;
agent sets the element's font weight to the next numericalvalue, unless the value is already 900, in whichcase the weight remains at 900. Thus, you mightencounter the following situations, illustrated in Figure 5-10:
P {font-weight: normal;}P EM {font-weight: bolder;}  /* results in 'bold' text, evaluates to '700' */H1 {font-weight: bold;}H1 B {font-weight: bolder;}  /* if no bolder face exists, evaluates to '800' */P {font-weight: 100;} /* assume 'Light' face exists ; see explanation */
background-color: #ffffff;
}

open code
Use of this code is encouraged! (o_.)/

The containingblock is the context in which formatting takesplace. For example, the containing block of a boldface element couldbe the paragraph in which it occurs, as demonstrated in Figure 9-1.

Figure 9-1. An example of a containing block

Not every element in CSS generates a containing block for itsdescendant elements. The rules for the establishment of a containingblock are as follows:

Web-based applications are similar to app servers, except for one thing: Web-based applications don't have client apps, instead they use web browsers on the client side. They generate their front ends using HTML, which is dynamically generated by the web-based app. In the Java world, Servlets are best suited for this job.

I will take a break from my normal pragmatic approach to getting you (the programmer) started with using XML and Java and just talk about the high level (design level) benefits of this wonderful combination. A good design is important to a good implementation for any system.

When you create your data using an XML editor (that you can write), you can not only input the content of your data, but also define the structural relationships that exist inside your data. By allowing you to define your own tags and create the proper structural relationships in your information (with a DTD), you can use any XML parser to check the validity and integrity of the data stored in your XML documents. This makes it very easy to validate the structure and content of your information when you use XML. Without XML, you could also provide this validation feature at the expense of developing the code to this yourself. XML is a great time saver because most of the features that are available in XML are used by most programmers when working on most projects.

By using XML and Java, you can quickly create and use information that is properly structured and valid. By using (or creating) DTDs and storing your information in XML documents, you have a cross-platform and language independent data validation mechanism (for free) in all your projects!

You might use XML to define file formats to store information that is generated and used by your applications. This is another use of the structured nature of XML. The only limitation is that binary information can't be embedded in the body of XML documents. For example, if you wrote a word processor in Java, you might choose to save your word processor documents to an XML (actually your ApplicationML) file. If you use a DTD then your word processor would also get input file format validation as a feature for free. There are many other advantages to using XML and a file storage format for your applications which will be illustrated later in the chapter.