OmniOutliner-Users digest, Vol 1 #161 - 17 msgs

[Brian C.]

Our macro-level plan is to move the document format completely over to 
XML, so XSLT transformations can be written by users; eventually, we'll 
add more code for folks that don't want to or can't roll their own 
solution.

In the short term, I was (and am) working on some export example 
'Scripts, but they're not done yet, because I'm pretty much learning 
AppleScript as I go along; it's just enough unlike the more traditional 
languages I do know to be semi-baffling unless I stop dead and do 
nothing else but stare at the O'Riley book.

We had a support person leave us rather unexpectedly, so we're one man 
down temporarily in the support department; keeping poor Scott from 
disappearing under waves of angry OmniWeb customers and the search for 
a replacement has been eating up a lot of time.

Additionally, Greg's new baby means that Steve's the only person 
working on Outliner at the moment. I'm sorry that this feature hasn't 
made it in there yet; we do plan to make what you're asking for 
possible, but we have other things we're working on at the moment, and 
there's only so much of us to spread around.

Sincerely,

Brian C.
Support Manager
Omni Group




On Tuesday, September 24, 2002, at 12:08  PM, 
omnioutliner-users-request at omnigroup.com wrote:

> It should be trivial to provide html export that uses headings and 
> paragraph tags
> (which is how Word/PP deal with import), but Omni still hasn't 
> provided it.

<snip>

> You just make html (and ideally, xml) export configurable.  Take a 
> look at the freeware app MacJournal (written by a single student 
> developer), which does a pretty good job here without
> any bloat.  But if you're going to argue that Omni ought not to worry 
> about this because they've got AS support, then they ought to at least 
> provide a few scripts so that AS idiots like me can have a base to 
> start from.