Using a custom filter on the resourceStore of each Scheduler, you should be able to share a CrudManager.
Each Scheduler would have a completely different visible set of resources. Dragging an event from one Scheduler to the other would have to be handled specially. The "drop" gesture would not be a remove and add. It would be an assignment to a new resource (possibly a new time)
There will be only one CrudManager. The second Scheduler wouldn't need one. All the data resides in the first scheduler.
The event store is shared, so that's fine.
The second Scheduler's resource store loads itself from the first Scheduler's resource store, and will refresh itself whenever that master store changes. That is the contract of a chained store.
I cannot run that. I have no PHP on my MacOS system. Apple see fit to destroy people's installation during what they fondly regard as "upgrades".
I can suggest that you set a breakpoint in the second Scheduler's resource store's fillFromMaster method.
If it works as it should it should use allRecords from its master store, which means the full dataset, ignoring the master store's filtering, and apply its ownchainedFilterFn to ingest only the ones you want.
I cannot run that. I have no PHP on my MacOS system. Apple see fit to destroy people's installation during what they fondly regard as "upgrades".
I can suggest that you set a breakpoint in the second Scheduler's resource store's fillFromMaster method.
If it works as it should it should use allRecords from its master store, which means the full dataset, ignoring the master store's filtering, and apply its ownchainedFilterFn to ingest only the ones you want.
Thanks again, Animal! Yeah, MacOS... I'm so happy we Dockerized our setup (initially) for production but helps for MacOS too.
Please see this video. You guys at Bryntum running a PHP server for the CrudManager example so I dump my code right in there
Thanks a lot for patience and complete test case. I applied some changes and tested it online (complete code posted in the ticket), but it doesn't works as expected. Seems like you cannot now share one crudManager instance via 2 schedulers.
I've opened another ticket to fix this problem https://github.com/bryntum/support/issues/5668