Re: [Haskell-cafe] Superset of Haddock and Markdown

2011-11-21 Thread Malcolm Wallace

On 20 Nov 2011, at 22:20, Ivan Lazar Miljenovic wrote:

 On 21 November 2011 03:19, David Fox dds...@gmail.com wrote:
 On Fri, Nov 18, 2011 at 1:10 AM, Ertugrul Soeylemez e...@ertes.de wrote:
 Ivan Lazar Miljenovic ivan.miljeno...@gmail.com wrote:
 
 Wasn't there talk at one stage of integrating pandoc into haddock?
 
 I wouldn't mind Haddock depending on Pandoc, at least optionally
 (-fmarkdown-comments).  Taking this to its conclusion you could easily
 have syntax-highlighted code examples in Haddock documentations and
 allow alternative output formats.
 
 I'm not sure the pandoc license (GPL) is compatible with the GHC license.
 
 Do you mean because GHC ships with a Haddock binary?

GHC also ships with a GPL'd gcc binary, on at least some platforms.

Regards,
Malcolm

___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe


Re: [Haskell-cafe] Superset of Haddock and Markdown

2011-11-21 Thread David Fox
On Sun, Nov 20, 2011 at 2:20 PM, Ivan Lazar Miljenovic
ivan.miljeno...@gmail.com wrote:
 On 21 November 2011 03:19, David Fox dds...@gmail.com wrote:
 On Fri, Nov 18, 2011 at 1:10 AM, Ertugrul Soeylemez e...@ertes.de wrote:
 Ivan Lazar Miljenovic ivan.miljeno...@gmail.com wrote:

 Wasn't there talk at one stage of integrating pandoc into haddock?

 I wouldn't mind Haddock depending on Pandoc, at least optionally
 (-fmarkdown-comments).  Taking this to its conclusion you could easily
 have syntax-highlighted code examples in Haddock documentations and
 allow alternative output formats.

 I'm not sure the pandoc license (GPL) is compatible with the GHC license.

 Do you mean because GHC ships with a Haddock binary?


Haddock carries the same license as GHC.

___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe


Re: [Haskell-cafe] Superset of Haddock and Markdown

2011-11-21 Thread Brandon Allbery
On Mon, Nov 21, 2011 at 12:28, David Fox dds...@gmail.com wrote:

 On Sun, Nov 20, 2011 at 2:20 PM, Ivan Lazar Miljenovic
 ivan.miljeno...@gmail.com wrote:
  On 21 November 2011 03:19, David Fox dds...@gmail.com wrote:
  I'm not sure the pandoc license (GPL) is compatible with the GHC
 license.
  Do you mean because GHC ships with a Haddock binary?

 Haddock carries the same license as GHC.


More to the point, Haddock uses ghc internals these days; it's not just a
matter of bundling, and the licenses *must* be compatible.

-- 
brandon s allbery  allber...@gmail.com
wandering unix systems administrator (available) (412) 475-9364 vm/sms
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe


Re: [Haskell-cafe] Superset of Haddock and Markdown

2011-11-21 Thread Thomas Schilling
On 21 November 2011 17:34, Brandon Allbery allber...@gmail.com wrote:
 Haddock carries the same license as GHC.

 More to the point, Haddock uses ghc internals these days; it's not just a
 matter of bundling, and the licenses *must* be compatible.

No.  If the haddock library any program that links against that
library (e.g., the haddock program) effectively becomes GPL licensed
(roughly speaking).  However, ghc and none of the core libraries link
against haddock, so that's not a problem.  You could run into issues
if you wanted to write a closed-source program that links against the
haddock library.

I generally don't like GPL-licensed libraries for that reason, but in
this case I think it would be fine.

 (Of course, the issue is that many tools start out as programs and
then turn into libraries -- pandoc is a good example.  At that point
GPL becomes an issue again.)

-- 
Push the envelope. Watch it bend.

___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe


Re: [Haskell-cafe] Superset of Haddock and Markdown

2011-11-20 Thread David Fox
On Fri, Nov 18, 2011 at 1:10 AM, Ertugrul Soeylemez e...@ertes.de wrote:
 Ivan Lazar Miljenovic ivan.miljeno...@gmail.com wrote:

 Wasn't there talk at one stage of integrating pandoc into haddock?

 I wouldn't mind Haddock depending on Pandoc, at least optionally
 (-fmarkdown-comments).  Taking this to its conclusion you could easily
 have syntax-highlighted code examples in Haddock documentations and
 allow alternative output formats.

I'm not sure the pandoc license (GPL) is compatible with the GHC license.

___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe


Re: [Haskell-cafe] Superset of Haddock and Markdown

2011-11-20 Thread Ivan Lazar Miljenovic
On 21 November 2011 03:19, David Fox dds...@gmail.com wrote:
 On Fri, Nov 18, 2011 at 1:10 AM, Ertugrul Soeylemez e...@ertes.de wrote:
 Ivan Lazar Miljenovic ivan.miljeno...@gmail.com wrote:

 Wasn't there talk at one stage of integrating pandoc into haddock?

 I wouldn't mind Haddock depending on Pandoc, at least optionally
 (-fmarkdown-comments).  Taking this to its conclusion you could easily
 have syntax-highlighted code examples in Haddock documentations and
 allow alternative output formats.

 I'm not sure the pandoc license (GPL) is compatible with the GHC license.

Do you mean because GHC ships with a Haddock binary?

-- 
Ivan Lazar Miljenovic
ivan.miljeno...@gmail.com
IvanMiljenovic.wordpress.com

___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe


Re: [Haskell-cafe] Superset of Haddock and Markdown

2011-11-18 Thread Roman Cheplyaka
* Johan Tibell johan.tib...@gmail.com [2011-11-17 21:09:15-0800]
 Hi all,
 
 I spent some time today documenting a library and the experience left me
 wanting a better markup language. In particular, Haddock lacks:
 
  * markup for bold text: bold text works better than italics for emphasis
 on computer monitors.
  * hyperlinks with anchor texts: having the actual URL rendered inline with
 text hurts readability.
 
 Could Haddock markup be extended to also include some Markdown features?
 The new features could be hidden behind a flag so old documentation doesn't
 get unwanted markup (e.g. if it uses *...* to not mean bold).
 
 P.S. This good make a good weekend hack that shouldn't be too difficult.

Sounds awesome!

Maybe have a switch that enables markdown and disables markup-related
features of haddock (everything except linking to identifiers/modules, I
believe), so that we don't affect existing docs. Then make it possible
to pass this flag through cabal.

-- 
Roman I. Cheplyaka :: http://ro-che.info/

___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe


Re: [Haskell-cafe] Superset of Haddock and Markdown

2011-11-18 Thread Ivan Lazar Miljenovic
On 18 November 2011 19:06, Roman Cheplyaka r...@ro-che.info wrote:

 Maybe have a switch that enables markdown and disables markup-related
 features of haddock (everything except linking to identifiers/modules, I
 believe), so that we don't affect existing docs. Then make it possible
 to pass this flag through cabal.

As in have an opt-in Cabal field?

-- 
Ivan Lazar Miljenovic
ivan.miljeno...@gmail.com
IvanMiljenovic.wordpress.com

___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe


Re: [Haskell-cafe] Superset of Haddock and Markdown

2011-11-18 Thread Ertugrul Soeylemez
Ivan Lazar Miljenovic ivan.miljeno...@gmail.com wrote:

 Wasn't there talk at one stage of integrating pandoc into haddock?

I wouldn't mind Haddock depending on Pandoc, at least optionally
(-fmarkdown-comments).  Taking this to its conclusion you could easily
have syntax-highlighted code examples in Haddock documentations and
allow alternative output formats.


Greets,
Ertugrul


-- 
nightmare = unsafePerformIO (getWrongWife = sex)
http://ertes.de/



___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe


Re: [Haskell-cafe] Superset of Haddock and Markdown

2011-11-18 Thread Twan van Laarhoven

On 18/11/11 09:18, Ivan Lazar Miljenovic wrote:

On 18 November 2011 19:06, Roman Cheplyakar...@ro-che.info  wrote:


Maybe have a switch that enables markdown and disables markup-related
features of haddock (everything except linking to identifiers/modules, I
believe), so that we don't affect existing docs. Then make it possible
to pass this flag through cabal.


As in have an opt-in Cabal field?


For a cabal field, we could just have haddock be the default markup 
language. Something like:


   DocMarkupLanguage: Haddock | Markdown | Plain | Html | ...
   -- default is Haddock

But before worrying about that, such a possibility should exist in haddock.


Twan

___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe


[Haskell-cafe] Superset of Haddock and Markdown

2011-11-17 Thread Johan Tibell
Hi all,

I spent some time today documenting a library and the experience left me
wanting a better markup language. In particular, Haddock lacks:

 * markup for bold text: bold text works better than italics for emphasis
on computer monitors.
 * hyperlinks with anchor texts: having the actual URL rendered inline with
text hurts readability.

Could Haddock markup be extended to also include some Markdown features?
The new features could be hidden behind a flag so old documentation doesn't
get unwanted markup (e.g. if it uses *...* to not mean bold).

P.S. This good make a good weekend hack that shouldn't be too difficult.

-- Johan
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe


Re: [Haskell-cafe] Superset of Haddock and Markdown

2011-11-17 Thread Ivan Lazar Miljenovic
On 18 November 2011 16:09, Johan Tibell johan.tib...@gmail.com wrote:
 Hi all,
 I spent some time today documenting a library and the experience left me
 wanting a better markup language. In particular, Haddock lacks:
  * markup for bold text: bold text works better than italics for emphasis on
 computer monitors.

Even for the italics offered by /.../ would ideally be replaced, as
too often people (including myself) forget to escape paths or when
listing alternatives (e.g. foo/bar), leading to borked documentation.

  * hyperlinks with anchor texts: having the actual URL rendered inline with
 text hurts readability.
 Could Haddock markup be extended to also include some Markdown features? The
 new features could be hidden behind a flag so old documentation doesn't get
 unwanted markup (e.g. if it uses *...* to not mean bold).

Wasn't there talk at one stage of integrating pandoc into haddock?

-- 
Ivan Lazar Miljenovic
ivan.miljeno...@gmail.com
IvanMiljenovic.wordpress.com

___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe