There is no doubt in my mind that sphinx produces better pages than
s5. A lot better.
In fact, the s5 slides are *wretched*. The fonts change size when I
resize the page, the header just barely is adequate to contain
headlines, I've had to disable footers, scrolling scrolls by the total
amount in *all* pages, etc, etc.
Perhaps a better css would help, but I spent about 8 hours yesterday
wrestling with css and javascript. It was an educational experience,
but I don't want to repeat it.
In contrast, creating sphinx pages is relatively simple. Creating
Leo's home page took a bit of doing: I had to rewrite the html
following the sphinx model. I had to override the following in
_static/default.css to accommodate the size of the Leo logo.
div.sphinxsidebarwrapper {
/* padding: 10px 5px 0 10px; */
padding: 0px 5px 0 4px; /* top left bottom right */
}
That was it.
I think we all pretty quickly get a feel for the strength of various
tools. And right now S5 feels feeble. It's way too inflexible. It's
fragile: allowing scrolling breaks almost everything. The javascript
is horrendously complex.
Imo, the fundamental model of s5 is dubious, namely cramming all
slides on a single page.
Suppose, instead, that we use Leo to create a succession of sphinx
pages from @slideshow <fn>?
We can use the same convention as s5 does: that each direct child of
the @slideshow node creates a slide. The create-slides command will
create files like:
fn-1.html, fn-2.html, etc.
As far as layout goes, everything should "just work". We'll have the
sphinx headers, footers, including nav buttons, and optionally the
left sidebar and logo. There may be issues with creating a toc file,
but presumably the create-slides command could do that.
A big issue exists with both sphinx and s5. It would be convenient to
have text float to the left or right of screenshots. Css can do this
provided that the html page provides elements that encapsulate the
graphics. Imo, flowing text is particularly important for s5: too much
of the "internals" get broken when scrolling is allowed. Flowing text
would allow us to banish scrolling.
In short, sphinx may be a better alternative to s5. A create-slides
command working on @rst trees may eliminate some of the supposed
advantages of s5.
Big questions remain. My next step will be to see whether rst/sphinx
define sufficient html elements to float text and graphics.
All comments welcome, as usual.
Edward
P.S. This is all very frustrating. I want to create slideshows
yesterday. But it would be foolish to charge ahead with inadequate
tools.
EKR
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
