Issue 1466: FullCalendar ResourceViews
Status:  Invalid
Owner: ----
Closed:  Aug 2013
Reported by martinle...@gmail.com, Jul 17, 2012
Hi all,
I have tested the resource view(resourceDay) found in http://tux.fi/~jarnok/fullcalendar-resourceviews/.
I did it successfully without any problem, however, once I put more events(50 events) in the option "resources", the calendar become very very slow(35seconds). The way I generated the resource objects is exactly the same shown in the url provided above.

I am pretty sure it's not caused on the server, but at the client

Can anyone tell me what's going on here? 

Your kindly assist will help me a lot.
Thanks
Aug 10, 2012
#1 mkirthik...@gmail.com
i had the same problem, so i added some pagination. (jPaginate)
Aug 18, 2013
Project Member #2 adamrs...@gmail.com
(No comment was entered for this change.)
Status: ReproTemp
Aug 25, 2013
Project Member #3 adamrs...@gmail.com
This message is being bulk-sent to a number of issues, both [very] old and new.

I have been working on taming this issue tracker, which has gotten out of control after months of neglect. You are receiving this message because I could not successfully reproduce the bug you were reporting with a reasonable amount of effort. I have written some new bug-report guidelines to be used by all bug reports going forward:

    http://arshaw.com/fullcalendar/wiki/Report-a-Bug/

Its salient point is that all bug reports should have an isolated demonstration, viewable online with a tool like JSFiddle.

If the bug you originally reported is still important to you, could you please first try the latest version of FullCalendar and see if it is fixed? If not, could you please file a NEW bug report that follows the new guidelines? This issue will not be monitored for further comments.

I'm sorry I have taken so long to respond to many of your request, and I'm sorry if this new procedure causes extra work for you. Going forward, the issue tracker will be much more of a well-oiled machine.

Again, if you must, PLEASE SUBMIT A *NEW* BUG REPORT (following the new guidelines) INSTEAD OF COMMENTING ON THIS ONE. Further comments on this report will be ignored. Thanks.
Status: Invalid
Labels: Type-Bug