From: Michael Welle <mwe012008@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: org-reveal: content side by side
Date: Tue, 13 Feb 2018 16:16:46 +0100 [thread overview]
Message-ID: <87bmgsncm9.fsf@luisa.c0t0d0s0.de> (raw)
In-Reply-To: <873725rrw7.fsf@wi.uni-muenster.de> (Jens Lechtenboerger's message of "Tue, 13 Feb 2018 13:33:12 +0100")
Hello Jens,
Jens Lechtenboerger <lechten@wi.uni-muenster.de> writes:
> On 2018-02-11, Michael Welle wrote:
>
>> Looks easy, eh? A header at the top, a footer at the bottom and a lot
>> of space in between. In some cases, like in [1], I wanted content (e.g.
>> <p>Ich...<br/>OS/2 Warp 4</p>) to be centered horizontally and
>> vertically between the footer and the header.
>
> I created emacs-reveal [0] for my own slides. Contents are centered
jepp, I had a gander at that slides as well as at your slides for the OS
course. Great stuff.
> vertically (default for reveal.js). CSS with “text-align: center”
> can be used for horizontal alignment.
>
> The howto for emacs-reveal is available at [1]. First-level
> headings are centered vertically and horizontally. I just added
> slide 20 with horizontally centered text (underneath a heading,
> which—as ugly hack—could just be a non-breaking space I guess).
Well, maybe it's just me, but the headings do not look vertically
centered. They jump up and down a lot while flipping through the slides.
For slides with a lot of content the heading is a bit more to the top of
the page, for slides with less content the heading 'sinks down' to the
center of the page. If you look at page 20 the heading is just above the
vertical middle of the slide, not at the top.
That jumping of the headings is one of my main issues, I think it's not
acceptable.
I can glue the headings to the top of the page (setting reveal-center to
nil). But then I have trouble centering the content. I tried with
putting in an empty <div> of a certain height. That works, for certain
meanings of work. The trouble is finding the height, which also might
change with changing resolution and content.
I have the feeling that all that can be fixed with using flex layout.
That means changing the CSS entirely, I think. But that is a lot of
work. On the other hand, I'm not a CSS expert.
> I hope that helps and would be happy to help more. (Responses may
> be slow in the coming days, though.)
No worries. Your help is much appreciated.
Regards
hmw
next prev parent reply other threads:[~2018-02-13 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 10:59 org-reveal: content side by side Michael Welle
2018-02-04 18:46 ` Michael Welle
2018-02-06 0:37 ` Matt Price
2018-02-07 17:42 ` Michael Welle
2018-02-11 15:29 ` Michael Welle
2018-02-13 11:19 ` Eric S Fraga
2018-02-13 11:43 ` Michael Welle
2018-02-13 12:33 ` Jens Lechtenboerger
2018-02-13 15:16 ` Michael Welle [this message]
2018-02-13 16:16 ` Jens Lechtenboerger
2018-02-13 16:21 ` Michael Welle
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=87bmgsncm9.fsf@luisa.c0t0d0s0.de \
--to=mwe012008@gmx.net \
--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 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).