Hi Alex
Thank you for your hard work.
The compact theme is a nice variant.
I ran the Plan9 backend on asciidoc.1 and and a2x.1 man pages -- they look fine
in the linux manpage reader. This manpage backend is nice because it bypasses
DocBook and DocBook XSL Stylesheets completely by generating the troff directly
-- you've got direct control over the troff output.
Ran the graphviz-cmap filter on the example that comes with AsciiDoc and it
worked just fine. It might be a good idea to point out that this variant is a
drop-in replacement which will override the distributed filter.
I've added all three to the AsciiDoc plugins page:
http://www.methods.co.nz/asciidoc/plugins.html
The updated Cheatsheet is brilliant, the only comment I have is that the
document header is no longer REQUIRED.
Cheers, Stuart
On 18/09/11 02:53, Alex Efros wrote:
Hi!
Let's start using new cool feature of 8.6.6: plugin management! :)
compact - my theme plugin, similar to default color scheme but more
compact.
9man - my backend plugin to generate man pages (troff) compatible with
OS Inferno and Plan9.
Both available for download from http://powerman.name/asciidoc/
Also I've updated asciidoc's cheatsheet to be consistent with small syntax
changes in latest versions.
And released Gentoo ebuild for 8.6.6, so I hope it will be added to
portage soon (you can use 'powerman' overlay or just download ebuild from
Gentoo bugzilla to install 8.6.6 on Gentoo right now).
BTW, about theme plugins. If your theme change more than just few colors,
if it change elements layout, or if you just dislike structure of
asciidoc.css - you'll have to use different css selectors in your theme.
Which in turn means it will be very hard to support your theme, sync it
with changes in next asciidoc versions.
To solve this issue I propose to document structure of html generated by
asciidoc - complete list of all #id, .class and tags hierarchy which can
be output by each html-compatible backend. Probably this can be easily
automatically generated from backend's .conf-files (but I don't know
python and so can't be 100% sure in this). Running diff against such
document should be ease way to detect all changes in backend output and to
update our custom theme.css.
As side effect, it would be nice to have examples of asciidoc source for
each #id, .class and tags hierarchy generated by backend - this allow to
create simple theme test page, and let easily compare themes.
One more thing: pygments support is really cool - it let me to uninstall
both source-highlight and boost, which was my dream each time I recompile
my Gentoo :) and it provide nice css to style syntax highlight. But while
pygments contain about 17 different themes, asciidoc provide only one by
default and doesn't allow to change pygments theme in usual way (using
attributes). I think this is nice small feature to add in next version.
--
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.
