File: about.html

package info (click to toggle)
hsc 0.916-2
  • links: PTS
  • area: main
  • in suites: hamm, slink
  • size: 2,584 kB
  • ctags: 2,277
  • sloc: ansic: 17,375; makefile: 396
file content (92 lines) | stat: -rw-r--r-- 5,109 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>hsc - Introduction</TITLE>
<LINK REV="owns" TITLE="Thomas Aglassinger" HREF="mailto:agi@giga.or.at">
<LINK REL="Next" HREF="copy.html">
<LINK REL="Copyright" HREF="copy.html">
<LINK REL="Previous" HREF="index.html">
<META name="ROBOTS" content="NOINDEX, NOFOLLOW">
</HEAD>
<BODY>
<A HREF="index.html"><IMG SRC="image/main.gif" ALT="Contents" ALIGN="middle" WIDTH="70" HEIGHT="16"></A>
<IMG SRC="image/noindex.gif" ALT="-----" ALIGN="middle" WIDTH="70" HEIGHT="16">
<A HREF="copy.html"><IMG SRC="image/copy.gif" ALT="Copyright" ALIGN="middle" WIDTH="70" HEIGHT="16"></A>
<A HREF="index.html"><IMG SRC="image/back.gif" ALT="Up" ALIGN="middle" WIDTH="70" HEIGHT="16"></A>
<A HREF="index.html"><IMG SRC="image/prev.gif" ALT="Previous" ALIGN="middle" WIDTH="70" HEIGHT="16"></A>
<A HREF="copy.html"><IMG SRC="image/next.gif" ALT="Next" ALIGN="middle" WIDTH="70" HEIGHT="16"></A>
<HR>
<P ALIGN="right"><I>Welcome Boyz and Girls to the Non-Official Shit-Reduction Program</I><BR>
(Novi Sad, "Me, Myself, All Over Again")
</P>
<H1>Introduction</H1>
The main purpose of this chapter is to help you deciding whether you
should go on reading this documentation or not.
<H2>Motivation</H2>
<P>If you read this, it's quite likely that you tried to design a html
page. And you probably found out that html is a very clumsy thing: No
macros, no include files and several other features lacking.</P>
<P>And what can you do after your page is ready? View it with a
browser and test-click all links? Pfuahahaha! Most browser are
designed to handle as many errors as possible and display a readable
page, but don't mention your errors! And link-testing is a very stupid
task...</P>
<P>Of course, there are several tools around: You can use a macro
languages like <KBD>m4</KBD> to define macros and include files, use
some of the various html validators, replace your special characters
with <KBD>recode</KBD> and run a link validation tool on your
page.</P>
<P>So, after installing several Tools (and compilers and
interpreters), you are ready to go... and can start five programs
after a simple change to one of your pages.</P>
<H2>What It Is</H2>
<P><KBD>Hsc</KBD> tries to summarize the functionality of all
these tools in one program: it performs a (basic) syntax
check, validates your (local) links, replaces special characters
by entities and provides a way to define macros which should
remind you to html.</P>
<P>It also supports several features you probably will not find in
most other tools, like <A HREF="features/uris.html#prjrel">project
relative URIs</A>, stripping useless white spaces and automatically
setting the <A HREF="features/getsize.html">attributes for images
size</A>.</P>
<P>Furthermore it provides some concepts to maintain your project with
popular tools like <KBD>make</KBD>.</P>
<H2>How It Works</H2>
<P><KBD>Hsc</KBD> simply acts as a preprocessor: You give it an "extended"
html-source (later in this document referred as "hsc source")
containing special commands, and <KBD>hsc</KBD> interprets it and produces a
pure html output as object file. This output file can be viewed with
your w3-browser.</P>
<P>Normally you will create your hsc sources using a simple text
editor, maintain them in a <I>Makefile</I> and process them with <KBD>hsc</KBD>. At
least I consider this the recommend way of using this tool.</P>
<H2>What It Is Not</H2>
<P>Obviously, there is no fancy GUI, no (pseudo-)WYSIWYG, no drag
&amp; drop - there are other programs which provide these
functionalities. But a common lack of these programs usually is that
they give less support for large projects and are limited in
configurability.</P>
<P>If you just want to create your own personal homepage, write a
short html document with information about your three selfwritten
freeware-proggies, include a picture of your cat, send greets to Sepp
and Hugo or something like that, there are probably other tools which
are easier to handle and will serve your needs more or less well.</P>
<P>It should also be stated that you will require several experiences
usually not needed for w3-authoring (or better: not expected to be
needed by most people). This includes a basic understanding of macro
creation, writing <I>Makefile</I>s and playing around with scripting
languages like Rexx. If you have never done such things before, I
recommend you forget this package soon and come back in a few
years.</P>
<P>This also is no install-and-run package. You will need several
other tools to fully use it, and it is not within the scope of this
documentation which one you choose. Although it contains some comments
and suggestions about that at various places.</P>
<P>Despite the general html- and w3-hype of the recent years, both this
tool and the author of it consider many concepts introduced with it
ridiculous, braindead and sometimes even pure shit. So this manual
contains opinions and language you might consider offensive. If you
want to hear the usual "Oh how great are all those things!", you will
have to look for something else.</P>
</BODY></HTML>