Your browser doesn't support Javascript.

Please follow this link for a leaner version of this website

Scriptdigital.com
Frontier Newbie Toolbox

image FNT en français

Frontier Newbie Toolbox

Table of Contents

Exploring Frontier

Get Start Tools

Web Site Management

Learning UserTalk

Edito

News

  
The "Get Start Tools"

What's on this Page :

 

These are the suites and scripts that I consider essential in the learning process of Frontier. The last one is a little bit more advanced, but you can download it now and use it later.

 

http://www.kalypso.demon.co.uk/frontier/verbi.html

To use Frontier, you need to know UserTalk, its scripting language. To know UserTalk, you need to know some of the verbs that are the foundation of UserTalk. To know those verbs, you need DocServer, which is the description of (not all but most of) the verbs that you can use in UserTalk. Unfortunately, UserLand provides DocServer only as a website that you can download (and as a downloadable Frontier source of the website). Having to load html pages just to check the syntax of a verb is, in my opinion, no fun, and take too much time. Enter Verbi from John DeLacour.

Follow the instructions on the Verbi page. You will also need to download the DocServer Frontier Source (the link is on the Verbi page). Once DocServer and Verbi are installed in your root, it works like a charm. You option-click or alt-click a verb in any editable window (script, outline, wp), and voilà, a wp window opens in Frontier with the same information that you will find in the DocServer html pages. But you will access it much faster, and you will not leave Frontier. Verbi also has a menu that follows the old version of DocServer for Frontier 4.2.3 , so its easy to access UserTalk verbs by this menu.

Another positive point in favor of Verbi is that some documentation from UserLand that you are encourage to download, like the User's Manual, links directly to DocServer on scripting.com. So while you are reading the User's Manual, you have to go on the internet to follow those links. Not in my opinion the best approach.

image of Verbi in action
 
Legend : Looking for "string.mid()" in Verbi, part of the resulting window

 

http://www.macrobyteresources.com/scripting/frontier/suites/verblist.html

An other invaluable tools is the suite VerbaList from Seth Dillingham. What Verbalist does is create an outline of the verbs that are in a specific table with all their parameters. So once Verbalist is installed in your root, put the following in the QuickScript window, run it and go take a break (it might take a while before you get the result).

verbalist.makeVerbList (@workspace.listOfVerbs, @system.verbs.builtins)

Then, put somewhere in your custom menu the following script :

edit(@workspace.listOfVerbs)

To top it all off, put a shortcut to open via your keyboard the object "workspace.listOfVerbs". You will not regret it! When I just want to check the parameters of a verb, or even if a verb exists , or just to refresh my memory (there are more than 800 UserTalk verbs!), I open the window that contains this outline. I even do a Find sometimes in this window with a word (or part of it) that I think might be contained in a verb.

image of verbalist
 
Legend : Part of an outline created by Verbalist

 

http://www.bekkoame.or.jp/~n-iyanag/Frontier/

Print is a little gem from Nobumi Iyanaga. This script will save you countless hours when writing scripts. What does print is that it "prints" the value of any variable in a script in a wp window. When you are writing a macro that is based on a script, and you want to debug it, you just have to print the result while rendering a page. Its much more easier than to follow this variable/result in the debugger while rendering.

Print is also especially useful for stringType and listType. So if you have a long string or a long list in a variable, you can "print it", from anywhere in your script. Here is a simple example that will explain the function of print. If you don't understand this script, don't bother. It's just a funny script to show you that instead of opening the debugger to see the result of the script, you can simply "print it". If you don't know what a list, a string, or the Frontier debugger are, no problemo, put print in your root and keep in one corner of your memory that you have it. When you will be ready to use print, you will see how great it is.

on doLongList() 
	local(longList = {}, tableName)
	for i = 1 to sizeOf(workspace) 
		tableName = nameOf(workspace[i])
		longList = longList + tableName
	print(longList)
	return(longList)

 

image of the debugger
 
Legend : The variable longList in the debugger

 

image of a printsheet
 
Legend : The variable longList in a printSheet

When you import print in your root, type "suites.print" at the prompt asking where the object should go.

   
 
PreviousNext Next : Web Site Management | Top
  
  

Dernière mise à jour: Mardi, le 22 juin 1999.
http://scriptdigital.com/fnt/getStartTools.html
Produit sur Macintosh.
Créé avec Frontier 5.
   

©Emmanuel M. Décarie
Création, intégration et gestion de sites webs avec Frontier.
UserLand, Frontier, and UserLand Frontier are trademarks of UserLand Software, Inc. Some of the images are © UserLand SoftWare, Inc. The Workspace.Compendium and The Frontier Newbie Toolbox are independent projects by Emmanuel M. Décarie and are not associated with UserLand Software, Inc.
Éperon