Premium support for our pure JavaScript UI components


Post by chrisb »

Hey guys,

We're getting some pressure from our users for some abiltity to "inactivate" tasks.
In terms of what this means, we're still trying to understand, but the gist of it is something similar to what is described here: https://www.mpug.com/exploring-the-virtues-of-inactivating-tasks/

Is this on the roadmap at all? If not, could it be? Failing that, any hints on how we might implement this in the gantt?

Thanks

Chris


Post by arcady »

I've made a feature request for this: https://github.com/bryntum/support/issues/2981
Yet I cannot give any estimation at the moment. We're pretty packed w/ our current tasks I'm afraid.

If you want to implement this feature yourself I would start with checking the code of the following Engine files:
Gantt/lib/Engine/quark/model/scheduler_pro/ScheduledByDependenciesEarlyEventMixin.ts - the code of some methods there should be overridden to disable inactive predecessors affecting its successors (class docs)
Gantt/lib/Engine/quark/model/gantt/ScheduledByDependenciesLateEventMixin.ts - the code of some methods there should be overridden to disable inactive successors affecting its predecessors (for backward scheduling) (class docs)
Gantt/lib/Engine/quark/model/scheduler_basic/HasChildrenMixin.ts - the code of some methods there should be overridden to disable start/end dates rollup for inactive tasks (class docs).

Also you will need to prevent such tasks dates recalculations ..which sounds similar to manually scheduled tasks behaviour. So I would search for manuallyScheduled string in the Engine folder to see how it's done.
That's where I would start digging. :)

If you need that badly you can probably use our professional services for developing the feature. Please contact sales at bryntum.com for details if that works for you.


Post Reply