Thanks for giving the deck.js backend a boost, Charles.

I've merged in your pull request. I then followed up with a few refinements:

1. Expect all extensions in the extensions directory to be named consistently (i.e., extensions/<name>/deck.<name>.js)

2. Only load extensions when the corresponding attribute is set (e.g., menu, toc, navigation, etc)

3. Cleanup some of the formatting/syntax in the Haml

I still don't see the deck.split.js extension in the main deck.js repository. Perhaps you copied it into your installation and forgot you had?

I updated the deck.js instructions on asciidoctor.org to document the new attributes. However, the instructions for how to setup the third-party extensions is still a bit fuzzy. I think a they warrant a dedicated section in the guide.

-Dan

On Wed, Nov 20, 2013 at 9:26 AM, LightGuardjp [via Asciidoctor :: Discussion] <[hidden email]> wrote:

Very cool, excellent work!

On Wed, Nov 20, 2013 at 12:16 AM, ch007m [via Asciidoctor :: Discussion] <[hidden email]> wrote:

That was problem with the backend. Everything is solved in my pull request (add missing references to css, js files) and add missing attribute :menu

BTW, as extension split is present in last deck.js distro, documentation can be updated to remove the fact that we must copy/paste extensions split

On Tue, Nov 19, 2013 at 8:01 PM, LightGuardjp [via Asciidoctor :: Discussion] <[hidden email]> wrote:

This is a problem with the backend, correct?

On Tue, Nov 19, 2013 at 3:16 AM, ch007m [via Asciidoctor :: Discussion] <[hidden email]> wrote:

Ticket created with modification proposed for deckjs backend

https://github.com/asciidoctor/asciidoctor-backends/issues/29

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Why-menu-status-or-go-options-of-deck-js-does-not-work-with-HTML-generated-tp1011p1019.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]

To unsubscribe from Asciidoctor :: Discussion, click here.
NAML

--

Jason Porter
http://en.gravatar.com/lightguardjp

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Why-menu-status-or-go-options-of-deck-js-does-not-work-with-HTML-generated-tp1011p1023.html

To unsubscribe from Why menu, status or go options of deck.js does not work with HTML generated, 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/Why-menu-status-or-go-options-of-deck-js-does-not-work-with-HTML-generated-tp1011p1031.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML

--

Jason Porter
http://en.gravatar.com/lightguardjp

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Why-menu-status-or-go-options-of-deck-js-does-not-work-with-HTML-generated-tp1011p1032.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML

--

Dan Allen | http://google.com/profiles/dan.j.allen

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Why-menu-status-or-go-options-of-deck-js-does-not-work-with-HTML-generated-tp1011p1067.html

To unsubscribe from Why menu, status or go options of deck.js does not work with HTML generated, click here.
NAML