Ah, I didn't foresee those ambiguities, but now I see what you mean. I've added your instance below (exactly how this sort of thing comes out for me as well), used in Test.hs, and pushed & released reactive-fieldtrip-0.0.4. And yeah, adding a 'pure' to promote static to dynamic is pretty easy.<br>
<br>Note that now Test.hs imports FRP.Reactive.FieldTrip (a new collect/re-export module) instead of FRP.Reactive.FieldTrip.Adapter.<br><br>Thanks for the suggestion, Greg.<br><br> - Conal<br><br><div class="gmail_quote">
On Mon, Nov 24, 2008 at 3:56 PM, Greg Fitzgerald <span dir="ltr"><<a href="mailto:garious@gmail.com">garious@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">>> static transformations of dynamic geometry.<br>
</div><div class="Ih2E3d">>> dynamic transformation of static geometry and dynamic transformation of<br>
>> dynamic geometry. And the corresponding three additional instances for 2D<br>
>> geometry. All six would be very useful.<br>
<br>
</div>Implementing just the dynamic transformation of dynamic geometry seems<br>
to work out best.<br>
<br>
instance Transform xf a => Transform (Behavior xf) (Behavior a) where<br>
(*%) = liftA2 (*%)<br>
<br>
With the other instances, GHC complains about ambiguities, and it's<br>
easy enough to pull either side up into the dynamic realm.<br>
<br>
Thanks,<br>
<font color="#888888">Greg<br>
</font></blockquote></div><br>