Book HomeCascading Style Sheets: The Definitive GuideSearch this book Thursday 23rd of October 2014 04:16:54 AM

A.3. Online Communities

One can read only so much before it comes time to join a discussion and ask some questions. There are two major venues for discussions about CSS, but each is concerned with a specific type of discussion -- so make sure you go to the right place.

A.3.1. comp.infosystems.www.authoring.stylesheets

This Usenet group, often abbreviated as ciwas (pronounced "see-wass"), is the gathering place for CSS authors. A number of experts in the field check this newsgroup regularly, this author among them, and all are there for one primary reason: to help new CSS authors over the hurdles that learning any new language will generate. The secondary reason is for the spirited debates that occasionally erupt over some aspect of CSS, or a browser's implementation thereof. Rather unusually for a newsgroup, the signal-to-noise ratio stayed fairly high for the last few years of the 1990s, and will with any luck continue in that vein.


Anyone who wishes to be involved in discussing the future course of CSS, and to clearing up ambiguities in the specifications, should subscribe to this list. The members of the list are all, in one fashion or another, interested in making CSS better than it is already. Please note: www-style is not the place to ask for assistance with writing CSS. For help with CSS authoring problems, visit ciwas instead. Questions beginning with "How do I ... ?" are frowned upon by the regulars of www-style and are usually redirected to a more appropriate forum such as ciwas. On the other hand, questions that begin "Why can't I ... ?" or "Wouldn't it be cool if ... ?" are generally welcome, so long as they relate to some ability that appears to be missing from CSS.

Messages to www-style are only accepted if the sender is already subscribed to the list. In order to subscribe, send email to with the word subscribe in the subject of the message; to unsubscribe, send email to with the word unsubscribe in the subject of the repeat-left, for example, although it couldcertainly be added in some future version of CSS. For now, you getfull tiling, horizontal tiling, vertical tiling, or no tiling at all. Repeating: Real-world issues

There are a few things to keep in mind when it comes to web browsers.First is that in Navigator 4 and Internet Explorer 4, tiling onlyhappened down and to the right. If you're using Explorer 4,centering an image in the background and then tiling it would look message.

Library Navigation Links

Copyright © 2002 O'Reilly & Associates. All rights reserved.

Client side - Graphical Java Applications

The simplest category of XML Java applications is the kind of Java application that stores information in XML documents (files). This is illustrated in Figure 1. By using XML to create your own markup languages (i.e. your own file formats for your information) in an open way, you don't have to use propietary and binary file formats. Using XML over proprietary binary file formats, allows your applications to have immense inter operability across platforms, applications and even programming languages. Since any kind of markup language can be defined using XML (you can even formalize it by creating a DTD for it) applications can store their information using their own markup languages. For example, address book information can be stored in an AddressBookML file. A few commercial programs currently available allow saving their application data to XML files, e.g., Framemaker can save its documents as XML files.

In order to create applications of this category, you might have to define a DTD for your information. Then you have to write classes to import and export information from your XML document(s) (validating using your application's DTD if you have one). You must also write the classes which create the user interface in your application. The user of your application can view and modify information using the GUI (graphical user interface), and they can save (and load) their information to (and from) an XML file (that might use your DTD); in other words, they can save (and load) their information to (and from) an ApplicationML file (where Application is the name of your application). Some examples are AddressBookML, MathML, SVGML, etc.

contains only images -- then thanks to the fact that color is inherited, the border color for that table would be the text color of its parent element. This is likely to be BODY, DIV, or another TABLE. Thus, if an image has a border, and the BODY is its parent, given this rule:

BODY {color: purple;}

then, by default, the border around the image will be purple. Of course, to get that border to appear, you have to do a little work

Before we get there, however, there are a few more things to cover. Remember that absolutely positioned boxes can have backgrounds, margins, borders, and padding; styles can be applied within them, just as with any other element. This can make them very useful for the creation of sidebars, "sticky notes," and other such effects. One example is the ability to set a "change marker" on any paragraph that has been edited. This could be done using the following styles and markup:into another external style sheet and LINK it in.( Just make sure your LINK comes before the@import statement.) You'll end up withsomething like this:

/* file 'link-styles.css' */        /* file 'import-styles.css' */H1 {margin-bottom: 0;}              H1 {margin-bottom: 0;}P {margin-top: -1em;}               P {margin-top: 0;}<LINK REL="stylesheet" TYPE="text/css" HREF="link-styles.css"TITLE="Linked">