<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I very much agree. When it comes to lightweight markup languages for
use in web (and more) templating there's: <a
href="http://daringfireball.net/projects/markdown/">Markdown</a>,
<a href="http://michelf.com/projects/php-markdown/extra/">Markdown
Extra</a>, <a href="http://haml-lang.com/">Haml</a>, <a
href="http://textile.thresholdstate.com/">Textile</a>... to name
just a few. Is it worth maintaining another tool?<br>
<br>
When it comes to documentation within source files couldn't D adopt
one of the <a
href="http://en.wikipedia.org/wiki/Comparison_of_documentation_generators">many
different </a>documentation generators? Again wouldn't that mean
less custom tools to maintain.<br>
<br>
Unless of course ddoc does something more than these other tools?<br>
<br>
Cheers,<br>
<br>
Chris<br>
<br>
<br>
On 06/29/11 09:38, James Fisher wrote:
<blockquote
cite="mid:BANLkTing-TA0=6AyCm5KMRYotwP3WHn_8A@mail.gmail.com"
type="cite">
<div class="gmail_quote">On Wed, Jun 29, 2011 at 7:46 AM, Jacob
Carlborg <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:doob@me.com">doob@me.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 2011-06-28 23:09, Walter Bright wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
5. I know I suck at web site design, which is why David
Gileadi helped<br>
us out by designing the <a moz-do-not-send="true"
href="http://d-programming-language.org" target="_blank">d-programming-language.org</a>
look & feel.<br>
</blockquote>
<br>
</div>
I think it makes it hard when most of the pages are written in
DDOC. It doesn't help to attract web designers.<br>
</blockquote>
<div><br>
</div>
<div>I'd definitely agree with that. I have no experience with
DDOC, but TBH I don't intend to ever have any. As a general
criticism of DDOC, it seems like another reinvented wheel.
Semi-plaintext formats surround us like the plague, and for
every use case for documentation, there's a better option. If
you want</div>
<div>
<ul>
<li>simplicity, use <a moz-do-not-send="true"
href="http://daringfireball.net/projects/markdown/">Markdown</a>.
Supported everywhere, like GH.</li>
<li>bulky extensible semantic documentation, use <a
moz-do-not-send="true" href="http://www.docbook.org/">DocBook</a>.
Used by O'Reilly, I'm told. Presumably that's how <a
moz-do-not-send="true"
href="http://book.realworldhaskell.org/">Real World
Haskell</a> is maintained as a slick website and an
O'Reilly book.</li>
<li>readability, but power and extensibility if required,
use <a moz-do-not-send="true"
href="http://docutils.sourceforge.net/">docutils</a>/<a
moz-do-not-send="true" href="http://sphinx.pocoo.org/">Sphinx</a>.
Used for the <a moz-do-not-send="true"
href="http://docs.python.org/py3k/">Python standard
library documentation</a>, which, as anyone who has used
it knows, is The Best Documentation In The World.</li>
</ul>
</div>
<div>That said, I suspect DDOC is now entrenched at least in the
stdlib documentation, so maybe we'll have to live with it.
However, the case for <a moz-do-not-send="true"
href="https://github.com/D-Programming-Language/d-programming-language.org/blob/master/index.dd">using
it for the website</a> is nonexistent (anyone disagree?).</div>
</div>
</blockquote>
</body>
</html>