Tutorial Appendix

1. Glossay of Terms

2. Variable Naming Conventions

3. Object Database Map


 

1. Glossary of Terms

Directives

Directives are items that affect the contents of a page. They begin with a # sign and go at the top of pages, one per line. In tables, they also begin with a # sign, unless stored in the #prefs table, where the # sign is optional.

See also the Frontier site, http://frontier.userland.com/, for a list of website framework directives.

DLL

A Dynamic Link Library is an external file containing code, usually written in C or C++, that Frontier can call. On Macintosh, these are also called shared libraries. One way to extend Frontier is to write DLLs. Regex and ODBC are examples of Frontier DLLs.

DocServer

Contains documentation about Frontier's verbs, one verb per page. DocServer is on the web, at http://docserver.userland.com/

Fat Page

An HTML page with a Frontier object embedded inside it.

Filters table

A website's #filters table contains three scripts -- firstFilter, pageFilter, and finalFilter -- that allow your scripts to change the contents of the page at different steps of the rendering process.

Frontier.root

Frontier's main object database. This database contains a System table and much of Frontier's functionality.

GDB

A guest database.

Guest database

An object database other than Frontier.root that does not contain a System table.

See the New Website section of the website tutorial.

Inheritance

Directives and attributes are inherited through the object database hierarchy. For example, a page inherits its background color from the #bgcolor directive in the table above it, or the table above that, and so on. Inheritance allows for attributes and directives to be over-ridden.

See the section on inheritance in the website tutorial.

Macro

1. A Frontier script, embedded in the source of a web page or in its template, delimited by curly braces.

2. A script that is called by an embedded macro (1. above).

Object

Any item in an object database table is an object: it's a generic term for a database item.

Example use: "Edit the template object to give your site a new look."

Object database

A Frontier database, composed of tables, subtables, and various types of data.

ODB

An object database.

Prefs table

A #prefs table is a way to group table-based directives. It's not necessary to use a #prefs table, but it can be a helpful organization tool.

See the Changing Colors section of the website tutorial.

Rendering

The process of flowing a page's contents through a template, and evaluating embedded macros and glossary references. When a page is previewed or published, the page is first rendered.

Root

A root is another name for an object database. Object databases end with the file extension .root.

Return key

Windows keyboards don't have a Return key, but Mac keyboards do. On Windows this refers to the main Enter key, not the keypad Enter key.

Table

A table is an item in an object database. Tables contain various types of objects and windows -- and they can contain other tables. Tables are like folders on your hard drive.

Template

A template contains the design for a site, it's "outer" HTML. Templates are used to give a common look to your site, so that your entire site can be changed easily and quickly.

See the Editing Templates section of the website tutorial and the HowTo at the Frontier site on using multiple templates.

Tools table

The #tools table in a website contains macros, text, and outline renderers that are used in building a website.



 

2. Variable Naming Conventions

There are no rules about variable naming, other than that variable names should contain only letters and numbers.

But there are certain conventions -- not rules, but practices -- that are often followed.

The reason to follow these conventions is that it makes your code easier to read by other people. It also makes it easier to read other people's code, if they've followed the conventions.

One general convention is that variable names are inner-cased. This means that for multi-word names, the first letter is not capitalized, but the first letters of subsequent words are capitalized. A variable would be named indexCounter rather than indexcounter, IndexCounter, or some other variation.

Note that variable names are not case-sensitive: Frontier treats indexCounter and indexcounter as the same variable. The reason for inner-casing is purely for human readability.

adrPageTable, adrParamTable, pta

These usually contain the address of the current page table. The modern way is to use pta: it's shorter, saves typing.

adrXxx

Addresses usually start with an "adr" prefix, as in adrPageTable, adrItem, adrPage, or adrObject.

f

This is almost always the path to a file on the hard drive.

flXxx

Booleans usually start with an "fl" prefix, which is short for flag. An example might be flSupportsIndexing or flFound.

htmlText

htmlText is the name of a string that a website macro, outline renderer, or CGI script might return. This is a string that contains HTML text.

i, j, k

For numbers that are loop counters, one usually uses i. For a nested loop, j is used. For a loop nested inside there, k is used. And so on.

nomad

This is a "wanderer," used when traversing an object database.

objType

The type of an object, as in objType = typeOf (adrObject^).

s

Miscellaneous string variables are often, simply, s.



 

3. Object Database Map

This is a map of the shipping Frontier.root, followed by a list of frequently asked questions and answers.

Table of Contents

examples

scratchpad

suites

       appleScripts

       bbSite

       commercial

       custody

       droplet

       FilemakerLib

       finderAliases

       ftpClient

       mail

       navigator

       netUtils

       newScript

       odbEditor

       outliner

       people

       states

       webEdit

       webEditServer

system

       agents

       callbacks

       cards

       compiler

       deskscripts

       environment

       extensions

       macintosh

       menus

       misc

       paths

       shutdown

       startup

       temp

       verbs

user

       backups

       batchExporter

       betty

       callbacks

       com

       custody

       databases

       export

       html

       inetd

       log

       menus

       odbEditors

       people

       prefs

       rootUpdates

       scheduler

       webBrowser

       webEdit

       webServer

websites

       samples

       userland

workspace

       notepad

Frequently Asked Questions

examples

These are example objects of different types. Some of these are used as examples in various Frontier docs.

scratchpad

The scratchpad is for transient storage.

Items in the scratchpad don't disappear when Frontier is quit: however, it's not for permanent storage.

suites

The suites table contains mini-applications. Many suites have their own menu, and can be activated by choosing the suite's name from the Suites submenu that's in the Main menu.

suites.appleScripts

    Mac-only.

    This is a suite of utilities for managing AppleScript scripts and OSAXen in Frontier.

    See Working with AppleScript.

suites.bbSite

    Mac-only.

    This suite implements BBEdit-managed websites.

    See BBEdit and Frontier.

suites.commercial

    Mac-only.

    This suite contains utility scripts for building Frontier glue files based on an application's aete resource.

suites.custody

    This suite manages custody of odb objects, so that WebEdit and similar applications can check in and check out objects.

suites.droplet

    Mac-only.

    This suite is needed to make droplets.

suites.FilemakerLib

    Mac-only.

    A set of scripts for scripting FileMaker Pro. It's designed to be easier than using the Object Model FileMaker verbs.

    See the FilemakerLib website.

suites.finderAliases

    Mac-only.

    A small utility suite that presents an user interface for creating aliases in various locations.

suites.ftpClient

    Mac-only.

    Simplified glue for scripting Anarchie or Fetch -- FTP clients -- on Macs.

suites.mail

    Mac-only.

    A set of traps for receiving mail from Eudora and storing the mail in object databases.

suites.navigator

    Mac-only.

    A suite which implements navigators -- MacBird cards which are a sort of help system, which show people where things are.

suites.netUtils

    Mac-only.

    Utilities for managing Macintosh networks.

suites.newScript

    Mac-only.

    Presents a user interface for creating a new script: one can choose the type and location of the new script.

suites.odbEditor

    Mac-only.

    Implements external editing of objects in the root. Text files can be edited by BBEdit, MacBird cards can be edited by the MacBird card editor.

suites.outliner

    Mac-only.

    Presents a menu and interface for storing refcon data in outlines.

suites.people

    Manages users and groups. This suite is used by WebEdit to provide access control to object databases.

suites.states

    An example suite which contains a table of state names.

suites.webEdit

    This suite, the client side of WebEdit, presents a menu for check-in/check-out and remote editing of database objects (via the web, via HTTP).

    See Setting Up the WebEdit Suite.

suites.webEditServer

    The server side of WebEdit.

    See Setting up the WebEdit Server.

system

system.agents

    Agents are background tasks in Frontier.

    

system.agents.FrontierPath

        When chosen in the About Window, displays the path to Frontier.root.

    

system.agents.menuMonitor

        Calls system.menus.agent, which manages Frontier's context-sensitive menubar.

    

system.agents.minutesSinceShip

        When chosen in the About Window, displays the number of minutes since this version of Frontier shipped.

    

system.agents.schedulerMonitor

        Calls the scheduler, which manages scheduled tasks.

    

system.agents.statusMessage

        When chosen in the About Window -- as it usually is, it's the default -- displays Frontier's version, free memory, and the current date and time, and the number of current threads.

    

system.agents.webBrowserAgent

        Mac-only.

        Manages synchronization between Netscape's and IE's shared menus.

system.callbacks

    These scripts are called when certain events take place in Frontier. They also call corresponding scripts in the user.callbacks table, so that Frontier's user interface can be customized by the user.

    

system.callbacks.closeWindow

        Called when a Frontier window is closed.

    

system.callbacks.cmd2Click

        Called when text is command-double-clicked on (Macintosh) or control-double-clicked on (Windows).

    

system.callbacks.compileChangedScript

        Called when an uncompiled script window is being closed. Default behavior is to present a dialog box asking if the user wants to compile the script.

    

system.callbacks.control2Click

        Called when text is control-double-clicked on (Macintosh).

    

system.callbacks.openWindow

        Called when a window is opened.

    

system.callbacks.option2Click

        Called when text is option-double-clicked on (Macintosh) or alt-double-clicked on (Windows).

    

system.callbacks.resume

        Called when Frontier is becoming the frontmost application.

    

system.callbacks.saveWindow

        Called when a window is about to be saved.

    

system.callbacks.shutdown

        Called when Frontier is shutting down.

    

system.callbacks.startup

        Called when Frontier is starting up.

    

system.callbacks.suspend

        Called when Frontier is stopping being the frontmost application.

system.cards

    Mac-only.

    Contains MacBird cards that are part of the user interface on Macintosh.

system.compiler

    This table is maintained by the Frontier application: it's not supposed to be edited by the user.

    

system.compiler.cards

        Contains the address of the active card.

    

system.compiler.kernel

        Contains tokens used by the compiler.

    

system.compiler.language

        Contains constants and tokens used by the language.

    

system.compiler.stack

        Contains the stack which can be viewed while debugging.

    

system.compiler.semaphores

        The list of current semaphores.

    

system.compiler.threads

        The list of current threads.

    

system.compiler.files

        The list of currently-open Frontier files. Contains references to their contents.

system.deskscripts

    The path to the current desktop script is stored at system.deskscripts.path.

    See the page on Desktop Scripts.

system.environment

    Contains data about the machine Frontier is running on.

    

system.environment.isMac

        True if the machine is a Macintosh, false otherwise.

    

system.environment.isWindows

        True if the machine is a Windows machine, false otherwise.

    

system.environment.osMajorVersion

        The major version number of the operating system.

    

system.environment.osMinorVersion

        The minor version number of the operating system.

    

system.environment.osVersionString

        The entire version number of the operating system.

    

system.environment.osFullNameForDisplay

        The full name, for display use, of the operating system.

system.extensions

    Contains UCMDs, XCMDs, DLLs, and their glue scripts.

    (Note: beginning with Frontier 6, it's preferable to store such items in guest databases, but it's not required.)

    This table ships empty on Windows. On Macintosh, it contains:

    

system.extensions.finderFlags

        Mac-only.

        UCMD and glue for setting Finder info bits on Macintosh.

    

system.extensions.forks

        Mac-only.

        UCMD and glue for manipulating resource and data forks of Macintosh files.

    

system.extensions.ic

        Mac-only.

        UCMD and glue for getting and setting Internet Config preferences on Macintosh.

    

system.extensions.jump

        Mac-only.

        UCMD and glue for running a dialog similar to the Macintosh Jump dialog. (It's an early version of the Jump dialog, which is now implemented as a MacBird card.)

    

system.extensions.latinToMac

        Mac-only.

        UCMD and glue for converting Latin-encoded text to Mac-encoded text. This is used mainly in CGIs and dynamic pages.

    

system.extensions.listSelect

        Mac-only.

        XCMD and glue for implementing a list selection dialog box.

    

system.extensions.locker

        Mac-only.

        UCMD and glue for implementing a locked user interface.

    

system.extensions.loginAs

        Mac-only.

        UCMD and glue for logging into a remote volume.

    

system.extensions.logout

        Mac-only.

        UCMD and glue for logging out of a remote volume.

    

system.extensions.passwordDialog

        Mac-only.

        UCMD and glue for presenting a password dialog.

        (Use dialog.getPassword instead.)

    

system.extensions.pbs

        Mac-only.

        UCMD and glue for miscellaneous string and list processing.

    

system.extensions.StuffItCmd

        Mac-only.

        UCMD and glue for stuffing and expanding StuffIt archives.

    

system.extensions.syslargestblock

        Mac-only.

        UCMD and glue for returning the system's largest block.

    

system.extensions.trigCmd

        Mac-only.

        Math functions: sines and cosines, etc.

    

system.extensions.wordInfo

        Mac-only.

        Sample UCMD and glue for manipulating words in strings.

system.macintosh

    Mac-only.

    Contains constants and scripts used in the Macintosh version of Frontier only.

    

system.macintosh.constants

        Various constants used in Apple events.

    

system.macintosh.core

        Core Apple events verbs.

    

system.macintosh.globals

        Apple events verbs.

    

system.macintosh.misc

        More Apple events verbs.

    

system.macintosh.objectModel

        Constants used by Object Model Apple events calls.

    

system.macintosh.required

        The four required Apple events verbs.

system.menus

    This table contains Frontier's main and Help menus, shared menus, and scripts that menus call.

    

system.menus.agent

        This is called from system.agents.menuMonitor.

        This script manages Frontier's context-sensitive menubar.

    

system.menus.buildMenuBar

        Builds Frontier's menubar.

    

system.menus.buildSuiteSubMenu

        Manages the Suites submenu in the Main menu.

    

system.menus.data

        Contains information about the current installed suite and the type of the frontmost window.

    

system.menus.helpMenu

        Frontier's Help menu.

    

system.menus.menuBar

        Frontier's main menubar.

    

system.menus.modals

        Contains menus that appear based on the type of the frontmost window.

    

system.menus.scripts

        Contains scripts that various Frontier menu items call.

    

system.menus.sharedMenus

        Mac-only.

        Contains shared menus for applications that support menu sharing.

    

system.menus.swapInSuite

        This script is called from the Suites submenu items. It removes the current suite from the menu bar and installs a new one.

    

system.menus.virginSuitesMenu

        This is an empty copy of the Suites submenu.

system.misc

    Windows-only.

    No objects other than the below should be stored in this table.

    

system.misc.com

        Contains the address of the COM-exposed methods table, usually user.com.

system.paths

    This table contains the paths Frontier searches when resolving an address.

system.shutdown

    When Frontier is shutting down, all scripts in this table are called. However, users should not store shutdown scripts in this table, but instead store them in user.callbacks.shutdown.

system.startup

    When Frontier is starting up, all scripts in this table are called. However, users should not store startup scripts in this table, but instead store them in user.callbacks.startup.

system.temp

    This table is for temporary storage. This table is empty when Frontier starts up, as items in this table are never saved to disk.

    Several Frontier applications, such as mainResponder, use this table to store temporary data.

system.verbs

    

system.verbs.apps

        Glue scripts for scripting other applications.

        On Windows this ships empty, but on Macintosh it contains glue for web browsers, FTP clients, BBEdit, FileMaker, Eudora, WebSTAR, and more.

    

system.verbs.builtins

        This table contains most of Frontier's built-in verbs.

        See the DocServer website for documentation.

        Highlights of this table include:

            system.verbs.builtins.html: website framework

            system.verbs.builtins.webserver: webserver framework

            system.verbs.builtins.inetd: TCP server framework

            system.verbs.builtins.tcp: TCP scripting verbs

            system.verbs.builtins.xml: XML verbs

    

system.verbs.colors

        This contains a table of colors with their hex values.

    

system.verbs.constants

        Constants used in scripts: lf, cr, tab, and the names of the months in English.

    

system.verbs.globals

        "One-word" Frontier verbs, such as getBinaryType, edit, msg, and so on.

        See DocServer.

    

system.verbs.traps

        Mac-only.

        Apple event handlers. This is the Macintosh equivalent of user.com.

        CGI events are handled by system.verbs.traps.www[omega].sdoc.

user

The user table contains preferences and data.

user.backups

    Preferences for backing up Frontier.root.

user.batchExporter

    Batch Exporter preferences.

user.betty

    

user.betty.prefs

        XML-RPC preferences.

    

user.betty.rpcHandlers

        XML-RPC handlers.

user.callbacks

    

user.callbacks.closeWindow

        These scripts take one parameter, a title. The title parameter is the full path to window's file, or window name if unsaved. If this script returns false, Frontier does not close the window.

    

user.callbacks.cmd2Click

        These scripts take one parameter, a name. This is the callback for control-2Clicking in Windows or command-2Clicking on the Macintosh. Name is the string that was double-clicked.

    

user.callbacks.compileChangedScript

        These scripts take one parameter, the address of the script that is not compiled. This script is called by Frontier before closing a script window that has been edited. Return true to have Frontier compile the script before closing the window.

    

user.callbacks.control2Click

        These scripts take one parameter, the string that was selected. On Macintosh this is called when a control-double-click is performed. This isn't used on Windows -- use user.callbacks.cmd2Click instead.

    

user.callbacks.openWindow

        This script takes one parameter, the name of the window being opened. Unlike the closeWindow callback, openWindow is called for all opens, even when script generated. Also unlike closeWindow, an openWindow callback cannot prevent the window from opening. It can hide it to keep it invisible, or change its title before it's shown.

    

user.callbacks.option2Click

        Handles alt-2clicks on Windows and option-2clicks on Macs.

    

user.callbacks.resume

        Called when Frontier moves to the foreground. These scripts take no parameters.

    

user.callbacks.saveWindow

        These scripts take two paramaters, the path to the window to save and a flag saying whether or not the window should be saved as a runnable desktop script. The path parameter is the full path to window's file, or window name if unsaved. Frontier calls this script to save file objects. The return value should be the (packed) data to be written to disk (by Frontier).

    

user.callbacks.shutdown

        Called when Frontier quits. These scripts take no parameters.

    

user.callbacks.startup

        Called when Frontier starts up. All of these scripts run to completion before agents start running. These scripts take no parameters.

    

user.callbacks.suspend

        Called when Frontier is moved from being the foreground application. These scripts take no parameters.

user.com

    Windows-only.

    Frontier scripts exposed to COM via Frontier's COM server.

user.custody

    Storage for suites.custody.

    

user.custody.prefs

        timeOutMinutes: how long until a custody lock expires

    

user.custody.objects

        The list of currently checked out objects.

user.databases

    Preferences for guest databases.

    See the page on user.databases.

user.export

    Preferences for exporting and importing Frontier objects.

user.html

    Website framework preferences and storage.

    

user.html.changedPages

        An outline, the list of changed pages.

    

user.html.editors

        Obsolete.

    

user.html.fileWriters

        Custom fileWriters.

        See: http://discuss.userland.com/msgReader$1098

    

user.html.glossary

        The global website glossary.

    

user.html.images

        The global images table.

    

user.html.macroErrors

        An outline, a list of macro errors, if your prefs specify logging to this outline.

    

user.html.macros

        Global website macros. User-written macros that are used in multiple websites can be stored here.

    

user.html.menu

        Preferences for the HTML menu.

    

user.html.prefs

        The top level of the #directives hierarchy.

    

user.html.renderers

        Outline renderers. User-written renderers may be stored here as well as UserLand-supplied renderers.

    

user.html.sites

        FTP sites. This is largely obsolete: use the #ftpSite directive instead to store site location information.

    

user.html.templates

        Website templates. This is largely obsolete: use the #template object and #templates table in your websites to store templates.

user.inetd

    

user.inetd.config

        Settings for inetd servers. Frontier ships with an HTTP server that's configured in this table, at user.inetd.config.http.

    

user.inetd.listens

        Table of open listens for inetd servers. This table is maintained by Frontier and shouldn't be edited.

    

user.inetd.prefs

        Global inetd server prefs.

    

user.inetd.shutdown

        Frontier maintains this flag: when it's set to true, all inetd servers are stopped.

user.log

    Logs.

    

user.log.outlines

        If your preferences specify that logging should go to outlines, then those outlines are stored in this table.

    

user.log.prefs

        Preferences for logging.

user.menus

    User menus.

    

user.menus.bookmarkMenu

        Your Bookmarks menu.

    

user.menus.customMenu

        The custom menu, the one that bears the initials of the user.

user.odbEditors

    Preferences for editing Frontier objects in external applications such as BBEdit and the MacBird card editor.

user.people

    Storage for the People suite's users, groups, and services.

    This should not be edited directly, but rather via the People verbs and the People based web-admin.

user.prefs

    Various user preferences.

    

user.prefs.agentsEnabled

        True if agents are running.

    

user.prefs.appendFileSuffixes

        Append file suffixes when exporting Frontier objects. (Mac-only.)

    

user.prefs.commonStyles

        Settings for the Main menu's Common Styles submenu.

    

user.prefs.dates

        Contains a list of month names in English.

    

user.prefs.dialogs

        Storage for various dialog boxes.

    

user.prefs.firstRootRun

        True if this is the first time this copy of Frontier has been launched.

        Don't set this to true.

    

user.prefs.fonts

        Default font settings for new objects.

    

user.prefs.frontierIsServer

        Obsolete. Specifies to log to the file system rather than to outlines.

    

user.prefs.initials

        The user's initials.

    

user.prefs.mailAddress

        The email address of the user.

    

user.prefs.mailHost

        The SMTP mail host of the user.

    

user.prefs.name

        The user's name.

    

user.prefs.openAboutWindow

        A boolean: if true, the About Window is opened on startup.

    

user.prefs.search

        Preferences for the Find dialog box.

    

user.prefs.serialNumber

        The Frontier serial number. If this is the Trial version, it will be empty.

    

user.prefs.textEditorApp

        The path to the external text editor.

user.rootUpdates

    Preferences for root updates.

    

user.rootUpdates.servers

        Subtables for each database that the user subscribes to.

user.scheduler

    Settings for Frontier's built-in scheduler.

    

user.scheduler.everyMinute

        Tasks that run every minute.

    

user.scheduler.hourly

        Task that run once an hour.

    

user.scheduler.log

        The scheduler log.

    

user.scheduler.overnight

        Tasks that run once a night.

    

user.scheduler.prefs

        Scheduler preferences.

    

user.scheduler.tasks

        The main scheduler tasks table.

user.webBrowser

    Preferences for web browser scripting.

    Also includes user.webBrowser.proxy, proxy settings for Frontier's HTTP client (tcp.httpClient).

user.webEdit

    WebEdit preferences.

    

user.webEdit.prefs

        Contains the name of the current server.

    

user.webEdit.servers

        Preferences for servers the user has access to via WebEdit.

user.webServer

    Settings, data, and scripts for Frontier's webserver framework.

    

user.webserver.actions

        Action scripts -- used when running Frontier behind a Mac OS server such as WebSTAR.

    

user.webserver.callbacks

        Callbacks that allow for filtering of .fcgi -- classic, old-style -- CGI scripts.

    

user.webserver.cgis

        Table of storage for .fcgi CGIs.

    

user.webserver.postFilters

        Filters that run after a request has been run.

    

user.webserver.preFilters

        Filters that run before a request is handled.

    

user.webserver.prefs

        Global webserver preferences.

    

user.webserver.realms

        Username and password protection via realms.

    

user.webserver.responders

        Webserver responders -- scripts that handle incoming HTTP requests and build a response.

    

user.webserver.stats

        Statistics about the webserver: number of hits and so on.

    

user.webserver.utilities

        User storage for utility scripts relating to the webserver.

websites

The websites table contains website source. With Frontier 6, it's recommended that websites are stored in guest databases, in the www folder that's in the Guest Databases folder. However, you may continue to use the websites table to store websites.

websites.samples

    Sample pages that show some of the features of the website framework.

websites.userland

    A small sample site, an earlier version of www.userland.com, that demonstrates some website framework concepts and features.

workspace

The workspace is the user's space for scripts and data. Unlike the scratchpad or system.temp table, it's safe to store items here permanently.

With Frontier 6, it's recommended that you store your scripts and data outside Frontier.root, in guest databases. However, you may continue to use the workspace table.

workspace.notepad

    This is an outline, the user's notepad.

    To open it, type ctrl-Y (Windows) or cmd-Y (Macintosh).

Frequently Asked Questions

How can I jump to a location in Frontier.root?

    Use the Jump command, ctrl-j (cmd-j on Macs), and type in the dialog box the address you want to jump to.

Where can I find documentation about Frontier verbs?

    DocServer: http://docserver.userland.com/

Where is the website framework?

    system.verbs.builtins.html

Where are Frontier's website macros?

    Frontier macros such as imageRef, frontierLogo, and so on are stored at html.data.standardMacros.

    Other macros are stored at user.html.macros -- and you can store your own macros here, too, as well as in your websites themselves.

Where are outline renderers?

    Frontier's built-in outline renderers are stored at user.html.renderers. You can store your own renderers here, too, or in the #tools table of your websites.

Where is the webserver framework?

    system.verbs.builtins.webserver

Where are XML-RPC handlers stored?

    user.betty.rpcHandlers

Where are the TCP verbs?

    system.verbs.builtins.tcp

Where are the XML verbs?

    system.verbs.builtins.xml

Where do I put my websites?

    The recommended location is in a guest database in the www folder that's in the Guest Databases folder. You can also store them in the websites table at the top level of Frontier.root.

Where is the People suite's web admin website stored?

    people.webAdmin

Where is Frontier's menubar?

    system.menus.menubar

Where is the HTML menu?

    html.menu.theMenu

Where is the Help menu?

    system.menus.helpMenu

Where do I go to edit my custom menu?

    user.menus.customMenu

Where do I go to edit my Bookmarks menu?

    user.menus.bookmarkMenu

Where do I set my proxy server settings?

    user.webBrowser.proxy

How can I compact Frontier.root?

    Save A Copy.

Where do I put my scripts?

    It depends on what type of scripts they are. Website scripts go in the #tools table of your websites. Other types of scripts may be stored in the workspace table. You can also create suites of related scripts and store them in the suites table. You can store scripts in your own guest databases.

Where do glue scripts for applications go?

    system.verbs.apps

Where do shared menus go?

    system.menus.sharedMenus (Mac-only.)



Copyright 1992-2002 UserLand Software, Inc..