On Nov 1, 11:09 pm, Francois Bertrand [EMAIL PROTECTED] wrote:
Hi Marius
1. I was wondering why the use of Option and not Can ?
Because I didn't need the Failure part of Can.
I'm not saying Option is bad Can is good ... not by far. But Can is
more liftish even if you do not use Failure. It has some handy
artifacts that option does not. Neverthelesse there is and implicit
conversion from Option to Can and vice-versa. No biggie ... just
wondering.
2. Any particular reason for using StringBuilder in
FlotOverview.render and not JsExp composition (same for Flot
object)? ... it just seamed easier? .. renderHide and renderShow
functions... I think Lift has abstractions for those as well.
I didn't knew about JsExp composition when I began this widget. I
agree I should use it.
3. I'd recommend using English names for functions etc.
Yes, sorry about that. The flotDemo webapp is a simplified version of
a real application where I have to put spanish comments and funcion's
names.
4. SensorActor .. any reason for not using CometActor ?
The CometActor in the flotDemo webapp is the
net.liftweb.flot_demo.web.model.FlotCometExample class.
The SensorActor.scala file contains;
- a Scala Actor (AcumMuestrasActor) that acumulates sampling values
and notify each FlotCometExample that listens to it,
- a java thread (Sensor) that simulates a sensor sending every 2
seconds a sample with 3 measurements:
I don't see the value to use CometActor for the AcumMuestrasActor
class and the Sensor object, but maybe there is something I don't
understand.
Sorry man ..FlotCometExample escaped me :D ... still is this just an
example or something that people can use in many cases? .. if it is
probably a better name without example part would be more fitful.
Thanks for your comments.
Francois
On Nov 1, 5:01 pm, Marius [EMAIL PROTECTED] wrote:
Nice.
1. I was wondering why the use of Option and not Can ?
2. Any particular reason for using StringBuilder in
FlotOverview.render and not JsExp composition (same for Flot
object)? ... it just seamed easier? .. renderHide and renderShow
functions... I think Lift has abstractions for those as well.
3. I'd recommend using English names for functions etc.
4. SensorActor .. any reason for not using CometActor ?
Br's,
Marius
On Nov 1, 9:12 pm, Francois Bertrand [EMAIL PROTECTED] wrote:
Hi:
The flot widget is a wrapper around the jQuery Flot widget
(http://code.google.com/p/flot/). It generates the necessary javascript
code
and can be used from a comet actor to refresh the graph in real time.
The commited source are:
- the flot widget itself in the lift-widgets module (Scala source
athttp://github.com/dpp/liftweb/tree/master/lift-widgets/src/main/scala...
)
- a new demo webapp below sites
(http://github.com/dpp/liftweb/tree/master/sites/flotDemo).
I appreciate any suggestion, recommendation you may have.
Saludos,
Francois
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
