Your grid has dates. Now someone wants a timeline.

It starts with "Can we see this on a timeline?"

Then it becomes "Can I drag this to a new date?" And then: "Can everything that depends on it move too?"

That's the moment a UI feature turns into a scheduling engine. Drawing bars on a timeline is the easy part. Moving one, and correctly recalculating everything it affects, is where the real work begins: dependencies, constraints, resources, working calendars, and performance across thousands of tasks.

Whether your timeline shows the same records as your grid or a completely separate dataset, the question is the same: should you build this yourself, or use a scheduling engine that already exists?

In this live session, Mats Bryntse, founder of Bryntum, who has been building scheduling components since 2009, shows what's hiding under that simple request. He uses Bryntum Gantt as the main example.

You'll leave knowing:

• Where a timeline becomes a scheduling problem: dependencies, constraints, resources, working calendars and rescheduling, and why solving that properly can take months of specialist engineering.
• What a scheduling engine actually does for you: watch Bryntum Gantt handle that complexity live, then see where Scheduler, Scheduler Pro and Calendar fit as the problem changes.
• How to decide whether to build or buy for your own application, and where to start evaluating Bryntum if buying makes sense.

Who it is for:

Front-end and full-stack developers who have a scheduling, planning or resource problem, or can see one coming. Using AG Grid? You'll see how the two work together.

About the partnership:

AG Grid and Bryntum are partners, two specialist products built to work well together. AG Grid handles your data. Bryntum handles what happens to it over time.