On 24 Apr 2012, at 09:34, Andrew Butterfield wrote: > What I am suggesting is that I help to develop those instructions by > (1) cleaning up the dross leftover from previous attempts > (2) Following them carefully (keeping a diary) > and adding feedback on the instructions to the wiki (using the Discussion > facility) > (3) Updating the wiki once some consensus on revised instructions have been > reached
You get an enthusiastic +1 from me I find it tricky to be systematic about it, especially given the diversity of possible platforms (combinatorial fun!), and the fact that targets move. I've been trying to move the pages towards something which explicitly accounts for this (eg. the “known configurations” tables, the timestamping). One minor change lately, simpler URLs: * http://www.haskell.org/haskellwiki/WxHaskell/Mac * http://www.haskell.org/haskellwiki/WxHaskell/Linux * http://www.haskell.org/haskellwiki/WxHaskell/Windows Another thing which I think would help is just improving the visual appearance, not for the sake of making it nicer, but just using better markup to help separate bits of the pages from each other. Good luck, -- Eric Kow <http://erickow.com>
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel