Frontier Page

Note: This section of my site, like Frontier itself, is basically defunct and is retained only for historical reasons.


Other pages relating to Frontier at this site. Stuff is slowly being added.

Various Notes

Mail2FM Status

The currently shipping version of Mail2FM is 1.6.7. This version fixes another bug in the non-regex digest processing code that caused problems with digests that did not have a blank line after the delimeter. Also fixed a bug where the default date and time where not being set correctly.

After much procrastination, I’ve finally begun actually writing code for Hydra, the next major version of Mail2FM. I’m also writing notes on the new modular plug-in architecture, so that other people will be able to write plug-ins for clients I don’t intend to support personally, such as Mailsmith. Once I’ve got the notes into some sort of coherent order, I’ll put them up here.

Wish List

These are ideas for the things to add in future versions of Mail2FM. Some of these are my idea, some were suggested by others. The order of this list does not necessarily reflect the priority I give to the items.

Add support for Outlook Express. (Requested by Anthony Wilson.)
This doesn’t look like it will be too terribly hard, and since somebody else asked for it, I’m giving it the highest priority.
Redo the suite’s architecture to use some sort of plug-in system for the various clients.
I think this will be necessary to keep the suite from becoming a total mess as support for OE and other clients is added. The current Mail2FM architecture was only intended for a single mail client, and the more I add the harder it will be to maintain and improve the code. This is a pretty high priority item, because the sooner it gets done the less work there will be to convert the existing scripts. You may be interested in my design notes on the new architecture.
Add a way to automatically import all mailboxes into the Filemaker database. (Requested by Aadjan van der Helm.)
This would allow people to easily export the entire contents of their mail client’s database into the FMP database.
Replace the MacBird cards with custom dialogs.
The MacBird card used to create new tasks has been a real pain. An undocumented change in Frontier 5 caused a serious bug with Eudora, and another such change probably caused a second bug, and the card editor is so unstable that it crashes nearly every time I use it. However, the excellent explanation of custom dialogs in Frontier: The Definitive Guide should be enough for me to replace these troublesome cards with real dialogs.
Support ’eNot’ triggering of message imports.
The ’eNot’ event can be sent by Eudora and Emailer to applications that have registered to recieve them. Every time a message comes in, the event is sent with information on the message. Adding support for importing messages based on an ’eNot’ event would allow the entire importing process to be automatic.
Support message importing from a Newton.
I own a MessagePad 2100, and I’d like to be able to easily move mail from it into Mail2FM. This is a pretty tough one, but there are some third-party tools that may make this possible. Anyway, this is not as high priority as most of the things on this list since I only know of two Newton owners who use Mail2FM (including myself).
Add support for Mailsmith (from Bare Bones Software).
This has finally shipped, and it does indeed have good scripting support. However, I don’t actually like it much, so probably I’ll leave support to someone else through the plug-in architecture.
Allow plug-ins to provide custom handling of certain messages.
This idea was inspired by a request to add support for an unusual custom digest format.
Support importing of single messages saved as text files. (Requested by John Nicholas.)
This would provide a “lowest denominator” import option.

Other Stuff

Printable Versions of Web Pages

I’ve seen sites that have a link to a printable version of each article, where the nav bar and other such things are absent. This would be really nice for some things I’m working on, so I’ve been thinking about how to do it in Frontier. My first thought was a macro that when called while rendering the “fancy” page, would go off and render the “plain” page and then insert a link to it. On further consideration, I don’t think this will work. Anyway, if I figure something out I’ll post it.