[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Orgmode] export and containers
From: |
Richard Riley |
Subject: |
Re: [Orgmode] export and containers |
Date: |
Mon, 02 Mar 2009 19:12:45 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.0.91 (gnu/linux) |
Carsten Dominik <address@hidden> writes:
> On Mar 2, 2009, at 5:00 PM, Sebastian Rose wrote:
>
>>
>> OK - I failed badly :-(
>>
>> I think we can skip the extra <div> element around the TOC.
>>
>> Here's why:
>>
>> As it looks now, the problem with the fixed TOC does not go away. My
>> old trick seems to work only for HTML doctype and/or tables...
>> Should
>> have tested that one before...
>>
>> So until now it's not getting any better - but more complicated.
>>
>> And all those stlyes in the stylesheet become confusing :-/
>>
>> The main problem is the height of the TOC on orgmode.org. The <div>
>> element grows and shrinks in height when we resize the window.
>> Unfortunately, we can't set the height property to 100% because of
>> the
>> unicorn. Instead I set it to 60% to support Netbooks - but 60% will
>> be
>> too high if the window is resized to be under a certain height. And
>> 60% is low, if the window fills a bigger screen (> 17')
>>
>> Seems I can't solve that by adding structural elements. The only
>> element I could think of would be a table with height=100% and the
>> unicorn in the first row (fixed height), TOC in the second row (no
>> height property).
>>
>>
>> Most of this seems to be true for the other containers I thought of.
>>
>>
>> Just one around everything and one around the all the sections and
>> footnotes seems to make sense so far.
>
>
> So one that wraps everything in body. OK, let's call it "content".
>
> And then one that does contains the sections and footnotes, but
> not the title, preamble, and postamble? Am I understanding this
> correctly?
>
> - Carsten
So long as every thing has a div we can then use descendants of the main
content to CSS any elements.
I see the most important thing (and making it simple) is just to assign
a class ID at the org file level
#class=myclass
..stuff
#endclass
This generates
<div class="myclass">
..stuff
</div>
at html export and whatever for anything else.
I really dont see the plethora of sec-id# that are currently generated
being really useful since they change on each export if new stuff is
entered. This make existing CSS redundant unfortunately.
Sebastian?
- Re: [Orgmode] export and containers, Richard Riley, 2009/03/02
- Re: [Orgmode] export and containers, Sebastian Rose, 2009/03/02
- Re: [Orgmode] export and containers, Carsten Dominik, 2009/03/02
- Re: [Orgmode] export and containers, Sebastian Rose, 2009/03/02
- Re: [Orgmode] export and containers, Carsten Dominik, 2009/03/02
- Re: [Orgmode] export and containers, Sebastian Rose, 2009/03/02
- Re: [Orgmode] export and containers, Carsten Dominik, 2009/03/02
- Re: [Orgmode] export and containers,
Richard Riley <=
- Re: [Orgmode] export and containers, Sebastian Rose, 2009/03/02
- Re: [Orgmode] export and containers, Richard Riley, 2009/03/02
- Re: [Orgmode] export and containers, Sebastian Rose, 2009/03/02
- Re: [Orgmode] export and containers, Richard Riley, 2009/03/02
- Re: [Orgmode] export and containers, Carsten Dominik, 2009/03/03
- Re: [Orgmode] export and containers, Sebastian Rose, 2009/03/03
- Re: [Orgmode] export and containers, Carsten Dominik, 2009/03/03
- Re: [Orgmode] export and containers, Sebastian Rose, 2009/03/03
- Re: [Orgmode] export and containers, Sebastian Rose, 2009/03/02
- Re: [Orgmode] export and containers, Sebastian Rose, 2009/03/02