I edited the leader paragraphs above each code block that
was flagged as being XML or Java content, such that the
paragraphs make sense when both the XML and the Java blocks
are present. I turned the Both button back on. I also caught
a bunch of other editing things.
Mahmoud Ben Hassine caught a couple of sentences that were
problematic when the Both option is on. I then caught a couple
of other problems. I fixed all of that.
Thanks for reading closely, Mahmoud. I always appreciate that.
I made a new implementation of the XML/Java toggle (and added a third choice for having both available).
Changes to make a dynamic ToC work with content selection toggles
Various asciidoc and JavaScript changes to make the dynamic ToC (tocbot) work with the content toggle (XML or Java in this case but also more options in other projects).
This is a demo of the functionality and it located in the domain.adoc file.
added code to handl PDF ifdef
JavaScript added to support slider control
If view in local file system use safari. (Cookies not supported on local filesysem on chrome)
Remaining bug... if user selects xml and refreshes the examples still show XML but slider goes back to JAVA.
Could use a new tool suite. But this is based on the Spring.io toggle.
Implemented java vs xml toggle in reference documentation
This commit ports the javascript widget used in Sagan for toggling
between Maven and Gradle on each project page and uses it to toggle
between java based config and XML based config. The preference the user
selects is cookied so that it should stick between pages in the multiple
page layout as well as for future visits to the documentation.
The only page that has implemented the toggle in this commit is the
domain.adoc page. The spring-batch-intro.adoc has the toggle reference
in it, but it's only there to verify multiple includes are working.
Polishing
