Conventions

Introduction
byAndrew Filevet al.?
Wrox Press ©2002
Team FLY

We've used a number of different styles of text and layout in this book to help differentiate between different kinds of information. Here are examples of the styles we used and an explanation of what they mean.

Code has several fonts. If it's a word that we're talking about in the text - for example, when discussing a for (...) loop, it's in this font. If it's a block of code that can be typed as a program and run, then it's also in a gray box:

         public Employee this[int index] 

Sometimes we'll see code in a mixture of styles, like this:

         public Employee this[int index]         {            get            {                foreach (Employee em in employees)                {                   if (em.ID == index)                     return em;               }            return null;            }         } 

In cases like this, the code with a white background is code we are already familiar with; the line highlighted in gray is a new addition to the code since we last looked at it.

Advice, hints, and background information come in this type of font.

Important pieces of information come in boxes like this.

Bullets appear indented, with each new bullet marked as follows:

  • Important Words are in a bold type font.

  • Words that appear on the screen, or in menus like the Open or Close, are in a similar font to the one you would see on a Windows desktop.

  • Keys that you press on the keyboard, like Ctrl and Enter, are in italics.

Team FLY


Professional UML with Visual Studio. NET. Unmasking Visio for Enterprise Architects
Professional UML with Visual Studio. NET. Unmasking Visio for Enterprise Architects
ISBN: 1440490856
EAN: N/A
Year: 2001
Pages: 85

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net