Facets for calendar designed to be used primarily for markup templates creation. (html markup with some macrosubstitutions of calendar controls, links and etc...) It's rebuilds on every calendar scroll and etc.. So we do not tested and even designed the usage of complex components (which requires scripts objects and etc) inside the calendar. I even can't imagine why you need dataFilterSlider inside calendar :)
facets for Calendar.
So not all facets are affected by limited kind of content inside. Or?
For example, in rich:togglePanel there are also facets, but can have any content inside. Am I right? So called complex components are not impossible but needs more client-server-overhead ?
I even can't imagine why you need dataFilterSlider inside calendar :)
Imagine a Calendar-Object with a facet in which I can provide checkboxes or even dataFilterSlider, with which the user can slide faster from one month to another or can select preselected timespans between two calendar-Objects faster. You are right, I do not need that as I can provide another tab or something else in which I can provide these missing functionality inside a rich:calendar-facet. But it s a little pitty limiting the possiblity of the the expression of my creativity :-)
For example, in rich:togglePanel there are also facets, but can have any content inside. Am I right?
panels encoded on server side and calendar is almost the only component rendered completelly at client side script. And its server side knows almost nothing about markup.