Dapr vs. DHTMLX

Rapid development of web applications: DHTMLX provides a set of pre-built UI widgets that can be easily integrated into web applications, which makes it well suited for developing applications quickly. DHTMLX is well suited for building enterprise-level applications that require complex UI elements and data visualization. DHTMLX is less appropriate for Simple applications: If you are building a simple application that does not require a complex UI, DHTMLX may be overkill, and you may be better off using a lighter-weight framework.

Incentivized

• We got a response and fix for every issue we opened a ticket for
• The components are full with quite a lot of feature
• The team is responsiveness is very quick

• We would like to have more cell controls (like a Date Time Picker, Date Range Picker)
• In the cell editing mode we would like to have a better integration into the Angular world

With regard to the two major components we used, namely the tabular representation and the graphical modeler, we were able to effectively replace the existing building blocks of our applications by integrating them. We were able to retain existing functionalities and benefit from a significant enhancement with what DHTMLX offers natively. This made it easy for us to get our end-users to adopt the change.

We looked at Kendo UI for ASP.Net Core as it has a Gantt chart but it was not as close a fit to our requirements as the DHTMLX Gantt Resource Management component. We'd have had to do much more work to make this fit.

Incentivized

• Rapid development of web applications
• Rich data visualization tools, which makes it ideal for building data-driven applications
• Suited for building enterprise-level applications

Incentivized