|
|
Home | Switchboard | Unix Administration | Red Hat | TCP/IP Networks | Neoliberalism | Toxic Managers |
| (slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and bastardization of classic Unix | |||||||
|
|
Cascading Style Sheets (CSS) were introduced way back in 1996. A cascading style sheet is a set of instructions called styles in a linked external file or within the source code of a page that tells a browser how to render page elements - text color and sizes, page backgrounds, tables etc. they are very similar to MS Word styles and its a shame that even FrontPage 2003 does not handle external styles gracefully: it makes available only paragraph styles in the style selection windows on the toolbar (as well as in a special class selection window of the style toolbar).
Another Frontpage idiosyncrasy is the it automatically copies and make internal style sheet is you cut and paste a clip from a web page. This is very annoying feature as you need to delete this stylesheet each time you past the clipping.
The most basic way of using CCS is to specify using them typical types of paragraphs. for example instead of
<blockquote><p><font size="2" face="Arial">
...text...
</font></p></blockquote>
you can use paragraph style:
p.quote { font-family: arial; font-size: 10pt; margin-left: 50pt }
|
|
By using a linked stylesheet you only need to change one file and then the entire site would be updated. Also if you decided to change the font to Helvetica 10, you do not need to edit all pages. You can do it in the external stylesheet. Generally using external stylesheet makes HTML markup tidier. Styles can also help to parameterize fonts, for example:
<font class="normal">
Styles are essentially a parameterless macros and you can imitate them (and do much more) using macroprogramming. Here is a function that can add an HTML to the page:
In FrontPage 2003, FrontPage 2002, and FrontPage 2000, this function adds any HTML content to a specified document, either appending to or replacing the document. It does this by creating an IHTMLTxtRange object from the body element of the FPHTMLDocument object. If the argument for the blnClearPage parameter is True, the entire contents between the opening and closing <body> tags is replaced; otherwise, the HTML is appended to the bottom of the current content, before the closing <body> tag.
The objects used in this example are as follows:
- FPHTMLDocument
- IHTMLTxtRange
- FPHTMLBody
Public Function AddHTMLToPage(objPage As FPHTMLDocument, _ strHTMLtext As String, blnClearPage As Boolean) As Boolean Dim objRange As IHTMLTxtRange Dim objBody As FPHTMLBody On Error GoTo ErrorHandler If blnClearPage Then Set objRange = objPage.all.tags("BODY").Item(0).createTextRange ' clear out the current document If blnClearPage Then Call objRange.pasteHTML("") End If objRange.collapse False Set objRange = Nothing End If Set objBody = objPage.body objBody.innerHTML = objBody.innerHTML & strHTMLtext & vbCrLf AddHTMLToPage = True ExitFunction: Exit Function ErrorHandler: 'Could not insert HTML. AddHTMLToPage = False GoTo ExitFunction End Function 'Use the following subroutine to call the preceding function. Sub CallAddHTMLToPage() Dim strHTMLString As String strHTMLString = "<P><B><I>BLAH</I></B></P>" + vbCrLf Call AddHTMLToPage(ActiveDocument, strHTMLString, True) End Sub
External stylesheet is a text file with the extension .css that contains a series of styles. When a page in the web links to this file, the browser reads the stylesheet before rendering the page. To attach a CSS file in FrontPage:
You can have one "master" stylesheet for you website and several "ad-on" stylesheet that are necessary only for a few pages. That prevents from putting in the mater stylesheet too many styles that are not used by the most pages.
Also you probably should avoid excessive zeal in using this feature. Stylesheets are a good tool but overused they make coding less transparent instead of more transparent.
External CSS are typically located in a special directory, for example CSS
Frontpage 2003 support of external style sheets is weak. It does not import definitions into menus.
|
|
Switchboard | ||||
| Latest | |||||
| Past week | |||||
| Past month | |||||
 |
 |
 |
Inline Elements - Adding Style using the<span></span>ElementWant to be able to add
<span class=""></span>elements without hand coding? Do this...When working with frontpage and CSS, you have to be very specific with your stylesheets. If you want inline elements to appear in your formatting menu (as inline elements), you need to precede your classes with
[b]span[/b]. For example, let's say you want to make a word blue. You would need something like this in your stylesheet...
span.blue{color:#369;background:#fff;}Once you append the
[b]span[/b]to the class, that will now appear in FP's styling menu with an a (with underscore) symbol to the left of it. This means that it is an inline element. Block level elements have a ¶ to the left of them which means they are block level.If your style sheets have generic classes that start with a dot (.), they will appear in the menu without the a or ¶ symbols and will be treated as if they were block level elements.
FP's styling menu is sorted in a specific way. All of your predefined block level elements will appear at the top of the list. Then your generic classes will appear (in alphabetical order). And then your specific block and inline classes will appear at the bottom, in alphabetical order.
Society
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
Quotes
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Bulletin:
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
History:
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
Classic books:
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D
Copyright © 1996-2021 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|
|
You can use PayPal to to buy a cup of coffee for authors of this site |
Disclaimer:
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.
Last modified: March, 12, 2019
