How to digest free javascripts
|
||
| Home |
http://de.geocities.com/erhardweinerth/ |
Bottom |
| communicator |
the validation program for
web pages. |
|
| navigator |
the validation browser for
web pages. |
|
| composer |
the validation base for composing
web pages. |
|
| The main underlying structure,
that keeps everything in place, is the table. The composer menus deal with handling tables, links, anchors etc. The composer offers four views: 1. the regular view, that shows table borders and anchors. 2. the tag view, that shows tags, table borders. 3. the source view, that shows the source code. 4. the composer view, that shows the page like the navigator but does not run, - it does not execute. If you want to execute the features of the page, you may do this: 1. after save as, save the composer page. 2. open the document or if it is open reload the page. 3. now you can use the features of the page, they will execute like web pages. You can switch between the navigator page and the composer page, as you can see on the task bar. |
||
| free javascript original |
download or save as
- a document is stored. This file is the base for everything that
follows. It contains 1,2,3 or more parts, that have to be built in the test
page. There may be parts for the head tag section and or the body tag section and or for the body tag. In addition there may be external files, that the page needs to work properly. |
|
| free javascript with alterations |
Some free javascripts work
immediately. Others need a few alterations like changing external links
to internal ones with anchors instead of web addresses. Too many do not run after attempts to get them work with a few alterations. After an endless series of trail and error it may be willing to work as it should. As soon as the altered original runs I could stop. But in some types of cases I want to see something even if the task does not create anything for display. Then I have to add messages and other objects to get something to read or watch. |
|
| free javascript with expansions |
If the page does not contain
enough content I have to add more features. |
|
| free javascript examples |
The large number of tasks
that can be performed by using javascripts recommend a collection of examples,
from which you can draw the fitting one when you need it. You
cannot have too many examples. |
|
| free javascript exercises |
Tutorials may give us examples
and exercises. Free web tutorials may be the first we are looking for,
but books and CD ROMs and manuals from other sources may become
our indispensable favorites. The web got the greatest potential but it may
at a point in time not have the quantity and quality you desire. Working with
free javascripts lets us exercise what is needed to make it run and
the types of tasks on hand. |
|
| free javascript snippets |
Snippets are code pieces that
may be used over and over again. The larger your snippets collection the better. |
|
| error corrections |
Finding errors and getting
rid of them is a great adventure for all troubleshooters. Troubleshooting
exercises. |
|
| links with new destinations |
You got your own ideas where
you want to send your visitors to. You have to enter your own destinations. |
|
| anchors instead of web pages |
When working offline you need
offline destinations, anchors are the easiest choice. The Top anchor can be
used as default destination for many executed tasks. |
|
| checking of all external and internal links and
file calls |
Many file types may be called
by your page: gif,jpeg,html,js,css, data base, data bank, -etc. Many types of destinations may be used in links. |
|
| the structure of the page |
The top table is for the display
title, the Home and Bottom link, and the site address. The main table (width 760 pixels) is built of 3 columns and a number of rows as needed. The left column (100 pixels) contains a link to How to digest free javascripts? and anchors mainly for testing. The right column (100 pixels) contains a link to Changes that had to be made and anchors mainly for testing. The middle column (560 pixels) shows in the top part of the column some source code display, mainly javascript parts. Below can be seen objects that are part of the execution of the javascript. In pages with expansions this pattern is repeated in the middle column. The bottom table is for the Home and Top link, and the site directory link. In the head part of the page I placed a comment line that marks the entry point for javascript head parts. Javascript body tag parts go there without other choice. In the body part of the page I placed comment lines that mark the entry points for javascript body parts. In addition there are comment lines that mark entry points for the reading/display sections, that display parts of the source code, mainly javascript code. You can see the structure when you are using the composer source view. |
|
| default link destination |
In all pages of the site I
use the Top anchor as default link destination. |
|
| check lists |
A list of steps, a list
of instructions, a program, a list of points to check. They may be broad,
raw or narrow, fine, detailed. If they are truly useful they will be popular
and wanted. If you cannot find the right type of check lists create your own. |
|
| learning javascripting |
Why and what for do we use
free javascripts? 1. We want to learn javascripting so we can write our own javascripts. 2. We want to know what others do and how they perform the tasks. 3. They are additional exercises and examples to tutorials, books, CD-ROMs and other sources. |
|
| development environment |
There is always some type
of development environment within which we create web pages. In my
case I use the Netscape Communicator as starting point and end point. |
netscape
communicator |
| Home |
site directory |
Top |