On Sat, Jan 22, 2011 at 10:53, Leslie P. Polzer <[email protected]> 
wrote:
> Everytime a widget is refreshed without a page reload we are making
> an AJAX (Javascript) request to the server side. Check out weblocks.js
> for some big picture ideas of what is going on, and take a look at
> the requests with Firebug's "Net" panel.

I will.

> REST, of course, doesn't have much to do with Javascript. It's just
> a philosophy of URL building.
>
> I'm not sure what you want to achieve or understand, so I'm leaving
> it at that. Ask more specific questions and I'll be happy to get
> into more detail.

I would like to use  http://openlayers.org/ for drawing interactive
maps, and http://code.google.com/p/flot/ to draw interactive graphs.
Openlayer will receive changes (tracking of wehicles on the map, for
example) in as much of realtime as is possible, and flot will draw
data for those wehicles (speed and stuff). Also, I would like to be
able to use these javascript libraries to send the data back to
weblocks. So I need two modes of communication:
- realtime reception of the new data to be displayed
- static display and modification of the data (for example, select
date for data display, input stuff into forms).

I understand the concepts of how javascript libraries display the data
that is "currently loaded" (various arrays and similar), and I do
understand a bit how weblocks views work (with the simple "display all
objects", I'm still grasping the "display only this set of data"), but
I don't quite understand what I have to do on the weblocks side to
send and receive. Mostly, I have problems understanding CLOS and the
way weblocks uses it. I guess that is my main problem that stops me
using more advanced stuff in weblocks.

-- 
You received this message because you are subscribed to the Google Groups 
"weblocks" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/weblocks?hl=en.

Reply via email to