2009/7/13 therac25 <th3r...@googlemail.com>:
> Carrying on with my idea to discover Flapjax through useful 'real-
> world' widgets, I've put together a carousel example:
>
> http://la.di.da.free.fr/Flapjax/carousel/carousel.html
Nice job, keep it up!
I think we need more widgets, so we can come with some cool
abstraction. I wonder how complex applications are to be composed
in FRP? It's straightforward with imperative MVC: just don't! :)
Can we break a widget down to basic building blocks and a few
ways of combining them? We could then provide flexibility as
well as composability and correctness, which would be a win.
For example, I've written a simple RPN calculator [1] (actually, I've
translated an example from Fudgets, taking styling from a JS calculator).
What is unusual (compared to native JS implementations I've seen) is
the "combinational" style as well as separation of "business logic"
and "presentation".
Cheers,
Artyom Shalkhakov.
[1] http://www.sound-city.kz/fj/tabs.html#tab-content-1
(yes, I've taken your example as a starting point, thanks.)
Does that make sense?
[Btw, T25, that demo was tres cool.]
Shriram
2009/7/17 Shriram Krishnamurthi <s...@cs.brown.edu>:
Yes it does. On the one hand, I wonder what an FRP widget library would look
like? What benefits would it give?
For example, with Fudgets it's easy to compose widgets to get other
widgets (BTW, can Fudgets be considered FRP or not?). It's hard to do this
kind of thing with common widget toolkits, both desktop and web, and you
have to write too much code for even the simplest tasks.
On the other hand, bringing the best of both worlds seems to be the most
reasonable way.
Cheers,
Artyom Shalkhakov.