From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Rose Subject: Re: export and containers Date: Sat, 28 Feb 2009 22:09:24 +0100 Message-ID: <87k57ae0aj.fsf@kassiopeya.MSHEIMNETZ> References: <49a91200.1438560a.6867.ffffb3e4@mx.google.com> <87eixikd1u.fsf@kassiopeya.MSHEIMNETZ> <2C16E559-565E-4832-B5B9-C57504438508@uva.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LdWO6-0001cX-VH for emacs-orgmode@gnu.org; Sat, 28 Feb 2009 16:06:22 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LdWO6-0001cJ-C7 for emacs-orgmode@gnu.org; Sat, 28 Feb 2009 16:06:22 -0500 Received: from [199.232.76.173] (port=56369 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LdWO6-0001cG-61 for emacs-orgmode@gnu.org; Sat, 28 Feb 2009 16:06:22 -0500 Received: from mail.gmx.net ([213.165.64.20]:50104) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1LdWO5-0000Mo-HE for emacs-orgmode@gnu.org; Sat, 28 Feb 2009 16:06:21 -0500 In-Reply-To: <2C16E559-565E-4832-B5B9-C57504438508@uva.nl> (Carsten Dominik's message of "Sat, 28 Feb 2009 20:23:19 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: org-mode , Richard Riley Carsten Dominik writes: > Hi Sebastian, > > I could do this. Would this mean that org-info.js would become > backward not compatible with older pages? I believe quite a few people actually > pull org-info.js from orgmode.org. I'd have to rework it a bit. But I think it's worth it, since it offers more fleyibility in (web-)design. Maybe we could just branch and work it out. When done, we merge into trunk and inform everyone about the changes. New things brake old ones some times - so what? If we play it `fair', it should be fine. Adjusting org-info.js the way it is now, takes a weekend I hope. Actually, I doubt that there is much to be rewritten - maybe the info-view-mode changes a bit. I'd happily do a for f in $(find ~/org/ -name '*.org); do touch "$f"; done and re-publish all the stuff, to make my pages centered in the window. And that's all people willing to upgrade have to do. Also, I'm quite sure we can eleminate the remaining problems with the fixed TOC in IE on small screens, since there's another container around it. > > - Carsten > > On Feb 28, 2009, at 12:37 PM, Sebastian Rose wrote: > >> Richard Riley 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 "
>>> >>> 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: >> >> >>
-- center the page if desired >>
-- center the page if desired >> >>
-- Help with fixed TOC >>
>> the toc >>
>>
>> >>
-- Help with fixed TOC >> All the rest of the content goes here >>
>> >>
>> postamble >>
>> >>
>>
>> >> >> >> >> 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! >> - 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 >> >> >> _______________________________________________ >> Emacs-orgmode mailing list >> Remember: use `Reply All' to send replies to the list. >> Emacs-orgmode@gnu.org >> http://lists.gnu.org/mailman/listinfo/emacs-orgmode > > > - Carsten > > On Feb 28, 2009, at 12:37 PM, Sebastian Rose wrote: > >> Richard Riley 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 "
>>> >>> 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: >> >> >>
-- center the page if desired >>
-- center the page if desired >> >>
-- Help with fixed TOC >>
>> the toc >>
>>
>> >>
-- Help with fixed TOC >> All the rest of the content goes here >>
>> >>
>> postamble >>
>> >>
>>
>> >> >> >> >> 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! >> - 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 >> >> >> _______________________________________________ >> Emacs-orgmode mailing list >> Remember: use `Reply All' to send replies to the list. >> Emacs-orgmode@gnu.org >> http://lists.gnu.org/mailman/listinfo/emacs-orgmode > -- 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