Alternative HTML output
A Borg
igpop at cs.tu-berlin.de
Wed Jan 26 08:50:47 PST 2005
On 26.01.2005, at 17:02, Ryan Poling wrote:
> On Jan 26, 2005, at 7:18 AM, Philip King wrote:
>
>>
>> On Wednesday, 26 January, 2005, Adam Lindsay said:
>>
>>> However, I think there are a bunch of different interpretations
>>> of what the output structure could be. I, personally, would
>>> want the rows to be <h1>..<h6> headings, and the notes to be
>>> <p> paragraphs. I can see nested definition lists accommodating
>>> rows and lists, as well.
>>
>> Those are indeed good alternatives. In view of the increasing push
>> towards cleaner and more meaninfully structured HTML, creating the
>> sort of output OO currently produces would seem to buck the trend.
>>
>> - Philip
> I wonder if the simple HTML output could be done with an Applescript?
> I also agree that this would be a good idea, although I *do* actually
> like the current option of having the output look as close to the
> original as possible. It's very handy for quickly sticking an outline
> on a web page to share with others.
>
> -Ryan
>
I wonder if it wasn't possible to just edit the CSS included in the
html file. On first look,
OO does a mix of global styles defined in the header section, and
direct formatting via "style=" attributes
inside of tags.
If the generic html structure was clear, one could with not much effort
restructure the html so that the
inclusion of a different CSS would reformat the whole outline. In the
long term, if OO could separate
content (html) from presentation (css), this would be even easier.
For an impression of what is possible with such an approach, see
<http://csszengarden.com>: one html file,
and many css files, one more beautiful than the other.
Just a thought, Kei.
More information about the OmniOutliner-Users
mailing list