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 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384
|
<HTML>
<!--
***********************************************************************
FUNNELWEB MANUAL WEB PAGE
=========================
Copyright (c) Ross N. Williams 1992,1999. All rights reserved.
Permission is granted to redistribute and use this manual in
any medium, with or without modification, provided that all
notices (including, without limitation, the copyright
notice, this permission notice, any record of modification,
and all legal notices) are preserved on all copies, that all
modifications are clearly marked, and that modified versions
are not represented as the original version unless all the
modifications since the manual's original release by Ross N.
Williams (www.ross.net) consist of translations or other
transformations that alter only the manual's form, not its
content. THIS MANUAL IS PROVIDED "AS IS" AND WITHOUT ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT
LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND
FITNESS FOR A PARTICULAR PURPOSE. TO THE EXTENT PERMITTED BY
LAW THERE IS ABSOLUTELY NO WARRANTY.
***********************************************************************
-->
<HEAD>
<TITLE>7.6 Defining Macro Libraries</TITLE>
<STYLE TYPE="text/css"> <!-- A {text-decoration: none} // --> </STYLE>
</HEAD>
<BODY BACKGROUND="binary/background.gif"
BGCOLOR="#FFFFFF"
TEXT="#000000"
VLINK="#660000"
LINK="#FF0000"
ALINK="#CC0000">
<TABLE WIDTH="490">
<TR>
<TD WIDTH="130" VALIGN="top">
<IMG SRC="binary/d_clear.gif" ALT="" WIDTH="130" HEIGHT="1"><BR>
<FONT SIZE="2">
<BR>
<A HREF="http://www.ross.net/"
TARGET="rosshome"
onClick="window.open('','rosshome','location,status,menubar,scrollbars,resizable',false).focus(); return true;"
>
<IMG SRC="binary/rossnet_logo.gif"
WIDTH="64" HEIGHT="32"
BORDER="0" ALT="RossNet"
HSPACE="0" VSPACE="1"></A><BR>
<BR>
<A HREF="../index.shtml"
TARGET="funnelweb"
onClick="window.open('','funnelweb','location,status,menubar,scrollbars,resizable',false).focus(); return true;"
>
<IMG SRC="binary/linklogo.gif"
WIDTH="64" HEIGHT="32"
BORDER="0" ALT="FunnelWeb"
HSPACE="0" VSPACE="1"></A><BR>
<BR>
<TABLE CELLSPACING=0 CELLPADDING=0 BORDER=0><TR><TD BGCOLOR="#000000">
<A HREF="../reference/index.html"
TARGET="funnelwebreference"
onClick="window.open('','funnelwebreference','location,status,menubar,scrollbars,resizable',false).focus(); return true;"
><FONT COLOR="#FFFFFF"><B>Reference</B></FONT></A><BR>
<BR>
<A HREF="../developer/index.html"
TARGET="funnelwebdeveloper"
onClick="window.open('','funnelwebdeveloper','location,status,menubar,scrollbars,resizable',false).focus(); return true;"
><FONT COLOR="#FFFFFF"><B>Developer</B></FONT></A><BR>
<BR>
<A HREF="index.html"><FONT COLOR="#FFFFFF"><B>Tutorial</B></FONT></A><BR>
<A HREF="intro.html"><FONT COLOR="#FFFFFF">1 Introduction</FONT></A><BR>
<A HREF="macro.html"><FONT COLOR="#FFFFFF">2 Macros</FONT></A><BR>
<A HREF="type.html"><FONT COLOR="#FFFFFF">3 Typesetting</FONT></A><BR>
<A HREF="example.html"><FONT COLOR="#FFFFFF">4 Example</FONT></A><BR>
<A HREF="hints.html"><FONT COLOR="#FFFFFF">5 Hints</FONT></A><BR>
<A HREF="examples.html"><FONT COLOR="#FFFFFF">6 Examples</FONT></A><BR>
<A HREF="web.html"><FONT COLOR="#FFFFFF">7 Webmaking</FONT></A><BR>
<BR>
<A HREF="search.html"><FONT COLOR="#FFFFFF"><B>SEARCH</B></FONT></A><BR>
</FONT>
</TD></TR></TABLE>
</TD>
<TD WIDTH="360" VALIGN="top">
<FONT SIZE="3">
<A HREF="../reference/index.html"><IMG SRC="binary/title.gif"
WIDTH="302" HEIGHT="24"
BORDER="0" ALT="FunnelWeb Tutorial Manual"
HSPACE="0" VSPACE="0"></A>
<P><FONT SIZE="5">7.6 Defining Macro Libraries</FONT><BR>
<P><BR><FONT SIZE="4"><STRONG>Separating Macros Into An Include File</STRONG></FONT><BR>
<P>Once you start using FunnelWeb to make webs, you'll discover
that you find yourself defining and using the same macros over and
over. Rather than redefining them for each new web you make, you
can place them all in a FunnelWeb include file, so that they can
be included in the FunnelWeb file for each web you make. Suppose
that we create a file called <SAMP>style.fwi</SAMP> containing the
following text:
<P>
<PRE>
@$@<Begin page@>@(@1@)@M@{
<HTML>
<HEAD>
<TITLE>@1</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000033>
@}
@$@<End page@>@{
</BODY>
</HTML>
@}
@$@<Dilbert@>@Z@M@{@-
<A HREF="http://www.dilbert.com/">Dilbert</A>@}
@$@<Yahoo@>@Z@M@{@-
<A HREF="http://www.yahoo.com/">Yahoo</A>@}
</PRE>
<P>Once this is done, the main web file can become:
<P>
<PRE>
@!************************************************
@i style
@!************************************************
@O@<index.html@>@{
@<Begin page@>@(Dave's Home Page@)
<P>Welcome to my home page. Check out my
<A HREF="@<Links FILE@>">links page</A>.
@<End page@>
@}
@!************************************************
@$@<Links FILE@>@M@{links.html@}
@O@<links.html@>@{
@<Begin page@>@(Dave's Links@)
<P>Check out @<Yahoo@> and @<Dilbert@>.
@<End page@>
@}
@!************************************************
</PRE>
<P>Now we're starting to see some real simplification!
<P>Note: It's important to attach <SAMP>@Z</SAMP> to any
macro you place in an include file that you think might
not be called in some webs. If you don't, FunnelWeb will issue
"this macro is unused" errors for the included
macros you don't use.
<P><BR><FONT SIZE="4"><STRONG>Library Macros</STRONG></FONT><BR>
<P>Once you've created one or more macro libraries in the
form of FunnelWeb include files, you might find that sometimes
you want to redefine some of the macros that the include
file provides. For example, suppose that we are preparing
an Australian web page and that when we refer to Yahoo, we
want to refer to the Australian Yahoo site. If we try to
redefine the Yahoo macro:
<P>
<PRE>
@i style
...
@$@<Yahoo@>@Z@M@{@-
<A HREF="http://www.yahoo.com.au/">Yahoo</A>@}
</PRE>
<P>then FunnelWeb will issue an error "this macro
is already defined". FunnelWeb does not allow macros to
be redefined because this could be dangerous in a programming
context. It would be very bad if a programmer thought they
was invoking one piece of text when they were really invoking
another. So FunnelWeb complains.
<P>To stop FunnelWeb complaining, you can tag with a library
macro marker <SAMP>@L</SAMP> any macro in the include file that
you want to be able to redefine. For example:
<P>
<PRE>
@$@<Dilbert@>@Z@M@L@{@-
<A HREF="http://www.dilbert.com/">Dilbert</A>@}
@$@<Yahoo@>@Z@M@L@{@-
<A HREF="http://www.yahoo.com/">Yahoo</A>@}
</PRE>
<P>This allows us to redefined the Yahoo and Dilbert macros.
<P><BR><FONT SIZE="4"><STRONG>Modifying Default Behaviour</STRONG></FONT><BR>
<P>The library macro mechanism allows you to set up all kinds
of default behaviour that can be modified in specific webs. For
example, suppose that we rewrote the macro library as:
<P>
<PRE>
@$@<Begin page@>@(@1@)@M@{
<HTML>
<HEAD>
<TITLE>@1</TITLE>
</HEAD>
@<Body@>
@}
@$@<End page@>@{
</BODY>
</HTML>
@}
@$@<Body@>@L@{@-
<BODY BGCOLOR=#FFFFFF TEXT=#000033>@}
</PRE>
<P>Once this is done, we can modify the page background
and colours of any web by redefining the <SAMP>Body</SAMP>
macro without having to redefine the start and end
of page macros.
<P>
<PRE>
@!************************************************
@i style
@$@<Body@>@{@-
<BODY BGCOLOR=#000000 TEXT=#FFFFFF>@}
@!************************************************
@O@<index.html@>@{
@<Begin page@>@(Dave's Home Page@)
<P>Welcome to my home page. Check out my
<A HREF="@<Links FILE@>">links page</A>.
@<End page@>
@}
@!************************************************
@$@<Links FILE@>@M@{links.html@}
@O@<links.html@>@{
@<Begin page@>@(Dave's Links@)
<P>Check out @<Yahoo@> and @<Dilbert@>.
@<End page@>
@}
@!************************************************
</PRE>
<P><BR><FONT SIZE="4"><STRONG>Use Of Additive Macros</STRONG></FONT><BR>
<P>Additive macros can be used to insert information into
the middle of macros already defined. For example, suppose
you defined:
<P>
<PRE>
@$@<Begin page@>@(@1@)@M@{
<HTML>
<HEAD>
<TITLE>@1</TITLE>
@<Header fields@>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000033>
@}
@$@<Header fields@>+=@{@}
</PRE>
<P>Once the header fields macro is in place, you can add text such
as style commands or keyword tags to each of the pages of your web
without having to modify the header include file. Just add a definition,
such as the following, to your main FunnelWeb file:
<P>
<PRE>
@$@<Header fields@>+=@{
<STYLE TYPE="text/css">
<!-- A {text-decoration: none} // -->
</STYLE>
@}
</PRE>
<P><BR><FONT SIZE="4"><STRONG>Selecting Absolute Or Relative Links</STRONG></FONT><BR>
<P>Sometimes it's important to generate a web that uses
relative hyperlinks, and sometimes it's important to generate
a web that uses absolute hyperlinks. For example, it's important
to use relative links if you want to browse a web offline, or
if you want to ensure that username and password fields in
the URL are not obliterated by the following of an absolute link.
Absolute links are important where a web that is normally
adjacent to another web (and hence usually links to it using
a relative link) is separated and must be browsed offline.
<P>A good way to organize all this is to define FunnelWeb
macros for the URLs of webs in include files, but allow them
to be overruled by including files. For example, an
file might contain the following definitions:
<P>
<PRE>
@$@<Rocksoft WWW@>@Z@M@L@{http://www.rocksoft.com/@}
@$@<Ross WWW@>@Z@M@L@{http://www.ross.net/@}
@$@<Veracity WWW@>@Z@M@L@{http://www.veracity.com/@}
</PRE>
<P>These symbols are useful for referring to these various
webs from within these webs. However, it is convenient for
each subweb to refer to other subwebs using a relative path
rather than an absolute path, so when generating (say) a
subweb of the Ross webspace, the Ross macro could be redefined to:
<P>
<PRE>
@$@<Ross WWW@>@Z@M@{../@}
</PRE>
<P>This technique can be used in various forms to manage
the links in the online and offline versions of webs.
<P>
<TABLE WIDTH="100%">
<TR>
<TD ALIGN="left" VALIGN="bottom"><A HREF="web_style.html"><IMG SRC="binary/fw_left.gif" HEIGHT="32" WIDTH="32" BORDER="0" ALT="Prev"></A></TD>
<TD ALIGN="center" VALIGN="bottom"><A HREF="web.html"><IMG SRC="binary/fw_up.gif" HEIGHT="32" WIDTH="32" BORDER="0" ALT="Up"></A></TD>
<TD ALIGN="right" VALIGN="bottom"><A HREF="web_param.html"><IMG SRC="binary/fw_right.gif" HEIGHT="32" WIDTH="32" BORDER="0" ALT="Next"></A></TD>
</TR>
</TABLE>
<HR>
<FONT SIZE="2">
<A HREF="mailto:webmaster@ross.net">Webmaster</A>
<A HREF="copyright.html">Copyright © Ross N. Williams 1992,1999. All rights reserved.</A><BR>
</FONT>
</FONT>
</TD>
</TR>
</TABLE>
</BODY>
<!-- *********************************************************************** -->
<!-- End Of A FunnelWeb Manual Web Page (www.ross.net/funnelweb/) -->
<!-- *********************************************************************** -->
</HTML>
|