MCP Support for TinyFugue

After experiencing the joys of local editing with tkMOO-lite, I decided I must have local editing for TinyFugue. I checked out the existing local editing for TF by Brandon Gillespie and Stephen Sayer, mcpedit.tf, but didn't like the fact that TinyFugue was unavailable during local editing. The other major shortcoming was a lack of real MCP support -- the triggers simply rely on the keyword/value pairs to be laid out in a particular order, which is not guaranteed by the MCP spec.

Real MCP Support

I wrote a new set of TinyFugue macros to implement MCP support (for any request with arbitrary keyword/value pairs) and a set of macros to provide local editing with that support. In the comments I also show how you could add gopher support with a one-line macro.

To take advantage of this you'll need a pretty recent version of TinyFugue. You can find the latest versions available for ftp. You'll need a MOO that speaks MCP, which I'm told does not include LambdaMOO itself. Make sure your /addworld includes -Ttiny.moo on your MOO worlds (the triggers are limited to this world type). You may need to execute /mcp_login if the macros aren't loaded when you connect to your MOO.

Features of the Editing Support

In environments that support it, you can do background editing -- TinyFugue continues to run while you edit. Under X Windows the default action is to start an XTerm running your editor. Under screen the default action is to start your editor in a new screen window. If you're not running under screen or X the editor will be run in the foreground and you will not be able to continue using TF while editing.

If you are using background editing, you can have as many editing sessions as resources allow. At any time, /mcp_reedit (alisesd to the shorter /reedit) will re-invoke your editor on the last file uploaded to the current world.

Get the Macros

Go get the macros, try them out, and let me know how they work for you.
[Ben Jackson's Home]