Unplanned
Last Updated: 22 Dec 2019 11:17 by ADMIN
Patrick
Created on: 06 Oct 2019 00:52
Category: Window
Type: Feature Request
26
Predefined windows

I would imagine most applications would use the Alert, Confim, Prompt concepts so it would be nice if they were built in.
It would further be nice if they were styleable and callable from c# code very similar to the wpf.
Of course as a default they could follow whatever css style is being used already.

RadWindow.Alert(text);
RadWindow.Confirm(text, () => {});
RadWindow.Prompt(text, result => {});

 

https://docs.telerik.com/devtools/wpf/controls/radwindow/features/predefined-dialogs

5 comments
ADMIN
Marin Bratanov
Posted on: 22 Dec 2019 11:17

Hi all,

Here's an example of something reusable I just made that may be interesting in case you have not implemented something similar already: https://github.com/telerik/blazor-ui/tree/master/common/confirm-button

 

Regards,
Marin Bratanov
Progress Telerik

 UI for Blazor
ADMIN
Marin Bratanov
Posted on: 09 Dec 2019 08:37

Hello Ben,

You can see our short-term plans in our roadmap page: https://www.telerik.com/support/whats-new/blazor-ui/roadmap. We take the community feedback actively when prioritizing items, so the more popular a given request becomes, the more likely it is to be implemented sooner rather than later. This also means that we can't commit to firm timeframes for all those features in the portal, and the best way to know when something gets done is to Follow its progress.

 

Regards,
Marin Bratanov
Progress Telerik

 UI for Blazor
Ben Hayat
Posted on: 07 Dec 2019 13:01
I forgot to mention this in my previous note.
Something like SweetAlert.
Ben Hayat
Posted on: 07 Dec 2019 08:45

Hi Marin;

Since this feature is approved, what is your guesstimate to have a native component for (alert, confirm, and prompt)?

This way during development we can temporary use the JS version and eventually move to Telerik's component.

Thanks!
..Ben

ADMIN
Marin Bratanov
Posted on: 07 Oct 2019 07:16

Hi,

In the meantime, you can achieve them by implementing your own components holding TelerikWindow instances that have some predefined settings/content as per your needs; then those components can expose methods that toggle the dialog, and parameters for size, content, title, etc.

On styling - in WPF you have the concept of defining a <Style> that you can reference, but this does not exist in the web. It is likely that styling will be done with CSS (e.g., through a class like telerik-blazor-prompt), and we will probably expose a template option for the content. Maybe the ability to have a custom CSS class would also be beneficial. Perhaps all those settings could go into the PredefinedDalogParameters argument the methods might take and it would be able to expose new features in the future without breaking the method signature. Perhaps even the EventCallback for closing the dialogs could go in there, so there is no need for overloads.

 

Regards,
Marin Bratanov
Progress Telerik

 UI for Blazor