AOLpress is an integrated browsing and WYSIWYG authoring tool for the World Wide Web. AOLpress was designed both to make WWW authoring more accessible to beginners and to save valuable time and effort for professional Web publishers.
1. System Requirements
Required: 16 megabytes of RAM, requires 24 megabytes when using AOL and AOLpress simultaneously*
Required: System 7.x or later
Recommended: 68030 or faster processor. (AOLpress 2.0 is a fat binary and will run natively on the Mac 68K and the Mac PPC)
Required: 7 MB free on your hard disk
- Required: Color monitor using at least 256 colors
* If you have low memory, AOLpress may run better using Virtual Memory. Go to the Apple Menu => Control Panels and select Memory. In this dialog box, turn on Virtual Memory if you haven't already. Next, increase the amount of memory. Performance decreases as you increase Virtual memory used.
2. Networking Requirements
If you plan to use AOLpress as a browser and/or remote authoring tool, you will need the following:
Internet service provider (e.g. AOL 3.0 for Macintosh )
Modem
Connection software (MacTCP, Open Transport, PPP)
3. Installation and Configuration
You should have an "Install AOLpress 2.0" file. If you only have an "ap2.0.hqx" file, then you need to DeBinHex it. Do this by dragging and dropping "ap2.0.hqx" onto Stuffit Expander or a similar utility.
Double-click on the "Install AOLpress 2.0" icon. Follow the instructions to install AOLpress on your system in its own "AOLpress Folder". Files created by AOLpress will be placed in this folder.
- Double-click on the AOLpress icon.
- AOLpress does not insist that you set a proxy server and a name server, but it is highly recommended that you set them using Tools=>Preferences=>Network. AOL members only need to use screenname@aol.com as the Return address and a.mx.aol.com as the Mail Host in this dialog.
- After you have AOLpress running on your system, you may delete the installer file.
- Known extension conflict: Adobe Type Reunion (ATR) may cause problems for AOLpress. There is an ATR updater available:
ftp://ftp.adobe.com/pub/adobe/typereunion/mac/1.x/tyre12up.sit.hqx- Possible conflicts:
- Open Transport
FaxSTF 3.2: If you have the Control panel FaxMenu version 3.2.2 (FaxSTF 3.2 from STF Technologies), AOLpress may crash when it and the FaxMenu Control panel are enabled at the same time. The only workaround right now is to turn off this Control Panel using your Extensions Manager Control Panel.
Macintosh Easy Open Control Panel may cause random crashes while editing tables (possibly elsewhere). If you experience difficulties, try turning off (or removing if using <System 7.5) this control panel.
MacOS 7.5.2: We have had several reports of various crashes when running AOLpress. If you are running MacOS 7.5.2 you should probably take the time to install a free upgrade from Apple. In particular, AOLpress is known to crash when browsing certain sites (e.g., Web Crawler) when running on MacOS 7.5.2. This can be avoided by entering a DNS entry for the Name Server field in the Network Preferences dialog (Tools => Preferences => Network).
Ram Doubler 1.6.2 and System 7.5.3 might cause AOLpress to (screen) freeze prior to startup. Please let us know (bugs@aolpress.com) if you encounter this problem or if you find a workaround.
Note: On Power Macintoshes, the AOLpress 2.0 application needs to be in the same folder as "JgPly.PPC.shlb" (installed with AOLpress) to run correctly. If you wish to use AOLpress from your desktop or Apple Menu, create an alias. Click once on the AOLpress icon, choose File->Make Alias. Drag the alias to your System Folder->Apple Menu Items or drag it to your desktop. Just double click on the desktop to launch AOLpress.
Alternately, Power Macintosh AOLpress 2.0 users can install "JgPly.PPC.shlb" as a system extension. Drag and drop "JgPly.PPC.shlb" from the AOLpress installation folder to the System Folder of the startup drive. When prompted, click "OK" to put "JgPly.PPC.shlb" into the Extentions folder. When the Power Macintosh is restarted, the extension will be loaded.
68k Macintosh AOLpress 2.0 users can ignore this note.
4. Known Bugs
AOLpress may crash when attempting to display certain images. If you find that AOLpress crashes when attempting to display a certain page, try changing the Image Display Method in Tools->Preferences->General. In general, using the display method that displays PhotoShop4 JPG's is more stable when doing a lot of browsing and reloading of multiple pages.
When browsing pages with Frames on a 68K Mac, AOLpress may give error messages, display things incorrectly, and crash. Most problems occur when a browser window is displaying frames, then displays a non-framed page, and then displays a framed page again. AOLpress also has trouble with nested framesets on the 68K Mac.
AOLpress may crash when recursively webizing large folder structures. This is because AOLpress is running out of memory. If you have this problem you work around it by webizing smaller pieces of the folder (use the Options button in the Webize dialog).
Copy/Paste do not work in form Text Area fields.
Changing the number of colors used for display while AOLpress is running may cause a crash and force a reboot.
The Stop button is not activated when performing an Import or a Save As of a MiniWeb.
After using Edit->Make Icon from a MiniWeb view, there is no way to revert back to the default icon.
Currently, there is no direct way to remove a page as being the Stationery page for a MiniWeb. The workaround is to create a blank page then use Edit->Set Stationery to set it as the stationery page.
When creating or editing forms, the "Form Palette" used for inserting form elements, may get lost behind the page you are working in. This can be avoided by placing the Form Palette to the side of the window in which you are working.
When editing an Image Map, you can not Undo changes if you clear a shape or Clear All shapes.
Displaying ART images: The default MIME type for the .art extension is incorrect. The result is that when attempting to display ART images from a local drive, AOLpress will display the broken image icon. To correct this, change the MIME type for .art extensions to image/art in the Preferences: Extensions/MIME dialog (Tools -> Preferences -> Extensions/MIME...).
5. Notes and Hints
General Authoring
AOLpress is rather strict about enforcing legal HTML. When using AOLpress to edit pages which were created outside of AOLpress, it may change HTML which does not comply to the HTML 3.2 standard and specifications when saving it. To view a raw HTML file (before AOLpress has modified it) choose Tools -> Show HTML and File -> Reload from the Show HTML window. To save a raw HTML file (without being parsed by AOLpress) choose File -> Save As from the Show HTML window.
Editing pages with Server Side Includes (SSI): Editing pages with Server Side Includes is particularly tricky in a WYSIWYG environment. Generally if a SSI page is saved back to the server, the server parsed content is incorrectly saved in the HTML of the page. There are two ways to edit SSI pages when they are residing on an AOLserver.
1) Checking Server Side Include: Never Load in the Tools->Preferences->General dialog will cause AOLpress to display the HTML of SSI pages without the server parsed content.
2) Another way to obtain a SSI page without the server parsed content is by choosing Tools -> Show HTML and File -> Reload without SSI from the Show HTML window. You can then make changes in the HTML window, or parse and close the HTML window and make the changes in the browser/editor window and save it back to the server.
Either way, be careful when editing SSI pages from the browser/editor window, because deleting a selection that includes an SSI directive comment (which isn't displayed in the browser window) will delete the comment.Selecting text and formatting: In HTML the formatting information for a paragraph is located before the paragraph, unlike word processors where the formatting information is located at the end of the paragraph. Thus when selecting text to replace formatting, copy/paste, or drag/drop it is necessary to include the carriage return before the paragraph if you want the formatting to be included.
Netscape vs HTML 3.2. AOLpress gives you the choice of whether the display attempts to conform to the HTML 3.2 spec or to Netscape's interpretation of HTML. (There are fewer differences than existed between HTML 3.0 and Netscape's interpretation). In some cases this affects the actual HTML AOLpress generates and saves:
Tools->Preferences->General
Set to: NetscapeTools->Preferences->General
Set to: HTML 3.2Multiple Title tags allowed not allowed (removed when saved) Multiple Body tags allowed not allowed (removed when saved) <Script>...<Script> allows <Script> in the BODY forces <Script> to reside in HEAD
- ">" within quoted strings: When viewing pages with the preferences (Tools -> Preferences -> General) set to conform to Netscape, a greater than sign within a quoted string (e.g.
...VALUE=">="...) often terminates the tag even though it should not. It usually displays the rest of the tag in the page. To make the page viewable in both HTML 3.2 and Netscape mode (and generally acceptable by more browsers) the "> "should be converted to ">". This can be done by loading the page with preferences set to conform to HTML 3.2 and then saving it back or by manually making the change in the Show HTML window.
Authoring <Script>: When preferences (Tools->Preferences->General) are set to conform to HTML 3.2, AOLpress places all <Script> tags in the HEAD of the HTML document as specified in HTML 3.2. Setting the Preferences to conform to Netscape will allow you to place <Scripts> in the BODY but it is NOT recommended. Netscape's guide for authoring Java Script (their documentation may require Netscape for proper viewing) strongly suggests defining all script functions in the HEAD of the document and using event handlers embedded within tags within the BODY to call those functions.
Deleting Files from a MiniWeb: Using the MiniWeb view AOLpress allows the user to Edit=>Cut or backspace/delete an icon (subsequently deleting the object) without the presence of a confirmation dialog box.
Concurrent Editing: AOLpress when used with an AOLserver version 2.1 offers the ability to "lock" a page on a server from other editors. If "locking" is not being used and concurrent editing of the same page is occurring, changes may be overwritten. This usually happens because someone edits a cached version of a page and saves it. Be careful and use reload often if multiple people are editing the same page concurrently, especially when not using AOLserver.
Authentication and saving to a server. When saving a page to a server AOLpress saves all of the page elements as well. If you choose to cancel the authentication of a page you will still be prompted for authentication of the page elements that AOLpress is attempting to save.
To edit text or images which are links without following the link hold down the Option key and click with the mouse.
To create a MiniWeb out of a folder, or to regenerate a MiniWeb that isn't showing all of the files that it should (after moving files outside of AOLpress) use the Webize dialog by pressing Cmd-Shift-W (or choose Tools=>Webize from the MiniWeb view).
Double-click on a link to display the linked page in a new window.
Tables
Selecting (highlighting) a table in the page view requires that the paragraph before and after the table be selected. Dragging the mouse across or double clicking on a table will not highlight it but dragging the pointer from the paragraph above to the paragraph beneath (or vice-versa) will select the table.
Selecting tables within tables and tables at the end of the page: When a table is the first or last item in a table cell the table is not selectable with the mouse. This is because the selection of a table requires the selection of a paragraph before and after the table. It is easy to avoid this problem once you are aware of it. When creating tables nested within tables insert paragraphs into the table cell (by hitting Return) and place the cursor between these paragraphs when choosing Create Table. Extra paragraphs can be easily deleted later.
If you find yourself in this state, the workaround is to add a <P> tag at each end of the table you are trying to select:
- Highlight some of the table content (as a reference point) and choose Tools=>Show HTML.
The highlighted selection should be highlighted in the Show HTML window.
Insert <P> before the beginning table tag (<TABLE BORDER .....>) to insert a paragraph before the table.Insert a <P> tag immediately after the closing table tag (</TABLE>) to insert a paragraph after the table
Select Parse and Close from the file menu in the Show HTML window.
Typing in tables: Resizing tables on the fly as text is inserted is a lot of work and the typing speed in tables can be slower as a result. The more cells there are in the table, the slower the typing will be.
Lists
More than one list element on the same line occurs when there are lists nested inside a list without a paragraph tag between the list tags. This happens when Edit Complex lists is checked in the General Preferences dialog. It is impossible to insert text between two such list elements from the page view. The workaround is to manually add <P> tags after the <LI> tag in the Show HTML window.
Exiting from nested lists: AOLpress only allows one level at a time to be exited. If you wish to exit multiple nested levels, choose Format=>Exit List Format multiple times and delete the unwanted list elements when finished.
MiniWebs
If MiniWebs don't correctly show the contents of the folder, Webize the folder.
AOLpress can't tell if a MiniWeb filename has been changed outside of AOLpress. If files or links in a MiniWeb are modified outside of AOLpress, or if you ever notice that the MiniWeb view is not reflecting the true status of the folder, be sure to webize/regenerate (Tools->Webize Folder) the MiniWeb.Changing the Filetype of the MiniWeb. The file type (DOS, Mac, Posix) of a MiniWeb is determined by the general preference setting when the MiniWeb is created. AOLpress will force all files it creates or places in the MiniWeb to conform to the selected filetype restrictions.
Regenerating the MiniWeb will NOT change its file type. You must delete the document.nvd file out of the MiniWeb, and then create a new MiniWeb of the directory with the preference set to the new file type. Note also that AOLpress does not display the the document.nvd file in the list of files when browsing in the file chooser dialog - you must enter the filename manuaully. A document.nvd is present in all MiniWebsDeleting a MiniWeb deletes all of the contents in the MiniWeb.
Changing a filename in a MiniWeb
does not update links in subwebs.
does not update links in image maps
removes anchor extensions from links it changes
When editing long filenames in a MiniWeb using a list view (Name, Title, or MIME type) the file name display allows for ~27 characters. After that the text exceeds the filename box and is displayed behind the title. The workaround is to use the Web view to rename files longer than 27 characters.
Browsing for MiniWeb icons by default shows only files with .gif extension. Files of type gif, jpg, and xbm can be used for MiniWeb icons.
Miscellaneous
Opening or editing a page with a large amount of text (>100K) is very slow with AOLpress, and AOLpress will crash if given a file that is too large.
Check Links will indicate "Could not find ..." when there is a redirect at the specified URL.
The hotlist window does not have a horizontal scroll bar. To read long URLs the window may be resized larger.
Copyright © 1995-97 America Online, Inc.