they whom i call Scott S. Lawton wrote:
> Jumping in: it's not crazy to use Frontier for editing, then write the
> file to disk for Python/Ruby. Many folks don't like editing text files.
>
> Or, as Matt mentioned, OmniOutliner for editing.

well, if i'm just using Frontier as an outline editor, i'd
probably choose OmniOutliner; either adds an export step, and as
i mentioned OmniOutliner can do key value pairs as columns; the
export step seems like a potential source of error however

> I haven't kept current: can Frontier still run AppleScript? If so,
> isn't that a sufficient wrapper around AppleEvents?

it can; not sure if it has the endian problems; even if it
didn't, it would be quite a mess to wrap every Apple Event call
in my complex system; i've had some experience doing that to save
time converting old scripts and it wasn't pretty; there were also
problems passing complex objects to/from the embedded AppleScripts