Hi Stuart, Thanks! That works well. I changed the [+docinfo] section slightly to reference separate JS/CSS files rather than embedding the content into the conf file:
[+docinfo] include1::./collapse.js[] include1::./collapse.css[] I also moved the section so the files are only included when using the XHTML backend. A quick question - what is the rationale behind not auto-loading the filter? To avoid conflicts (conf/css/js naming) or something else? Cheers, Will On Aug 30, 2:47 am, Stuart Rackham <[email protected]> wrote: > Hi Will > > I've made some changes to the AsciiDoc trunk that makes it possible to install > the filter using only the --filter install command (a separate docinfo.html > file > is no longer necessary). I've attached the hacked filter, there are just 2 > changes: > > 1. Addition of a __noautoload__ flag file to inhibit auto-loading the filter. > > 2. The docinfo.html file has been added to the [+docinfo] section in the > collapse.conf file (the '+' section name prefix causes the section contents to > append rather than replace. > > You can install with: > > asciidoc --filter install crg-1.0.1.zip > > and use with, for example: > > asciidoc --filter crg mydoc.txt > > Note the filter is loaded explicitly because it's not auto-loaded. > > I built the filter plugin file with the new plugin 'build' command: > > asciidoc --filter build crg-1.0.1.zip crg > > Cheers, Stuart > > On 27/08/11 02:04, Will wrote: > > > > > > > > > Hi Stuart& Lex, > > > Thanks for the feedback. > > >>> The Zip file seems to be corrupt? > > > Yes, sorry my fault. The filter has been re-uploaded, please try > > again: > > >https://sourceforge.net/projects/collapsefilter/files/collapse_filter... > > >>> Personally I like the filter approach, it allows you to collapse arbitrary > >>> sections instead of the paragraph-by-paragraph approach. If this cou > > > I have managed to replicate all (I think) functionality using just a > > conf file. This has been uploaded to: > > >https://sourceforge.net/projects/collapsefilter/files/collapse_conf/1... > > > I think using a conf file has advantages over the filter method in > > that it is simpler, cleaner& faster. Drawback is (I suppose) a conf > > file restricts what can be done (but for this particular example, it > > is quite simple so shouldn't be an issue). Let me know what you > > think. > > > I still have a question though, and would like your input. CSS& JS > > is currently separated into a docinfo file and embedded into the xhtml > > output uising the -a docinfo1 switch. Is this the best way to include > > it (it means the standard conf files do not need to be modified)? If > > so, is it possible to either automatically include a file, or via the > > command line specify where the docinfo file lives on the filesystem? > > I can only see how to include it when it is in the source file > > directory, which means the "standard" docinfo file must be copied to > > every source directory before rendering. > > > Cheers, > > Will > > > > crg-1.0.1.zip > 3KViewDownload -- 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.
