Resource View (vertical, multiple columns per day)

Originally reported on Google Code with ID 490

It would be nice to manage several users on week/day view using seperated columns.

I've started to implement this functionality.
(Fork: http://github.com/calendarlover/fullcalendar)
This first commit only contains small updates, and a example file (multi-users.html)

The all-day mode seems incompatible with this kind of view, hence it has to be disabled
to 
allow multi-user mode.

TODO:
- Fix overlapping bug which occurs when two events are displayed in the same time but
for 
different users
- Add callback on drop to enable/disable move between different users with eventually
an 
update of event.userId
- Add filter system to mask/unmask quickly specific user columns
- Handle short names in case of long usernames (quickfix could be using css: 
overflow:hidden)

If you want to implement some of these methods please let me know as for now I have
to stop 
for a while the developpement of this feature.

Reported by ljaures on 2010-05-20 12:01:10

[arshaw]

A working example would be great, I'd love to see this in a service application like
service vehicle trucks per area, or sales people per zone.

+-----+-------------------+--------------------+-------------------+
|     |      Monday       |      Tuesday       |      Wednesday    |              

+-----+-------------------+--------------------+-------------------+
| RSC | TRUCK 1 | TRUCK 2 |  TRUCK 1 | TRUCK 2 | TRUCK 1 | TRUCK 2 |
+-----+=========+=========+==========+=========+=========+=========+
|8AM  | Place 1 |  ****** |  ******  |  ****** | Place 1 | Place 2 |
+-----+          ---------+--------------------+                   +
|9AM  |         | Place 2 |  Place 1 | ******* |         |         |
+-----+---------+         +--------------------+----------         +
|10AM |  *****  |         |  Place 2 | Place 3 | Place 3 |         |
+-----+-------------------+--------------------+-------------------+

Reported by JamesMorris.ars on 2014-07-12 14:30:31

[arshaw]

discussion has been moved to the Scheduler’s issue tracker: https://github.com/fullcalendar/fullcalendar-scheduler/issues/5