It seems to be a trend to use more and more IO in new FRP approaches.<div><br></div><div>Grapefruit's circuits encapsulate side effects, as does your approach</div><div><br></div><div>This is a big departure from the "pure" libs like Fran, Yampa, Reactive, ...</div>
<div><br></div><div>I wander if this is because of some fundamental problem with functional programming when it comes to FRP? </div><div><br></div><div>Some people claim that IO is also pure, and I tend to agree if we can capture the state of the real world and rewind to it somehow :)</div>
<div><br></div><div><div class="gmail_quote">On Thu, Apr 2, 2009 at 4:06 PM, Jeff Heard <span dir="ltr"><<a href="mailto:jefferson.r.heard@gmail.com">jefferson.r.heard@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Check links... god. <a href="http://vis.renci.org/jeff/buster" target="_blank">http://vis.renci.org/jeff/buster</a> (can you tell<br>
I was up till 3am last night?)<br>
<div><div></div><div class="h5"><br>
On Thu, Apr 2, 2009 at 10:05 AM, Jeff Heard <<a href="mailto:jefferson.r.heard@gmail.com">jefferson.r.heard@gmail.com</a>> wrote:<br>
> Yes,sorry. vis, not vs. <a href="http://vis.renci.org/buster" target="_blank">http://vis.renci.org/buster</a><br>
><br>
> It is a bit like grapefruit's circuits, but where Grapefruit circuits<br>
> describe the flow of events from place to place, Buster never does.<br>
> Events exist for all behaviours, to be selected by name, group, or<br>
> source. The other major difference is the |~| or "beside" operator,<br>
> which describes concurrent application of behaviours.<br>
><br>
> A last but somewhat minor thing is that the Event type is fairly<br>
> general, allowing for multiple data to be attached to a single event<br>
> and this data to be of many of the standard types (Int, String,<br>
> Double, ByteString, etc) as well as a user-defined type. Of course,<br>
> such an event type could be defined for other FRP frameworks as well.<br>
><br>
> -- Jeff<br>
><br>
> On Thu, Apr 2, 2009 at 9:53 AM, minh thu <<a href="mailto:noteed@gmail.com">noteed@gmail.com</a>> wrote:<br>
>> It's vis instead of vs:<br>
>> <a href="http://vis.renci.org/jeff/buster/" target="_blank">http://vis.renci.org/jeff/buster/</a><br>
>><br>
>> 2009/4/2 Peter Verswyvelen <<a href="mailto:bugfact@gmail.com">bugfact@gmail.com</a>>:<br>
>>> Sounds vaguely like Grapefruit's circuits, but I could be very wrong...<br>
>>> The link you provided seems to be broken?<br>
>>> On Thu, Apr 2, 2009 at 3:05 PM, Jeff Heard <<a href="mailto:jefferson.r.heard@gmail.com">jefferson.r.heard@gmail.com</a>><br>
>>> wrote:<br>
>>>><br>
>>>> Read more about it on its webpage: <a href="http://vs.renci.org/jeff/buster" target="_blank">http://vs.renci.org/jeff/buster</a><br>
>>>><br>
>>>> Yes, it’s to solve a particular problem. And yes, this is a rough<br>
>>>> draft of an explanation of how it works. I’ve not even really<br>
>>>> solidified the vocabulary yet, but I have this module which couches a<br>
>>>> large, abstract, interactive (both with the user and the system),<br>
>>>> multicomponent application in terms of a bus, inputs, behaviours, and<br>
>>>> events.<br>
>>>><br>
>>>> * Time is continuous and infinite.<br>
>>>> * An event is a static, discrete item associated with a particular<br>
>>>> time.<br>
>>>> * The bus is the discrete view of event in time at an instant.<br>
>>>> * A widget is an IO action that assigns events to a particular<br>
>>>> time based only upon sampling the outside world (other events and<br>
>>>> behaviours are irrelevant to it). e.g. a Gtk Button is a widget, a<br>
>>>> readable network socket is an widget, the mouse is an widget, the<br>
>>>> keyboard is an widget, a multitouch gesture engine is a widget.<br>
>>>> * A behaviour is a continuous item — it exists for the entire<br>
>>>> program and for all times — which maps events on the bus to other<br>
>>>> events on the bus. It is an IO action as well — where widgets only<br>
>>>> sample the outside world and are in a sense read only, behaviours<br>
>>>> encapsulate reading and writing.<br>
>>>> _______________________________________________<br>
>>>> Haskell-Cafe mailing list<br>
>>>> <a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
>>>> <a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> Haskell-Cafe mailing list<br>
>>> <a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
>>> <a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
>>><br>
>>><br>
>><br>
><br>
</div></div></blockquote></div><br></div>