Re: refreshing events on JQFullCalendar

Hi Davide,

I don't know.  It looks like you could instead return a json array of
events and run the renderEvent method on each of them.  See
http://arshaw.com/fullcalendar/docs/event_rendering/renderEvent/
I don't know if that means you'll end up with two duplicated events of
different color or not.

Or use #updateEvent:
(http://arshaw.com/fullcalendar/docs/event_data/updateEvent/) method
after using some jQuery to find the changed events in the client and set
their new CSS properties.  Have your callback make a Dictionary with the
keys the id of each modified event and the values the revised CSS rules.
 then emit that as json and iterate over it on the client finding the
EventObject and change its CSS.


Seems like there are mechanisms there to only update specific events but
I haven't done it before.


Good luck and sorry I can't be more help


Paul



On 01/15/2013 10:28 AM, Davide Varvello wrote:
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Hi Davide,

It would help me to run this discussion through the Seaside list.  So
I've cc'd it.

answers below.

On 01/15/2013 11:51 AM, Davide Varvello wrote:

Nothing other than the jQuery docs. jQuery in Seaside maps 1:1 with
jQuery because I think Lukas Renggli builds the package from the jQuery
docs or source.  I'm sure someone on the Seaside list has a better
answer for you about jQuery + ajax + Seaside.  I don't think its
possible to do conditional logic with it either.  My preference, and I
think the recommendation, is to do as little as possible in Seaside with
jQuery and instead put most of the logic in a js method that is called
on the client.

The docs of fullcalendar here: http://arshaw.com/fullcalendar/docs
are extensive.  I think I've got most of it in that package.  To get the
events in the client you want #clientEvents:

I added a link to the example that does what you want, in a limited way.
 Every 10 seconds it changes the background color of the events and only
sends enough JSON to identify the event and specify the new background
color.  It does not re-render the whole thing.  I think building the js
function in Seaside would be not fun.


When you initially render the events be sure to give them a unique id by
setting something in the id inst var. (In the example its the first line
in the #renderCalendar: method)



Take care

Paul


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Hi Paul,

 

Nothing other than the jQuery docs. jQuery in Seaside maps 1:1 with
jQuery because I think Lukas Renggli builds the package from the jQuery
docs or source.  I'm sure someone on the Seaside list has a better
answer for you about jQuery + ajax + Seaside.  I don't think its
possible to do conditional logic with it either.  My preference, and I
think the recommendation, is to do as little as possible in Seaside with
jQuery and instead put most of the logic in a js method that is called
on the client.

The docs of fullcalendar here: http://arshaw.com/fullcalendar/docs
are extensive.  I think I've got most of it in that package.  To get the
events in the client you want #clientEvents:

I added a link to the example that does what you want, in a limited way.

Sorry Paul, which link are you saying about?

Davide

 

 Every 10 seconds it changes the background color of the events and only
sends enough JSON to identify the event and specify the new background
color. 

 It does not re-render the whole thing.  I think building the js
function in Seaside would be not fun.


When you initially render the events be sure to give them a unique id by
setting something in the id inst var. (In the example its the first line
in the #renderCalendar: method)



Take care

Paul

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside