emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastian Rose <sebastian_rose@gmx.de>
To: Richard Riley <rileyrgdev@googlemail.com>
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: export and containers
Date: Mon, 02 Mar 2009 10:29:03 +0100	[thread overview]
Message-ID: <87vdqsz31c.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <49ab92ef.0407560a.4681.543e@mx.google.com> (Richard Riley's message of "Mon, 02 Mar 2009 09:03:58 +0100")

Richard Riley <rileyrgdev@googlemail.com> writes:
> Sebastian Rose <sebastian_rose@gmx.de> writes:
>
>> Richard Riley <rileyrgdev@googlemail.com> writes:
>>> It's been a while since I've looked at my org set up. One thing that
>>> always struck me as a bit hacky was my use of
>>>
>>> :preamble "<div id='content'>
>>>
>>> and the corresponding postamble to enclose the exported web pages into a
>>> "container" div. Is there a better way to do this? I would think it
>>> would be a common enough need that by default or via an option all html
>>> should be enclosed in a "webcontainer" ID.
>>
>> While one container around everything makes it possible to center the
>> page horizontally, two containers make it possible to center the page
>> vertically as well.
>>
>> If we would go and change the structure once again, I'd even suggest the
>> following:
>>
>> <body>
>>   <div id="percent-50">         -- center the page if desired
>>     <div id="wrap">             -- center the page if desired
>
> Why always IDs as opposed to classes?


`percent-50' and `wrap' are there for a special purpose and unique in
that concern. `wrap' is the `content' you originally requested. I did
not use my brain and called it `wrap' without any annotation.

>>> :preamble "<div id='content'>

I'd say they should have an ID assigned.



> Can css selectors select based on a part of a name? If not then there is
> no link between column-1 and column-2. e.g in this convention how does
> one create a common style for all columns or all "sec-" objects?

Aaah, OK, sorry for being unclear - a misunderstanding.

I did *not* mean to _change_ the structure of the XHTML in it's current
form, but simply _add_ additional containers to partition the whole
thing (just as you suggested) and thus make it possible to move certain
groups of content around through CSS.

All the "sec-" objects should go into `column-2'.
All the `sec-' objects share classes via the containers they live in:

    <div id="outline-container-2" class="outline-2">
    <div id="outline-container-2.1" class="outline-3">

etc.

That's already the case, and I think we don't need to change that.


* Suggestions for names

  `wrap' is, what they use in typolight and some other CMSs. But
  `content' sounds good to me too.

  <div id="center">
    <div id="wrap"><!-- or `content' -->

      <div id="box-1">
        <div id="table-of-contents">
         ...
        </div>
      </div><!-- end of box-1 -->

      <div id="box-2">
        <div id="outline-container-2" class="outline-2">
          <h2 id="sec-1"><span class="section-number-2">2</span> Konfiguration </h2>
          <div class="outline-text-2" id="text-2">
           ...
          </div>
        </div>
        ... more sections, footnotes ...
      </div><!-- end of box-2 -->

      <div id="postamble">
        postamble
      </div>


    </div><!-- end of wrap -->
  </div><!-- end of center -->



>>
>>       <div id="column-1">       -- Help with fixed TOC
>>         <div id="table-of-contents">
>>           the toc
>>         </div>
>>       </div>
>>
>>       <div id="column-2">       -- Help with fixed TOC
>>         All the rest of the content goes here
>>       </div>
>>
>>       <div id="postamble">
>>         postamble
>>       </div>
>>
>>     </div>
>>   </div>
>> </body>
>>
>>
>>
>> Having two boxes for the TOC would make the fixed TOC work in IE. In
>> general, I prefere to use two kinds of Boxes:
>>
>>   - one for positioning, floating and so on. This one should have _no_
>>     padding or margin at all!
>
> Can one not simply use .body for that?
>
>>   - one for margin, padding, styling.
>>
>> I found, this is the only way to reliably enforce a layout across
>> browsers.
>>
>>
>> column-1 and column-2 are for that very reason. All we can do to put the
>> TOC to the left or right is, to add margins to the body or the level 1
>> contents, and place it there. This is, what causes the problems with the
>> fixed TOC in IE. `column-1' and `column-2' (and `postamble') make it
>> possible, to adjust the layout in various common ways.
>>
>> The `percent-50' (oh what a name) and `wrap' are just there, to be able
>> to center the whole page horizontally _and_ veritcally.
>
>>
>>
>> Best,
>>
>> --
>> Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
>> Tel.:  +49 (0)511 - 36 58 472
>> Fax:   +49 (0)1805 - 233633 - 11044
>> mobil: +49 (0)173 - 83 93 417
>> Http:  www.emma-stil.de
>>

--
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.rose@emma-stil.de, sebastian_rose@gmx.de
Http:  www.emma-stil.de

  reply	other threads:[~2009-03-02  9:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-28 10:29 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 [this message]
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
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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vdqsz31c.fsf@kassiopeya.MSHEIMNETZ \
    --to=sebastian_rose@gmx.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=rileyrgdev@googlemail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).