Support Forum

You can position fields using CSS, how come you need to move them to another container?

It was deemed not needed in material, it is hidden using CSS so you can override that if you want it some other way.

Before I open a feature request on moving default items into other containers, why do you want to do it?

It is the best option I can think of with whats currently available in the API. You can inspect the sources and match the settings there (required: true in this case)

Something like this in your items config:

// Remove default name field
name: false,
// Create your own field mapped to name
myNameField : { type : 'text', ref : 'name', name : 'name', label : 'My name' },

Hi,

Not sure I follow what you want to achieve, but you can both rearrange the built-in fields and add your own. More information here: https://bryntum.com/products/gantt/docs/guide/Gantt/customization/taskedit, and in this demo https://bryntum.com/products/gantt/examples/taskeditor/

Hi,

Not sure I follow what you want to achieve, but you can both rearrange the built-in fields and add your own. More information here: https://bryntum.com/products/gantt/docs/guide/Gantt/customization/taskedit, and in this demo https://bryntum.com/products/gantt/examples/taskeditor/

Hi,

from reading our sources it looks like you are correct, thanks for a clear and on-point report! Have opened a ticket on fixing it: https://github.com/bryntum/support/issues/9062

Hi,

thanks for reporting. It is an issue with the CSS for that specific demo, have opened a ticket on fixing it: https://github.com/bryntum/support/issues/9059