Go to Table of Contents
Go to Table of Contents
Go to Table of Contents
Go to Table of Contents
Web Development Books
- Web Concept & Design: a comprehensive guide for creating effective
web sites
by Crystal Waters; New Riders Publishing; 1996; 276 pages; $39.99US
This is a very useful guide for people just getting started on building a
web site. It provides a good overview of planning and design issues and many
examples and illustrations. There is also a related web site: <www.typo.com>.
- Designing Web Graphics: How to Prepare Images and Media for the Web
by Lynda Weinman; New Riders Publishing; 1996; 258 pages; $50 US includes
CD-ROM
This is a very helpful introduction to preparing graphics for the web and
deals with topics like minimizing download time, minimizing color problems,
and creating text graphics. There is a related web site: <www.lynda.com>.
- O'Reilly and Associates
Publishing company specializing in computer related books on subjects such
as Web Development, HTML, JAVA, CGI Programming and much, much more! Online
ordering available.<www.ora.com>.
Go to Table of Contents
Go to Table of Contents
Go to Table of Contents
Recommended by BC
Other possible tools (but not officially supported)
- Claris
HomePage 3 Basics - basic WYSIWYG web editor with specific functions for
connecting Filemaker Pro databases to the web.
- BBEdit Lite - a freeware
Macintosh text editor for creating and editing HTML documents.
- Arachnophilia - a
free "careware" HTML Text Editor which is well-designed and full-featured.
- Web Weaver Lite
- a shareware Macintosh text editor for creating and editing HTML documents
- AOLPress - WYSIWYG editor with many
nice features.
- Netscape Composer
- WYSIWYG web page editor included with Netscape Communicator v4+.
Go to Table of Contents
Go to Table of Contents
Not supported by BC
-
HTML Grinder
- A powerful utility for Macintosh-based Webmasters. Uses plug-in tools that perform
repetitive chores on all of your HTML files at once.
Go to Table of Contents
Go to Table of Contents
Go to Table of Contents
If you would like to display a counter on your page which shows how many times your page has been accessed, include the code below on the page where the counter should appear. Change the phrase "username#.dat" to your username followed by a number with ".dat" as the extension. If you have a counter on several pages, add different numerals to the end of the username to make them unique.
<IMG SRC="/cgi-bin/wwwcount2.3/Count.cgi?df=username#.dat">
For example, this code produces the counter below:
<IMG SRC="/cgi-bin/wwwcount2.3/Count.cgi?df=web_development.dat">
To customize this counter, please see the Count
2.0 Example Page written by the program author.
Go to Table of Contents
InfoTech provides access on InfoEagle for knowledgeable programmers to
develop interactive WWW applications, using HTML front-ends and C or PERL CGI
scripts. (If you are going to be programming in PERL, you probably do not need
interactive access, but if you need to use the C compiler you will need interactive
login access added to your account.)
InfoProviders interested in developing interactive WWW applications
should send a brief description of the application you wish to develop
to the InfoEagle staff, (infoeagle@bc.edu). Once this is received and reviewed, your account privileges on InfoEagle will be changed to allow you to begin developing scripts.
InfoTech does not provide support for CGI scripting. We allow you access to the machine for the purpose of developing CGI applications, but IT will not write or debug your scripts.
To program CGI scripts on InfoEagle
You Must:
- Be an approved InfoProvider, with an account in your own name
- Know and be able to program CGI scripts in PERL or C.
- Be familiar with a UNIX environment.
The Scripts must:
- be placed in the organization/department data directory on InfoEagle that
you are responsible for. (for organizational purposes you may want to create
a directory called cgi-bin to hold all your scripts.)
- end in the .cgi extension.
- Perl Scripts must begin with the line #!/usr/local/bin/perl
- All source code for compiled scripts should be kept in your user directory
rather than your data directory, but the compiled executable must be kept
in the directory for the organization that's using the script and not in your
personal directory. Remember, when you leave BC, your personal directory will
be removed.
- if using FTP, be uploaded in ASCII format (PERL scripts) to avoid ^M characters
being inserted at the end of every line.
- have the execute permissions turned on for "world" or "everyone."
This can be done with the UNIX chmod command or with commands in an FTP client.
(WSFTP Pro and Fetch both support permission changes).
Go to Table of Contents
Copyright 2000 - The Trustees of Boston College
URL: http://www.bc.edu/cwis/web_development.html
Questions/Corrections/Comments
Last Update: January 26, 2001