
Hi, I've just put online the new haddock documentation for both the core and the contrib libraries: http://gorgias.mine.nu/xmonad/xmonad/ http://gorgias.mine.nu/xmonad/xmonad-contrib/ I think that an example of a good way of documenting a module can be seen here: http://gorgias.mine.nu/xmonad/xmonad-contrib/XMonad-Config-CustomKeys.html I suggest to use it as a model. Do you agree? Andrea

On 11/14/07, Andrea Rossato
I think that an example of a good way of documenting a module can be seen here: http://gorgias.mine.nu/xmonad/xmonad-contrib/XMonad-Config-CustomKeys.html
I suggest to use it as a model. Do you agree?
No, I don't! :) 1) Thanks, Andrea. A lot. 2) I've updated documentation yesterday. It is subjectively better now (no `XXX', at least). Have fun. -- vvv

valery.vv:
On 11/14/07, Andrea Rossato
wrote: I think that an example of a good way of documenting a module can be seen here: http://gorgias.mine.nu/xmonad/xmonad-contrib/XMonad-Config-CustomKeys.html
I suggest to use it as a model. Do you agree?
No, I don't! :)
1) Thanks, Andrea. A lot. 2) I've updated documentation yesterday. It is subjectively better now (no `XXX', at least).
Yes, I think this is good. I'd also suggest we show both configuration mechanisms: 1) updating defaultConfig 2) writing our own complete config (old style) So an extension would illustrate both cases: 1) how to use the extension to override/update defaultConfig and 2) what line to add to the default Map or binding to replace it entirely. -- Don
participants (3)
-
Andrea Rossato
-
Don Stewart
-
Valery V. Vorotyntsev