Back in 2017, we started to work with Bryntum ExtGantt and ExtScheduler that we included in our application to manage timelines.
In the same time we introduced React and Redux librairies to manage components and states in our front-end.
We were new to these technologies and at this time we hesitated a bit on the overall architecture, on how to make these blocks play well together.
- Our first idea was to put all the data in Redux (like for a standard React/Redux app), and feed Bryntum Gantt/Scheduler (through ExtJS memory proxy) and other React components
- However discussing with your team, it looked it wasn't feasible because of ExtJS 6.5.x
[i]one + half-way[/i]
binding between Proxy and data object. (See post https://forum.bryntum.com/viewtopic.php?f=39&t=8966)
In 2020, we introduced the new generation of Gantt and Scheduler components (no-ExtJS), in some new pages of our app.
We now plan to upgrade the legacy pages (that used ExtJS) with non-ExtJS components.
For this reason, we would like to discuss with you what seems to be the best approach to handle Bryntum timeline, together with other React components on a Single Page Application.
Thanks to your understanding of the inner mechanism of the Bryntum Task/Dependency/Other stores, could you provide us your suggestions and insights about such an architecture, where we would like to keep things simple, possibly in a single place and easy to maintain.