[Haddock] Regenerating Haddock docs on Hackage
david.waern at gmail.com
Fri Sep 10 13:45:41 EDT 2010
2010/9/10 Ross Paterson <ross at soi.city.ac.uk>:
> On Thu, Sep 09, 2010 at 09:30:34PM -0700, Mark Lentczner wrote:
>> Another example pointed out by copumpkin on #haskell today: He wanted to make sure I know of the rendering problems in the new Haddock. He pointed me at this page:
>> Make your window "page" width, and scroll all the way to the bottom - you'll see all sorts of artifacts.
>> I think it would be best if docs generated with older versions of Haddock were restored to the way that they where, and all pages generated with 2.8.1, were generated with --built-in-themes and the modified JS (no Frames button).
> I'm almost finished a pass through regenerating everything with 2.8.1
> (and --built-in-themes). When that's finished, I'll go back and redo
> the ones that were rebuilt before I heard about --built-in-themes.
> When that's finished (by the end of the weekend, I expect), 70-75%
> of the packages with documentation should be done with 2.8.1. For
> latest versions the proportion will be nearly 100%.
> As for the rest ... My problem with the old style file is that those
> big blue headers will make for a jarring experience for hackage users
> as they navigate around documentation. But obviously you don't want
> haddock 2.8 blamed for my kludges. What if we put some sort of marker
> on them, but not as obtrusive as the old style file?
I know the question was directed to Mark, but if you ask me I'd rather
see the big blue headers on a few packages than see strange looking
layout. Perhaps we can just change the colorscheme of the old CSS to
make it closer to Ocean, but otherwise keep it as it is?
More information about the Haddock