SPA: Can we replace ExtJs with Bryntum ?

[vadim_g]

Hi all & Bryntum team.

We are evaluating this library with the goal to use it at some point as a replacement for the ExtJs Modern toollkit we are using in our big SPA.

Because we use the trial mode for our evaluation, we can't really get the full picture how Bryntum widgets could work and be used a bit outside of their main goal (to be used in Grids, Scheduler...). I mean these cases:

1. Can we rely 100% on Bryntum's Grid and its widgets/fields, only, to build a SPA, as we do on ExtJs now ? See 2.

2. How to build heavy Forms like in ExtJs. I see most/all the fields have errors handling based on some given validation, but can't see (by a quick look) anything related at the container level which could be used to check the dirty and validation state of all fields within it. (something like the Form Manager https://docs.sencha.com/extjs/7.5.0/modern/Ext.field.Manager.html)

3. Is there any more detailed examples or guides except this example which has the source code hidden: https://bryntum.com/products/grid/examples/webcomponents, on how we could possibly use the widgets within a web app based on web components ?

Finally would be great for Bryntum team to consider in the future the posibility to offer for trial mode the source code as well, so we can evaluate better what we are about to buy.

Thanks.
Vadim

[mats]

Hey Vadim!

Glad you are evaluating our widget library!

1. Yes you can!

2. We are pretty close to what Ext JS has, you can look at the container class for top level APIs like https://bryntum.com/products/grid/docs/api/Core/widget/Container#property-isValid which queries all children for validity. If you miss any other specific APIs we'd be happy to look at adding it.

3. We don't use web components extensively ourselves but we have this class https://bryntum.com/products/grid/docs/api/Core/customElements/WidgetTag which can wrap one of our Widgets (used by GridTag in the example you linked). Happy to have a chat over a call if you like, feel free to book a slot here: https://calendly.com/bryntum/30min

Finally would be great for Bryntum team to consider in the future the posibility to offer for trial mode the source code as well, so we can evaluate better what we are about to buy.

Fair point! Hard to balance protecting IP while also giving customers easy access to validate source code, we'll discuss internally.

[vadim_g]

Hi Mats,

Great to hear from you.

1. Awesome.

2. We would need some Api for dirty state and reset/resetOriginalValue at the field and container level. If this is not yet implemented, I assume it should not take much to add them (ourselves).

3. Good, I think WidgetTag it's enough for now, for what we may need.

4. One more, what about a hash Router ?

Thanks.
Vadim

[mats]

1. Field level already has this built-in so it would be easy to add APIs to handle this on the Container level.

2. No plans for a router but it's again something you could implement on your own or use a 3rd party lib to solve.