Tuesday 07th of September 2010 11:20:10 AM
left column
All templates are XHTML 1.0 and CSS2/ tableless.
2 columns / menu and content dynamic
2 column layout grid. Both columns are dynamic and adjust themselves procentually to the browser window.
more nice and free css templates
body {
background-color: #8b4513;
font-size: 11px;
font-family: Verdana, Arial, Helvetica, SunSans-Regular, Sans-Serif;
padding:0px;
margin:0px;
}
#content {
float:left;
width:70%;
background:#fff;
border-right:2px solid #996666;
border-bottom:2px solid #996666;
margin-right:15px;
padding-bottom:20px;
}
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.
Web-based apps might themselves rely on another app server to gather information that is presented on the client web browser. Also, you can write Servlets that get information from remote or local databases, XML document repositories and even other Servlets. One good use for web-based apps is to be a wrapper around an app server, so that you can allow your customers to access at least part of the services offered by your app server via a simple web browser. So web-based apps allow you to integrate many components including app servers, and provide access to this information over the web via a simple web browser.
Web-based apps are very deployable, since they don't require special Java VMs to be installed on the client side, or any other special plug ins, if the creator of the web-based app relies solely on HTML. Unfortunately, this can restrict the level of service that can be offered by a web-based app when compared to the functionality offered by custom clients of an app server, but they are a good compromise when it comes to providing web-based access to your information. In fact, in a real world scenario, both a web-based app and app server may be used together, in order to provide your customers access to their information. In an Intranet setting, you might deploy the clients that come with the app server, and in an Internet setting it would be better to deploy a web-based app that sits on top of this app server, and gives your customers (relatively) limited access to their data over the web (via a simple web browser).
STRONG {font-weight: lighter;} /* lighter than its parent */
B {font-weight: lighter;} /*lighter still */
<P>
900 <SPAN> 700 <STRONG> 400 <B> 300 <STRONG> 200
</STRONG></B></STRONG></SPAN>.
</P>
<!-- ...or, to put it another way... -->
<P>
bold <SPAN> bold <STRONG> regular <B> regular
<STRONG> regular </STRONG></B></STRONG></SPAN>.dark green background -- the same dark green you are to use for
unvisited hyperlinks and the left edge of the browser window. All
headings, including document titles, are to use a sans serif font.
The rest is left to our discretion.
A lot of this is fairly straightforward. For the document
BODY, we write:
BODY {font-family: Times,serif; color: black;
background: white url(pix/grstripe.gif) repeat-y top left;}
6.2.5.1. Interesting effects
In technical terms, when abackground image has been set to be fixed, it ispositioned with respect to the viewing area, not the element thatcontains it. However, the background will only be visible within itscontaining element. This leads to a rather interesting consequence.
Let's say we have a document with a tiled background that