From: Nick Dokos <nicholas.dokos@hp.com>
To: =?utf-8?Q?=C5=81ukasz?= Stelmach <lukasz.stelmach@iem.pw.edu.pl>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Re: [BUG] define "just", preamble and postamble placement
Date: Fri, 08 Oct 2010 03:46:59 -0400 [thread overview]
Message-ID: <31670.1286524019@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from =?utf-8?Q?=C5=81ukasz?= Stelmach <lukasz.stelmach@iem.pw.edu.pl> of "Fri\, 08 Oct 2010 07\:31\:53 +0200." <87eic18d2u.fsf@kotik.lan>
Łukasz Stelmach <lukasz.stelmach@iem.pw.edu.pl> wrote:
> |-----------+-----|
> | Preamble |
> |-----------+-----|
> | | |
> | Content | TOC |
> | | |
> |-----------+-----|
> | Postamble |
> |-----------+-----|
>
> I'd like to have a layout like the above one, with (pre|post)ambles of
> full width (or at least as wide a the content + TOC). With the present
> layout preamble and postamble are siblings to TOC and the text and I
> can't get the desired layout.
>
I guess it depends on what you start with and how much you are willing
to do by hand (or by extra programming). Are you trying to get this
layout by html-exporting an org file without any massaging of the
resulting HTML/CSS? If so, I don't know how to do it - I don't know if
it's even possible with just the stock org-mode html export mechanism:
org has certain conventions about the HMTL it produces and although it
is possible to bend them (e.g. Sebastian Rose's org-info.js magic
transformation of standard HTML into info-like docs or folded outlines -
who'd have thunk it?), afaik it requires some surgery (e.g. in addition
to Sebaastian's JS script, one needs some machinery on the org-mode
side: org-jsinfo.el, that is very much tailored to Sebastian's script
and a line in the org file to get the whole thing moving).
If you are willing to write some CSS, I think it's quite possible to get
the layout you want (but you may need to add e.g. ids to various
elements in the HTML - I haven't looked at the HTML that org produces in
any detail to see what it puts in and what it leaves out). In
particular, I don't think that the parent/sibling structure of the DOM
tree limits you in any way as far as the layout goes: the <div
id="content"> just gives you a different containing block element; if it
wasn't there, the <body> element would be the containing block element -
but does that really make much difference? And if the preamble/postamble
were outside the div, the tree structure would be different but so what?
Minor adjustments in the CSS would take care of it, I should think.
But as I said, I'm no expert and I may very well be mistaken.
Nick
next prev parent reply other threads:[~2010-10-08 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 21:03 [BUG] define "just", preamble and postamble placement Łukasz Stelmach
2010-10-07 22:44 ` Nick Dokos
2010-10-08 5:31 ` Łukasz Stelmach
2010-10-08 7:46 ` Nick Dokos [this message]
2010-10-13 10:07 ` Łukasz Stelmach
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=31670.1286524019@gamaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=lukasz.stelmach@iem.pw.edu.pl \
/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).