1) The autocomplete and the combobox will come before the scheduler
=> Happy to read it
2) It makes sense for it to be a component a toolset like ours provides.
=> for sure
3) Checkboxes and radio buttons are things that are still not clear-cut in Blazor
=> can you explain me what isn't clear at this time ?
Posted on:09 Oct 2019 13:02
The autocomplete and the combobox will come before the scheduler, probably a multiselect will be before it too. The scheduler is simply something that a lot of people need and is actually quite hard to build, so it makes sense for it to be a component a toolset like ours provides.
Checkboxes and radio buttons are things that are still not clear-cut in Blazor, so we have to wait until they are determined - checkbox and radio button custom components will mostly be styling on top of the framework features.
UI for Blazor
Posted on:09 Oct 2019 12:54
+1 for Ben Hayat proposition.
Really like the way the Telerik's components are made but I don't really understand why Telerik decided to write scheduler components before core components like combobox but also checkbox, radio button or autocomplete. These components are :
* less complex to create than a scheduler
* used in more applications than a scheduler
Looking at the roadmap, I can see 2020. For a scheduler component, it's OK but for the core components, it's
Posted on:09 May 2019 01:10
Scheduler is a complex component. Nice to have, but I suggest Telerik team to focus on the core components needed for building business app for V1, after that they can extend to more compound components.
Just my two cents!
Posted on:08 May 2019 04:12
I took the liberty of clarifying the title a little bit so it is more generic and fits the component context.
I am leaving it open so the community can comment and vote on the request, which will let us gauge the interest and prioritize accordingly. The same applies for your other requests from today.
Progress TelerikUI for Blazor