What is Bayly root?

Bayly.root is how I ship my public domain contributions to the Userland community.

It contains a slowly increasing number of suites, Manila plug-ins and other useful goodies. All software is shipped as-is , no warranty is implied.

You can download here. It is about 3.5MB in a zipped format.

To install the root, place the unstuffed file in the apps folder in the Guest databases folder, double click the root to open it and run the #installer script. Frontier will thereafter open the root at every launch.

To make use of the individual items in the root, you will need to investigate the tables in the root and the documentation (limited but growing slowly) on this web site. The more high profile plug-ins such as manilafixer and commentit have in-line documentation.

Manila plugins must be installed, according to the Userland guidelines, they have an install script which must be run before they are visible to the Managing Editors of web sites thru the editors only menu (prefs -> plugins). Once visible the Managing Editors can choose to enable or disable them for use in their web sites. Visible plugins typically have an entry in the editors only menu once enabled.

As of August 16th, 2001 the root update mechansinm has been activated. Before using the root update, please download the current version.

As of Sunday 21st May, 2006 the root is shipped in a zipped format.

--David Bayly(dbayly at udena dot ch) from UK on 2/5/02; 10:18:13 AM [permalink]
This is a test comment for Jim.

--Peter Chapman(pchapman at pobox dot com) from USA on 5/16/01; 3:33:00 AM [permalink]
Thanks for your generous contributions to your fellow frontier users - very much appreciated.

I have just tried to download the latest copy of Bayly.root.sit to find that the file does not exist - is it still available?

Finally, you may be able to answer my question directly - I am having difficulty using glueFactory woth Frontier 7 Beta for OSX and FileMaker Pro 5.5. Specifically, glueFactory Reports an error "The file FileMaker Pro.app" wasn't found". It appears to have imported the required events before it fails. Frontier's built-in suite fails in a similar fashion.

Any ideas?

Cheers, Peter