Simon Marlow wrote:
They don't look too bad to me... a bit far to the right, perhaps, but
not too bad. Perhaps some lines in that table would help, or
alternating grey/white background for the rows? [...]
What I mean with "drunk" can be seen here:
https://aedion.de/haskell/haddock.png
It's slig
On 24 February 2005 20:11, Sven Panne wrote:
> Simon Marlow wrote:
>> On 22 February 2005 19:37, Duncan Coutts wrote:
>>> Excellent! Thanks a lot.
>>> Any hint as to when the next Haddock release will be?
>> Maybe when I've got this GHC release out of the way and my hair has
>> grown back :-S
>
>
Simon Marlow wrote:
On 22 February 2005 19:37, Duncan Coutts wrote:
Excellent! Thanks a lot.
Any hint as to when the next Haddock release will be?
Maybe when I've got this GHC release out of the way and my hair has
grown back :-S
Before we do a release, I think two issues should be solved IMHO:
On 22 February 2005 19:37, Duncan Coutts wrote:
> Excellent! Thanks a lot.
>
> Any hint as to when the next Haddock release will be?
Maybe when I've got this GHC release out of the way and my hair has
grown back :-S
Simon
___
Glasgow-haskell-users mai
On Tue, 2005-02-22 at 19:10 +, Ross Paterson wrote:
> On Tue, Feb 22, 2005 at 05:45:39PM +, Duncan Coutts wrote:
> > In gtk2hs we have one huge module which defines all the types (this is
> > produced by a code generator from a text file which describes the Gtk+
> > class hierarchy). Howeve
On Tue, Feb 22, 2005 at 05:45:39PM +, Duncan Coutts wrote:
> In gtk2hs we have one huge module which defines all the types (this is
> produced by a code generator from a text file which describes the Gtk+
> class hierarchy). However we don't ever want this module to be exposed
> to users. We re
On Tue, 2005-02-01 at 11:02 +, Simon Marlow wrote:
> I'm making some changes to the way Haddock creates links, and I'd like
> to solicit comments on possible alternatives.
>
> The existing approach is for each non-locally-defined identifier in the
> current module, we hyperlink to a module th
On 02 February 2005 12:22, Ross Paterson wrote:
> On Tue, Feb 01, 2005 at 11:02:45AM -, Simon Marlow wrote:
>> So the new approach is to try to build up a global table of the
>> "best" destinations to link to for each entity.
>
> Having a canonical home location for each entity might also hel
On Tue, Feb 01, 2005 at 11:02:45AM -, Simon Marlow wrote:
> So the new approach is to try to build up a global table of the "best"
> destinations to link to for each entity.
Having a canonical home location for each entity might also help with
another bugbear with Haddock: determining whether
On 01 February 2005 12:48, Ketil Malde wrote:
> "Simon Marlow" <[EMAIL PROTECTED]> writes:
>
>> There are some problems with the existing approach. It doesn't cope
>> well with instances: instances might refer to types/classes not below
>> the current module in the hierarchy. Also you might imp
On 01 February 2005 11:31, [EMAIL PROTECTED] wrote:
> On Tue, Feb 01, 2005 at 11:02:45AM -, Simon Marlow wrote:
>> I'm making some changes to the way Haddock creates links, and I'd
>> like to solicit comments on possible alternatives.
>>
>> The existing approach is for each non-locally-define
On Tue, Feb 01, 2005 at 03:19:11PM -, Simon Marlow wrote:
> On 01 February 2005 11:31, [EMAIL PROTECTED] wrote:
> > On Tue, Feb 01, 2005 at 11:02:45AM -, Simon Marlow wrote:
> >> So the new approach is to try to build up a global table of the
> >> "best" destinations to link to for each ent
"Simon Marlow" <[EMAIL PROTECTED]> writes:
> Hmm, I'm not sure that would be practical. Lots of entities are
> exported from more than one place, especially Prelude entities. You'd
> have a table on almost every single page listing Bool, Maybe, Int, etc.
But surely in many cases, it would be po
"Simon Marlow" <[EMAIL PROTECTED]> writes:
> There are some problems with the existing approach. It doesn't cope
> well with instances: instances might refer to types/classes not below
> the current module in the hierarchy. Also you might import an entity
> from a "hidden" module, but actually w
On Tue, Feb 01, 2005 at 11:02:45AM -, Simon Marlow wrote:
> I'm making some changes to the way Haddock creates links, and I'd like
> to solicit comments on possible alternatives.
>
> The existing approach is for each non-locally-defined identifier in the
> current module, we hyperlink to a mod
15 matches
Mail list logo
