Splitter Component

ADMIN

Marin Bratanov

Posted on: 28 Jun 2020 14:37

Yes, I am sure, Terje. This blog post is an exploration that showcases a very basic situation, but many other things are quite problematic, especially if you want them to be "native" Blazor (that is, to reduce the JS code a lot, or even get rid of it). To name a showstopper - two-way binding. We did try this with a movable Window in the initial releases we had, but the performance was not acceptable at all. The splitter will have the same hurdle - the size of the panes would depend on the drag action.

That is not to say that it is impossible to implement, but first we have to evaluate the framework roadmap so we don't have to invent, then reinvent, then rewrite; and then, if we have to write our own drag-and-drop framework - we have to write that too. Not impossible, but neither trivial, nor fast a task, that would mean something else that is highly requested would have to drop off the roadmap.

Regards,
Marin Bratanov
Progress Telerik

Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
Our thoughts here at Progress are with those affected by the outbreak.

Terje

Posted on: 28 Jun 2020 12:23

A core problem is that it will need drag-and-drop, which is something that Blazor cannot do right now

Are you sure?

https://chrissainty.com/investigating-drag-and-drop-with-blazor/#:~:text=Drag%20and%20drop%20API%20in,the%20drag%20and%20drop%20API.

Brent

Posted on: 01 Jun 2020 15:48

Thanks Marin. I'm glad you shared those details on the JS pulls with syncfusion. That is very enlightening to be aware of.

ADMIN

Marin Bratanov

Posted on: 01 Jun 2020 08:35

Hello Brent,

What I can say about this is that our components are truly native to Blazor, and we use JS Interop only where necessary and Blazor does not provide the needed abilities. With Syncfusion, at least at the time of writing, I am observing a lot of JS files being fetched for each component which makes me think that theirs are mostly wrappers over their JS solution. I am adding screenshots of this.

As for the grid column chooser - anyone else with the same need can Follow it here: https://feedback.telerik.com/blazor/1450105-column-chooser. The first step (a column header menu) is something we have planned for our R3 2020 timeframe.

Regards,
Marin Bratanov
Progress Telerik

Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
Our thoughts here at Progress are with those affected by the outbreak.

Attached Files:

Brent

Posted on: 31 May 2020 16:59

syncfusion demo shows what is possible

https://blazor.syncfusion.com/demos/splitter/default-functionalities/

and shucks, their datagrid already seems to have the custom column menu we like as well...

https://blazor.syncfusion.com/demos/datagrid/column-menu

maybe they've got a little lead in this space for now

ADMIN

Marin Bratanov

Posted on: 24 May 2020 12:08

Hello Kristijan,

You can monitor our roadmap page for details on what is planned for the longer term https://www.telerik.com/support/whats-new/blazor-ui/roadmap. At this point, I can't say when a splitter will be implemented. A core problem is that it will need drag-and-drop, which is something that Blazor cannot do right now - we will either have to implement an entirely home-grown solution for this, or wait for the framework to support it.

Regards,
Marin Bratanov
Progress Telerik

Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
Our thoughts here at Progress are with those affected by the outbreak.

Kristijan

Posted on: 22 May 2020 13:55

We also, would be this in plan?

Joe

Posted on: 22 Mar 2020 20:27

Yes we also need a Blazor splitter component.