HTML5 Slideshow - Impact of titles (==)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

HTML5 Slideshow - Impact of titles (==)

ch007m
Until now, I don't know if this is specific to Deck.JS or more general (DZSlides, RevealJS, ...) but when a document contains titles (==) and subtitles (===), only the titles are used to split and create new slides.

That impacts the development of asciidoc documents if we would like to use them for slideshow rendering but also as publication, training, documentation. Why ? Until now we can only use titles (==) and not subtitles (===) otherwise all the content is displayed in one slide which is not really readable (even if full screen - https://gist.github.com/cmoulliard/7657805)

Is there a workaround like adding this option just before the section where we would like to cut the slides ([options="split"]) ? That will allow to develop content like we did now but with the possiblity to specify where we would like to slit
Charles Moulliard
Apache Committer / Technologist Evangelist / Blogger / MiddleWare Specialist
Twitter : @cmoulliard
Reply | Threaded
Open this post in threaded view
|

Re: HTML5 Slideshow - Impact of titles (==)

LightGuardjp
What we really need is a new piece of syntax to designate a slide. We didn't have that until 0.1.4 with our own extensions. If you have a new piece of syntax to propose for slide breaks, please do. 

Sent from Mailbox for iPhone


On Tue, Nov 26, 2013 at 5:54 AM, ch007m [via Asciidoctor :: Discussion] <[hidden email]> wrote:

Until now, I don't know if this is specific to Deck.JS or more general (DZSlides, RevealJS, ...) but when a document contains titles (==) and subtitles (===), only the titles are used to split and create new slides.

That impacts the development of asciidoc documents if we would like to use them for slideshow rendering but also as publication, training, documentation. Why ? Until now we can only use titles (==) and not subtitles (===) otherwise all the content is displayed in one slide which is not really readable (even if full screen - https://gist.github.com/cmoulliard/7657805)

Is there a workaround like adding this option just before the section where we would like to cut the slides ([options="split"]) ? That will allow to develop content like we did now but with the possiblity to specify where we would like to slit


If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/HTML5-Slideshow-Impact-of-titles-tp1100.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

Re: HTML5 Slideshow - Impact of titles (==)

ch007m
I will dig the code in detail to make a proposition but as ruby (as language) is new for me, I don't know how much time I will take for that.


On Tue, Nov 26, 2013 at 3:42 PM, LightGuardjp [via Asciidoctor :: Discussion] <[hidden email]> wrote:
What we really need is a new piece of syntax to designate a slide. We didn't have that until 0.1.4 with our own extensions. If you have a new piece of syntax to propose for slide breaks, please do. 

Sent from Mailbox for iPhone


On Tue, Nov 26, 2013 at 5:54 AM, ch007m [via Asciidoctor :: Discussion] <[hidden email]> wrote:

Until now, I don't know if this is specific to Deck.JS or more general (DZSlides, RevealJS, ...) but when a document contains titles (==) and subtitles (===), only the titles are used to split and create new slides.

That impacts the development of asciidoc documents if we would like to use them for slideshow rendering but also as publication, training, documentation. Why ? Until now we can only use titles (==) and not subtitles (===) otherwise all the content is displayed in one slide which is not really readable (even if full screen - https://gist.github.com/cmoulliard/7657805)

Is there a workaround like adding this option just before the section where we would like to cut the slides ([options="split"]) ? That will allow to develop content like we did now but with the possiblity to specify where we would like to slit


If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/HTML5-Slideshow-Impact-of-titles-tp1100.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML




If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/HTML5-Slideshow-Impact-of-titles-tp1100p1102.html
To unsubscribe from HTML5 Slideshow - Impact of titles (==), click here.
NAML



--
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog :  http://cmoulliard.github.io

Charles Moulliard
Apache Committer / Technologist Evangelist / Blogger / MiddleWare Specialist
Twitter : @cmoulliard
Reply | Threaded
Open this post in threaded view
|

Re: HTML5 Slideshow - Impact of titles (==)

LightGuardjp
You don't need to go that far, we can certainly add in the extension needed, I was simply asking for a new syntax for a slide besides a header. 

I think the mismatch is that in HTML5 and in DocBook a new header means a new section, which makes sense that a section would be a slide. You can add the header text to the slide by using a role. Admittedly, neither of those are great solutions. I haven't really thought of a good new syntax to propose. If you have an idea for a new slide definition syntax, by all means put one forward and we can discuss that. 

Sent from Mailbox for iPhone


On Tue, Nov 26, 2013 at 10:25 AM, ch007m [via Asciidoctor :: Discussion] <[hidden email]> wrote:

I will dig the code in detail to make a proposition but as ruby (as language) is new for me, I don't know how much time I will take for that.


On Tue, Nov 26, 2013 at 3:42 PM, LightGuardjp [via Asciidoctor :: Discussion] <[hidden email]> wrote:
What we really need is a new piece of syntax to designate a slide. We didn't have that until 0.1.4 with our own extensions. If you have a new piece of syntax to propose for slide breaks, please do. 

Sent from Mailbox for iPhone


On Tue, Nov 26, 2013 at 5:54 AM, ch007m [via Asciidoctor :: Discussion] <[hidden email]> wrote:

Until now, I don't know if this is specific to Deck.JS or more general (DZSlides, RevealJS, ...) but when a document contains titles (==) and subtitles (===), only the titles are used to split and create new slides.

That impacts the development of asciidoc documents if we would like to use them for slideshow rendering but also as publication, training, documentation. Why ? Until now we can only use titles (==) and not subtitles (===) otherwise all the content is displayed in one slide which is not really readable (even if full screen - https://gist.github.com/cmoulliard/7657805)

Is there a workaround like adding this option just before the section where we would like to cut the slides ([options="split"]) ? That will allow to develop content like we did now but with the possiblity to specify where we would like to slit


If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/HTML5-Slideshow-Impact-of-titles-tp1100.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML




If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/HTML5-Slideshow-Impact-of-titles-tp1100p1102.html
To unsubscribe from HTML5 Slideshow - Impact of titles (==), click here.
NAML



--
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog :  http://cmoulliard.github.io




If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/HTML5-Slideshow-Impact-of-titles-tp1100p1105.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

Re: HTML5 Slideshow - Impact of titles (==)

ch007m
I will do a comparison of reveal, impress, slidy, deckjs, dzslides, landslide slideshows and will come back with a proposition this wek


On Tue, Nov 26, 2013 at 6:37 PM, LightGuardjp [via Asciidoctor :: Discussion] <[hidden email]> wrote:
You don't need to go that far, we can certainly add in the extension needed, I was simply asking for a new syntax for a slide besides a header. 

I think the mismatch is that in HTML5 and in DocBook a new header means a new section, which makes sense that a section would be a slide. You can add the header text to the slide by using a role. Admittedly, neither of those are great solutions. I haven't really thought of a good new syntax to propose. If you have an idea for a new slide definition syntax, by all means put one forward and we can discuss that. 

Sent from Mailbox for iPhone


On Tue, Nov 26, 2013 at 10:25 AM, ch007m [via Asciidoctor :: Discussion] <[hidden email]> wrote:

I will dig the code in detail to make a proposition but as ruby (as language) is new for me, I don't know how much time I will take for that.


On Tue, Nov 26, 2013 at 3:42 PM, LightGuardjp [via Asciidoctor :: Discussion] <[hidden email]> wrote:
What we really need is a new piece of syntax to designate a slide. We didn't have that until 0.1.4 with our own extensions. If you have a new piece of syntax to propose for slide breaks, please do. 

Sent from Mailbox for iPhone


On Tue, Nov 26, 2013 at 5:54 AM, ch007m [via Asciidoctor :: Discussion] <[hidden email]> wrote:

Until now, I don't know if this is specific to Deck.JS or more general (DZSlides, RevealJS, ...) but when a document contains titles (==) and subtitles (===), only the titles are used to split and create new slides.

That impacts the development of asciidoc documents if we would like to use them for slideshow rendering but also as publication, training, documentation. Why ? Until now we can only use titles (==) and not subtitles (===) otherwise all the content is displayed in one slide which is not really readable (even if full screen - https://gist.github.com/cmoulliard/7657805)

Is there a workaround like adding this option just before the section where we would like to cut the slides ([options="split"]) ? That will allow to develop content like we did now but with the possiblity to specify where we would like to slit


If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/HTML5-Slideshow-Impact-of-titles-tp1100.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML




If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/HTML5-Slideshow-Impact-of-titles-tp1100p1102.html
To unsubscribe from HTML5 Slideshow - Impact of titles (==), click here.
NAML



--
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog :  http://cmoulliard.github.io




If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/HTML5-Slideshow-Impact-of-titles-tp1100p1105.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML




If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/HTML5-Slideshow-Impact-of-titles-tp1100p1106.html
To unsubscribe from HTML5 Slideshow - Impact of titles (==), click here.
NAML



--
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog :  http://cmoulliard.github.io

Charles Moulliard
Apache Committer / Technologist Evangelist / Blogger / MiddleWare Specialist
Twitter : @cmoulliard
Reply | Threaded
Open this post in threaded view
|

Re: HTML5 Slideshow - Impact of titles (==)

ch007m
In reply to this post by LightGuardjp
Move the discussion here (https://github.com/asciidoctor/asciidoctor-backends/issues/34)


 
Charles Moulliard
Apache Committer / Technologist Evangelist / Blogger / MiddleWare Specialist
Twitter : @cmoulliard