<div>Hello again,</div><div><br></div>This page:<div> <div><a href="http://diveintopython3.org/about.html">http://diveintopython3.org/about.html</a> <br><br></div><div>indicates jquery is used along with some javascript programs for syntax highlight.</div>
<div><br></div><div>Regards,</div><div>Ketan</div><div><br></div><div><div class="gmail_quote">On Wed, Mar 2, 2011 at 8:07 PM, Ketan Maheshwari <span dir="ltr"><<a href="mailto:ketancmaheshwari@gmail.com">ketancmaheshwari@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello,<br><div><br></div><div>Check out the following:</div><div><br></div><div><a href="http://diveintopython3.org" target="_blank">http://diveintopython3.org</a></div>
<div><br></div><div>I thought they have a beautiful layout and if you see one of the chapters the code and its associated description has a nice highlight feature. Additionally the text into blue boxes that appears on the side gives it more elegance. e.g. </div>
<div><br></div><div><a href="http://diveintopython3.org/strings.html" target="_blank">http://diveintopython3.org/strings.html</a></div><div><br></div><div>I am looking into how they are generated; meanwhile I thought to push it here just in case someone knows already the strategy used to generate these pages.<br>
<br></div><div>From the footer links, seems the pages are available in multiple languages. This kinda indicates they are autogenerated.</div><div><br></div><div>Regards,</div><div>Ketan</div><div><font color="#888888"><br>
</font><div class="gmail_quote"><div class="im">
On Tue, Mar 1, 2011 at 9:34 PM, Michael Wilde <span dir="ltr"><<a href="mailto:wilde@mcs.anl.gov" target="_blank">wilde@mcs.anl.gov</a>></span> wrote:<br></div><div><div></div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
And, in defense of docbook, there is "asciidoc" - like reStructured text but for docbook:<br>
<br>
<a href="http://www.methods.co.nz/asciidoc/index.html" target="_blank">http://www.methods.co.nz/asciidoc/index.html</a><br>
<br>
and<br>
<br>
<a href="http://kaczanowscy.pl/tomek/2010-09/a-perfect-environment-for-docbook" target="_blank">http://kaczanowscy.pl/tomek/2010-09/a-perfect-environment-for-docbook</a><br>
<br>
The asciidoc user guide, presumably done using asciidoc, has some resemblance to our current User Guide:<br>
<br>
<a href="http://www.methods.co.nz/asciidoc/userguide.html" target="_blank">http://www.methods.co.nz/asciidoc/userguide.html</a><br>
<br>
This might let us make a smoother evolution from our current docbook markup to a kinder gentler markup.<br>
<br>
Justin, I am with you on deciding this soon. We may need some more experiments to do that.<br>
<br>
- Mike<br>
<br>
<br>
----- Original Message -----<br>
> Yeah, that looks tedious. But there is also this form which works for<br>
> most layouts:<br>
><br>
> Simple table:<br>
><br>
> ===== ===== ======<br>
> Inputs Output<br>
> ------------ ------<br>
> A B A or B<br>
> ===== ===== ======<br>
> False False False<br>
> True False True<br>
> False True True<br>
> True True True<br>
> ===== ===== ======<br>
><br>
> I dont think tables will make or break it for us.<br>
><br>
> I like the simple style of most of the other text constructs.<br>
><br>
> - Mike<br>
><br>
> ----- Original Message -----<br>
> > On Tue, 2011-03-01 at 11:54 -0600, Michael Wilde wrote:<br>
> > ><br>
> > > ----- Original Message -----<br>
> > > > For what it's worth, I think that if folks don't want docbook<br>
> > > > (which<br>
> > > > I'd<br>
> > > > more inclined to drop if there was any other reasonable<br>
> > > > equivalent<br>
> > > > system that produces good html output),<br>
> > ><br>
> > > Did you look at the reStructured text and Sphinx alternative I<br>
> > > described, which is used by Python and many other projects?<br>
> ><br>
> > I believe that expressing tables like this:<br>
> > +--------------+----------+-----------+-----------+<br>
> > | row 1, col 1 | column 2 | column 3 | column 4 |<br>
> > +--------------+----------+-----------+-----------+<br>
> > | row 2 | Use the command ``ls | more``. |<br>
> > +--------------+----------+-----------+-----------+<br>
> > | row 3 | | | |<br>
> > +--------------+----------+-----------+-----------+<br>
> ><br>
> > ... is silly. You are drawing tables in text. Imagine the amount of<br>
> > work<br>
> > required to add or remove a column.<br>
> ><br>
> > The reason one would use this is if it would be desirable for the<br>
> > documentation to look presentable in a plain text source file.<br>
><br>
> --<br>
> Michael Wilde<br>
> Computation Institute, University of Chicago<br>
> Mathematics and Computer Science Division<br>
> Argonne National Laboratory<br>
<br>
--<br>
Michael Wilde<br>
Computation Institute, University of Chicago<br>
Mathematics and Computer Science Division<br>
Argonne National Laboratory<br>
<br>
_______________________________________________<br>
Swift-devel mailing list<br>
<a href="mailto:Swift-devel@ci.uchicago.edu" target="_blank">Swift-devel@ci.uchicago.edu</a><br>
<a href="http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel" target="_blank">http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel</a><br>
</blockquote></div></div></div><br></div>
</blockquote></div><br></div></div>