<br><br><div class="gmail_quote">On Thu, Nov 27, 2008 at 8:26 AM, Thomas Davie <span dir="ltr"><<a href="mailto:tom.davie@gmail.com">tom.davie@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d"><br>
On 26 Nov 2008, at 22:50, Levi Stephen wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi,<br>
<br>
This is no longer a problem I managed to get this working by adding the following lines:<br>
<br>
updater <- mkUpdater (cGetTime clock) (return () `stepper` quitOnDestory windowDestroy)<br>
<br>
idleAdd (updater >> return True)<br>
</blockquote>
<br></div>
Excellent! I look forward to seeing a release of reactive-gtk some time, it'd be lovely to be able to program "proper" GUIs in a truely functional way.<br>
<br>
Bob</blockquote><div><br></div><div>Just don't hold your breath ;)<br><br>My project is more to develop an app, but I'm experimenting with using reactive and gtk together. Hopefully something like reactive-gtk could come out of it, but that isn't what I'm aiming for atm. If anything useful does turn up, I will package it though.<br>
<br>In particular, I'm not sure what the best way to represent GUIs in a reactive program is. Currently I'm just using an approach similar to the above, where any GTK event is 'wrapped' using makeEvent to create a reactive Event. I hope to get a better idea of what the best way is as I proceed and refactor as I go.<br>
<br>Levi</div></div><br>