Stuart Rackham <[email protected]> writes:
>> Unfortunately, this runs counter to my main use case. I want to plug
>> into existing documents. The reason for this is that I am using
>> asciidoc's multiple output. The idea is that I can generate printed
>> handouts (through docbook and pdf), as well as a non-slidy HTML
>> versions, which is easier to read. Asciidoc is good for this, because I
>> have conditionals; the versions are similar, but not identical.
>
> I see your point and valid use cases trump everything. I was playing around
> and was having problems with (in hindsight) CSS and the preamble (stuff
> between header and 1st section) -- the scheme I set up certainly won't be
> usable for existing documents, not introducing new syntax is a huge plus.
>
> Anyway, now I've reconciled my original problems and updated my example:
>
> http://www.methods.co.nz/tmp/slidy-example.html
> http://www.methods.co.nz/tmp/slidy-example.txt
>
> The slidy.conf is attached, it's pretty close to yours, handles preambles, the
> full AsciiDoc header and incremental numbered lists along with incremental
> open blocks.


Cool stuff. I'll take a look next week (snowed under this week!). 



>>> You can use the AsciiDoc 'Openblock' to group arbitrary block elements for
>>> incremental display.
>>
>>
>> Okay, that is useful, although it still has the problem that *any*
>> markup will be incremental. So
>>
>> ** First item
>> ** Second _item_
>> ** Third item
>>
>> will produce 4 increments.
>
> I don't understand.


The "_item_" increments as well; the whole list item doesn't appear at
once, unless it's marked up with "non-incremental". Unfortunately, this
requires modifying every element. 

At least this is how slidy works in my hands. Personally, I think that
this is a slidy limitation and would be better fixed in the javascript. 

Phil

-- 
You received this message because you are subscribed to the Google Groups 
"asciidoc" 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/asciidoc?hl=en.

Reply via email to