<br><div class="gmail_quote">On Wed, Feb 20, 2008 at 10:30 AM, Roman Cheplyaka <<a href="mailto:roma@ro-che.info">roma@ro-che.info</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* Spencer Janssen <<a href="mailto:sjanssen@cse.unl.edu">sjanssen@cse.unl.edu</a>> [2008-02-12 03:58:21-0600]<br>
<div class="Ih2E3d">> On Mon, Feb 11, 2008 at 12:25:59AM +0200, Roman Cheplyaka wrote:<br>
> > Mon Feb 11 00:24:06 EET 2008 Roman Cheplyaka <<a href="mailto:roma@ro-che.info">roma@ro-che.info</a>><br>
> > * Refactor XMonad.Hooks.DynamicLog<br>
> > This allows using DynamicLog not only for statusbar.<br>
><br>
> > , ((mod1Mask, xK_a ), sendMessage NextLayout >> (dynamicLogString myPP >>= \d->spawn $"xmessage "++d))<br>
><br>
> Why not use this instead:<br>
> > dynamicLogWithPP $ myPP { ppOutput = spawn . ("xmessage "++) }<br>
><br>
> Just trying to play devil's advocate against API increases here :)<br>
<br>
</div>Yeah, I was blind. Now it seems really pointless.<br>
Feel free to unapply it. Would you also edit [1]?<br>
</blockquote><div><br>Personally, I still feel like having dynamicLogString is a nice abstraction -- it decouples the status text generation from the output, and lets you get your hands directly on the status text if you would like. So, it turns out that this particular example can be done more simply using a specialized ppOutput, but that doesn't mean dynamicLogString might not still be useful.<br>
<br>-Brent<br></div></div>