From: Richard Riley <rileyrgdev@googlemail.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: org-mode <emacs-orgmode@gnu.org>,
Richard Riley <rileyrgdev@googlemail.com>
Subject: Re: export and containers
Date: Mon, 02 Mar 2009 19:12:45 +0100 [thread overview]
Message-ID: <49ac219e.0305560a.1bac.ffffac65@mx.google.com> (raw)
In-Reply-To: <8296CDBB-B545-4819-99A5-58EDD20DC7DC@uva.nl> (Carsten Dominik's message of "Mon, 2 Mar 2009 18:03:47 +0100")
Carsten Dominik <dominik@science.uva.nl> 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?
next prev parent reply other threads:[~2009-03-02 18:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 10:29 export and containers Richard Riley
2009-02-28 11:37 ` Sebastian Rose
2009-02-28 19:23 ` Carsten Dominik
2009-02-28 21:09 ` Sebastian Rose
2009-03-02 8:03 ` Richard Riley
2009-03-02 9:29 ` Sebastian Rose
2009-03-02 11:11 ` Carsten Dominik
2009-03-02 11:58 ` Sebastian Rose
2009-03-02 13:10 ` Carsten Dominik
2009-03-02 16:00 ` Sebastian Rose
2009-03-02 17:03 ` Carsten Dominik
2009-03-02 18:12 ` Richard Riley [this message]
2009-03-02 18:56 ` Sebastian Rose
2009-03-02 20:22 ` Richard Riley
2009-03-03 0:52 ` Sebastian Rose
2009-03-03 1:16 ` Richard Riley
2009-03-03 10:02 ` Carsten Dominik
2009-03-03 10:14 ` Sebastian Rose
2009-03-03 10:50 ` Carsten Dominik
2009-03-03 10:57 ` Sebastian Rose
2009-03-02 19:03 ` Sebastian Rose
2009-03-02 18:54 ` Sebastian Rose
2009-03-02 19:06 ` Sebastian Rose
2009-03-02 14:38 ` Richard Riley
2009-03-02 16:50 ` Sebastian Rose
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49ac219e.0305560a.1bac.ffffac65@mx.google.com \
--to=rileyrgdev@googlemail.com \
--cc=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.