I would like to customise the Template using the technique described in the API reference, and similar to one of the other threads in this forum. I have used this example posted by an admin to another thread: https://stackblitz.com/edit/angular-gmuolt-jxzifm?file=app/upload.component.ts

However, I find that when you add an ng-template, all of the default template, including default nice UX is removed.

Is it possible to instead customise the existing Template, for example by adding a second"row" or "li".

If not, how would I go about recreating the UX elements from the default template to use in my custom template?

Thanks.

Hi Team,

I want to know whether the Kendo UI Window for Angular is free or paid. I just want to use window widget.

Thanks and Regards,

Akhil Bahl

Hi there,

We are having hard times to get our notifications right. Here is how our application works.

We have created a custom NotifcationService that abstracts notification for both desktops (Kendo UI) and mobiles (Ionic). Application components can trigger our NotificationService whenever needed. For instance, for the login page, we display a notification on error or success. Our notifications always have a title / header and a content message.

Kendo UI notification for Angular provides three different ways: string (doesn't allow html tags), TemplateRef and Component.

• The first option would have been perfect if we would have been able to put some tags to format the output.
• The second option has not been considered given our abstraction logic.
• We gave a try to the third option but without success for the time being. We created a custom NoticationComponent with two inputs: title (string) and message (string). We used ComponentFactoryResolver to get an instance of our Component and send it our variables. But when we try to use its instancefor NotificationSettings.content it fails:

whereas passing NotificationComponent directly to NotificationSettings.content works well (but it is then not possible to pass input variables).

Are we missing something here? What would have been nice is either to:

1. Allow tags in content string
2. Manage an alternative object such as title, message
3. Allow input parameters for Component rendering case

Thanks

C.

Thanks

Qubao Ruan

I have been trying to make this work with the component factory and it does not work. Here is my example:

https://stackblitz.com/edit/angular-ist5kj-dgzkke?file=app%2Fapp.component.ts

this works though:

https://stackblitz.com/edit/angular-ist5kj-n263kq?file=app%2Fapp.component.ts

however, the right way to do it is the first one when you create the component and you need to pass in data to the component through the instance. is there a way to make the first option work?