This is a migrated thread and some comments may be shown as answers.

Problem with KendoValueAccessor in angular 2.0.0-beta.0

36 Answers 561 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Vasil
Top achievements
Rank 1
Vasil asked on 17 Dec 2015, 09:59 AM
Hi all,

After I upgraded to latest Angular 2.0.0-beta.0 release my site stopped working. I tracked the problem and found out that it is due to KendoValueAccessor, which has dependency to 'angular2/angular2'. This package is not provided any more.

Regards,

Vasil

36 Answers, 1 is accepted

Sort by
0
Accepted
Sebastian
Telerik team
answered on 17 Dec 2015, 10:34 AM
Hi Vasil,

We are already working to support the Angular 2 Beta version which was released a couple of days ago but we are not there yet. Since many of the concepts compared to the Alpha release changed we will need some time to modify our integrations accordingly, therefore expect updates on this topic in the first months of 2016.

Note that our goal is to work in parallel with the next Anguar 2 updates in 2016, and provide formal support with Kendo UI shortly after the Angular 2 official release is announced by Google. Hence I hope you understand that at this juncture we cannot provide any definite estimates or commitments.

Kind regards,
Stefan Rahnev,
Product Manager, Kendo UI
 
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
 
0
Vasil
Top achievements
Rank 1
answered on 17 Dec 2015, 03:51 PM

Hi Stefan, Sebastian,

Thanks for your reply. In fact I was able to figure out the problem myself by creating the following directive (see attachment).

 Regards,

Vasil

0
Aaron Jessen
Top achievements
Rank 1
answered on 13 Jan 2016, 01:34 PM

Hi @Vasil,

Thanks a million for posting your KendoValueAccessor implementation. Can you please explain how you are referencing `kendo`, in order to satisfy `kendo.webComponents`  in line 9? I can't find 'webComponents' in any file (kendo.webcomponents.js does not contain an exported module, and kendo.all.d.ts does not contain any reference to `webComponents`).

Thanks,

 

Aaron Jessen

0
Vasil
Top achievements
Rank 1
answered on 14 Jan 2016, 09:00 AM

Hi @Aaron,

 

It is a bit of a hack. I created the following file and added it to typings folder.

 

Regards,

Vasil

0
Aaron Jessen
Top achievements
Rank 1
answered on 14 Jan 2016, 04:11 PM

Hi @Vasil,

Thanks, again, for posting your code. I suppose my newness to TypeScript is a factor, but after an hour of hacking around, I still can't get my IDE (IntelliJ IDEA) and my rendered page to stop throwing errors. Even if I satisfy TypeScript so Webpack will render, the web page says it cannot find kendo. Perhaps I'm missing something simple?

Since it could be a few months until Telerik releases full support for Angular 2, is it possible for you to throw together a basic plnkr when you get a chance to demonstrate how everything plays together? I'm figuring more people than just myself could benefit.

Thanks,

 Aaron

0
Lisa
Top achievements
Rank 1
answered on 20 Jan 2016, 05:26 PM

I too am trying Vasil's solution but am running into the same problem at runtime:  

Uncaught Uncaught ReferenceError: kendo is not defined

Evaluating http://192.168.1.11:9001/node_modules/kendo/angular2/kendo_value_accessor.js

0
VasVas
Top achievements
Rank 1
answered on 26 Jan 2016, 07:49 AM

Dear Telerik,

I am checking angular 2 support in kendo ui . In version 2016.1.112 there are Angular2 JS files but they seem to have no implementation.

Are there angular 2 beta decleretives for kendo ui/kendo ui Pro. Do you have sample application we could play with. Could you point me to resources. 

 

Yours,

 

Ariel

0
Sebastian
Telerik team
answered on 27 Jan 2016, 02:17 PM
Hello guys,

I recommend you review the following blog post which explains what to expect in 2016 for Kendo UI in terms of Angular 2 integration. Hope it will clarify our goal and set you expectations objectively.

Kind regards,
Stefan Rahnev,
Product Manager, Telerik Kendo UI
 
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
 
0
Jason
Top achievements
Rank 1
answered on 02 Feb 2016, 04:04 PM
Sebastian,

I know I am not the only one that is going to ask this, but please do not drop the support for Angular 2 that you guys are already have.  It is great that you are going to make Angular 2 native controls for Kendo, but those are over a year away.  There are many developers, your clients, that went with kendo because of the Angular support and need to start developing Angular 2 now while it is in Beta to have it ready by the time it is released.  

What we really need is a way to continue/start our Angular 2 development now with the current JQuery based widgets and when the time comes to update them to use your new Angular 2 native ones.  If not you basically halt the development for your clients.  

At this point I am fine with using the JQuery widgets inside of my Angular 2 applications and I know others will be also.  We need to way to proceed forward without waiting a year. 

Thanks,

Jason
0
Sebastian
Telerik team
answered on 02 Feb 2016, 04:37 PM
Thanks for the input, Jason.

I am afraid that supporting Angular 2 with our current Kendo UI offering in the same way as we did with Angular 1 (via directives) is against the core principles and concepts for UI components defined by Google with Angular 2, and renders such integration ineffective. That's the reason we chose a different path to support Angular 2 with Kendo UI, as explained in the blog post referenced below.

We'll be pushing incremental support for Angular 2 according to the timeline provided in the blog, so you should be able to embrace what we deliver with each dev iteration (via the continuous delivery model mentioned in the article) released to the public in 2016.

Regards,
Stefan Rahnev,
Telerik Product Manager, Kendo UI
 
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
 
0
Jason
Top achievements
Rank 1
answered on 02 Feb 2016, 05:28 PM
[quote]Sebastian said:  
We'll be pushing incremental support for Angular 2 according to the timeline provided in the blog, so you should be able to embrace what we deliver with each dev iteration (via the continuous delivery model mentioned in the article) released to the public in 2016.
[/quote]

That is what Telerik does not understand.  By not providing a way to bridge that time gap, you are effectively shutting down any Angular 2 development for clients that want to use Kendo as their UI controls.  I know our company can't wait for a year until kendo is supported on Angular 2 natively to start development on our new application, and I am sure others can't as well.  There will be no embracing what you deliver with each dev iteration, because Angular 2 will not be an option.  

I am in the process of trying out Vasil's approach.  Does this only work for a particular widget or is it a solution for all widgets?  I notice the (spin) so I figure it may only work with the numeric textbox.
0
Sebastian
Telerik team
answered on 03 Feb 2016, 12:07 PM
Unfortunately there's no conceptually right (by the latest Angular 2 components definition) and straight-forward means to provide Angular 2 shims for the existing Kendo UI jQuery-based widgets. That's why we are unable to provide any temporary solution you are requesting.

Feel free to utilize and extend the workaround provided by community members in this thread, if applicable for you.

Kind regards,
Stefan Rahnev,
Product Manager, Telerik Kendo UI
 
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
 
0
Diego
Top achievements
Rank 1
answered on 16 Feb 2016, 08:01 AM

[quote]Sebastian said:Unfortunately there's no conceptually right (by the latest Angular 2 components definition) and straight-forward means to provide Angular 2 shims for the existing Kendo UI jQuery-based widgets. That's why we are unable to provide any temporary solution you are requesting.

Feel free to utilize and extend the workaround provided by community members in this thread, if applicable for you.

[/quote]

 

Hi Sebastian:

actually we are trying to integrate Kendo UI into our new Angular 2 app without success, i mean we know about blog post and the new Angular 2 roadmap but we have to find the best way to integrate right now.

So we have dropped the use of wrapper "kendo.angular2.min.js" because we have found that it use the "angular2/angular2" module that it has dropped in favor of "angular2/core". We think right now to integrate Kendo UI WebComponet because we guess that native angular 2 implementation will be really close.

Do we are right? We really need the right path to integrate it thinking also on new Angular 2 development on Telerik side.

0
Sebastian
Telerik team
answered on 16 Feb 2016, 09:09 AM
Diego, at this point I don't think we can advise you anything more than what has already been discussed in this forum thread. Feel free to adopt the solution posted by community members here for your scenario.

Regards,
Sebastian
Telerik
 
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
 
0
Diego
Top achievements
Rank 1
answered on 16 Feb 2016, 09:17 AM

[quote]Sebastian said:Diego, at this point I don't think we can advise you anything more than what has already been discussed in this forum thread. Feel free to adopt the solution posted by community members here for your scenario.

[/quote]

Just to know Sebastian....are you going to drop "kendo.angular2.min.js" file or update it in meanwhile?

So thanks!

Diego

0
Sebastian
Telerik team
answered on 16 Feb 2016, 09:23 AM
Yes, this file will be dropped and we won't support it with our future Angular 2 integrations, Diego.

You can use the updated version of the file posted by community members in this thread as a temporary workaround, if applicable, having in mind that it's not supported by our team.

Hope this makes sense.

Regards,
Sebastian
Telerik
 
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
 
0
Jason
Top achievements
Rank 1
answered on 16 Feb 2016, 05:00 PM

What we have decided to do is to continue our Angular2 development by using kendo as require jquery widgets.  It is actually not too far off from how they are used in Angular 1X.  We are just creating the widgets on the ngAfterViewInit of the component, it may not be the best way or the Angular way but it will allow us to continue with Angular 2 and update when the actual Angular 2 widgets come out.

 

0
Diego
Top achievements
Rank 1
answered on 16 Feb 2016, 05:14 PM
[quote]Jason said:

What we have decided to do is to continue our Angular2 development by using kendo as require jquery widgets.  It is actually not too far off from how they are used in Angular 1X.  We are just creating the widgets on the ngAfterViewInit of the component, it may not be the best way or the Angular way but it will allow us to continue with Angular 2 and update when the actual Angular 2 widgets come out.

 

[/quote]

 Good to hear that someone else is going with this approach....i hope we could share some experiences if needed.

Diego

0
Bruce Denham
Top achievements
Rank 1
answered on 04 Mar 2016, 04:45 AM

Hey Jason, since Telerik won't help us start building Angular2 apps with existing jQuery controls, can you point me to an example of how you managed to do it via ngAfterViewInit? My company is facing the same problem with needing to start building our Angular2 app NOW. We'd be out of business if we waited for Telerik's KendoUI rewrite.

Thanks and hope to hear from you soon.

Bruce Denham

bdenham@topazti.com

0
Bruce Denham
Top achievements
Rank 1
answered on 04 Mar 2016, 05:06 AM

Sebastian -- I don't understand why Telerik isn't helping its current customers who need to start building their Angular2 apps now using current KendoUI jQuery controls. Does Telerik seriously think companies can wait a year to start building their Angular2 apps? Like most companies, we have to start development on our app now so we can be finished by the end of this year. If we had to wait a year for KendoUI to catchup, we'd be out of business. 

Our company recent spent over $9,000 on several KendoUI Pro licenses to ensure we'd get great support and backing for Angular2 development. So forgive me if I'm astonished over the lack of Angular2 customer support I'm seeing here and in other blog postings. Very disappointing.

0
Jason
Top achievements
Rank 1
answered on 04 Mar 2016, 05:33 AM

Here is what we are doing.  We have almost complete converting one of our small apps and it has worked out really well so far.

We are using Typescript with WebPack and NPM.

Sample Component:

@Component({
    selector: 'XXXX',
    templateUrl: 'XXXX.html',
    providers: [XXXXService],
})
export default class XXXXComponent {
      
    //just defindes what is in _uiControls
    private _uiControls: {
        panelBar: kendo.ui.PanelBar;
        treeViewCategories: kendo.ui.TreeView;
        isLoaded: boolean;
    };
 
    //#region Life Cycle Methods
    ngOnInit() {
        window['XXXXComponent'] = this;
    }
 
    ngOnDestroy() {
        delete window['XXXXComponent'];
    }
 
    ngAfterViewInit() {
        try {
            this.createUIControls();
            window['XXXXComponent'] = this; //not the best way to get the component reference to the global scope.  Is there another way?
        }
        catch (e) { Log.error(e); }
        finally {
        }
    }
    //#endregion
 
    constructor(private _xXXXService: XXXXService) {
        //need to initialize _uiControls here
        this._uiControls = {
            panelBar: null,
            treeViewCategories: null,
            isLoaded: false
        };
    }
  
    /**
 * Creates all the Kendo UI controls
 */
    private createUIControls(): void {
        this._uiControls.panelBar = $('#KPanelBar').kendoPanelBar(this.getPanelBarOptions()).data("kendoPanelBar");
        this._uiControls.treeViewCategories = $('#kTreeViewCategories').kendoTreeView(this.getTreeViewCategoriesOptions()).data("kendoTreeView");
        this._uiControls.isLoaded = true;
    }
 
    private getPanelBarOptions(): kendo.ui.PanelBarOptions {
        let component = this;
        let options: kendo.ui.PanelBarOptions = {
            activate: function (e) {
            }
        }
        return options;
    }
 
    private getTreeViewCategoriesOptions(): kendo.ui.TreeViewOptions {
        let component = this;
        let dataSource: kendo.data.HierarchicalDataSource = new kendo.data.HierarchicalDataSource({
            data: [],
            schema: {
                model: {
                    id: 'key',
                    children: 'items'
                }
            },
        });
        let options: kendo.ui.TreeViewOptions = {
            dataSource: dataSource,
            checkboxes: {
                checkChildren: true,
            },
            loadOnDemand: false,
            dataTextField: 'name',
        };
        return options;
    }
}

Here is the sample HTML view:

<ul id="KPanelBar" style="height:99%;overflow:auto;">
    <li id="pb_tags_header_categories">
        <label>TITLE</label>
        <div id="pb_container_categories" style="height:100%;">
            <div id="kTreeViewCategories" style="height:100%;"></div>
        </div>
    </li>
</ul>

This may not be the best approach, but it is working for us and it will give us a clean way to move towards the native Angular 2 widgets when they become available.  

The biggest thing to remember when doing it like this is that any interaction with the kendo widget requires you to use kendo coding style.  By that I mean you can't use Angular templates, you need to use templates in the kendo style.  You have to treat this like it is totally separated from Angular.  You will need to use DynamicComponentLoader.loadIntoLocation a lot to inject your Angular components into kendo areas.  An example of this would be when using the Tab widget.  We are having to use loadIntoLocation in order to get our Angular components inside the tab content section.

Over the last 3-4 weeks, working with this approach I can see how it would be extremely difficult for this to be the supported way of doing things in Angular 2.  The whole way Angular 2 works is completely different than Angular 1.X and there would be no way to have a supported product for Angular 2 using the JQuery widgets.  With that said, I am still disappointing that Telerik just threw it under the bus like they did.  They could have come out and said here is a template to get it working.  I think everyone would have realized that there would be issues going forward with the jquery widgets and the ultimate goal was to move to native Angular 2 widgets.  I totally expect to run into things that are going to be very difficult or impossible to figure out with this approach but at least we can start conversion.

Hope this helps.  I will email you so you have my email if you run into any issues.

0
Bruce Denham
Top achievements
Rank 1
answered on 04 Mar 2016, 05:55 AM
This is great, Jason, I really appreciate this! I will try it out on some prototypes and show the rest of our devs. Thanks so much!
0
Diego
Top achievements
Rank 1
answered on 04 Mar 2016, 07:15 AM

Hi to All...

we do the same as well so...no more KendoValueAccessor but pure jQuery.....we have just started to an Angular 2 approach.....so on the template we mark just the "div" as "#chart" and on Angular 2 Controller: 

@ViewChild("chart")
    private chartElement: ElementRef;

So on 
public ngAfterViewInit() {
        // We have to use jQuery wrapper because of kendo dependencies
        this.kendoGrid = jQuery(this.chartElement.nativeElement).kendoGrid(this.mainGridOptions).data("kendoGrid");
        // Now we have to bind to elements
        kendo.bind(this.chartElement.nativeElement, this.mvvmObject);
    }

 

But really it is really sad to use kendo template...instead angular 2 syntax....and we are really not sure that this approach will work correctly on big application!

Diego

0
Aaron Jessen
Top achievements
Rank 1
answered on 05 Mar 2016, 01:36 PM

I'm having some success using jQuery to instantiate a Kendo grid, while using Angular 2's DynamicComponentLoader to bind a templated grid column. Here's the Plnkr.

While the approach may not be best-practice, and it may or may not be applicable to other widgets, it's so far enabling our company to move forward with the adoption of Angular 2 while still using Kendo's Grid.

On a related note, I traipsed across an actual ng2-compatible HTML5 grid: Wijmo's FlexGrid. It appears to be fairly feature-rich, it fully supports Angular 2 beta, and their roadmap is much more reasonable (they're apparently releasing an ng2-beta-compatible set of their components sometime in March 2016, with full support being released when Angular officially rolls out 2.0...not a year from now *WTF Telerik?!*).

0
Petyo
Telerik team
answered on 07 Mar 2016, 12:43 PM
Hi Aaron,

thank you for sharing the approach you have taken. I am not going to go into details commenting the roadmap or the features of our competitors.

I woud like to assure you that, as far as Telerik is concerned, deciding on a fresh, native Angular 2 implementation (instead of trying to make something exising "compatible" with the framework) was not an easy one from both engineering and product development point. There is tons of work to be done on our side.

However, based on our experience with the Angular 1.* support, where we wrapped the existing widgets in directives, we do believe that a native Angular 2 implementation will result in best and most reliable implementation we can offer to our customers in the long run.  

Concerning the "WTF" phrase, I would really appreciate if we can keep the discussion on calm and constructive grounds. Thank you beforehand.


Regards,
Petyo Ivanov,
Kendo UI Architect

Telerik
 
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
 
0
Aaron Jessen
Top achievements
Rank 1
answered on 07 Mar 2016, 04:52 PM
Apologies for the phraseology, Petyo. I did not say it out of hostility, but rather frustration over having to spend so much time coming up with hacks for a product for which I shell out $1,000/year in order to stay current.

Some sort of wrapper or full, Telerik-built example to hold everyone over would still be a really nice gesture, even if it goes against best practices; from the length and tone of this thread, it seems there are enough people who would benefit.
0
Sebastian
Telerik team
answered on 08 Mar 2016, 10:39 AM
I understand your point, Aaron, yet having a half-baked temporary/intermediate solution which is truly a hack is not something we can build quickly and share with our customers. Even if we do so, it'll be very limited and won't work in many scenarios, which you'll probably concur will eventually cause more harm than good to people using it.

Building Kendo UI from scratch to create true Kendo UI Angular 2 components is a gigantic effort, and as much as we want, we cannot deliver it in a couple of months. We understand our users would prefer to have something in the interim, that's why we built our strategy in 2016 to deliver Kendo UI Angular 2 component in waves starting in May.

Even more, we'll try (although we cannot make a firm commitment right now) to flip the switch and make our Kendo UI Angular 2 repository public a month or so before May, to allow early adopters to fetch pre-preview bits and make early tests. There will also be public updates in-between the formal milestones during 2016 we shared (see this post for reference).

Hope this will help you gradually adopt our Kendo UI Angular 2 components immediately after they are available, and develop your Angular 2 apps in parallel. Your feedback when using the early bits will be much appreciate and drive the next advancements in our Kendo UI Angular 2 journey.

Hope this makes sense and let me know if you have additional feedback going forward.

Kind regards,
Stefan Rahnev,
PM for Kendo UI, Telerik
 
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
 
0
Diego
Top achievements
Rank 1
answered on 08 Mar 2016, 11:25 AM

Hi Stefan,

we are "future" customers really disappointed about new Angular 2 time adoption. We really know that making Kendo UI components angular 2 native is really big effort....but we need also to develop our products using a well know library road-map. So this change on your road-map didn't make us so happy.

So please make your Kendo repository public just because:

1) we need to "learn" how to integrate your components and it takes time

2) we also need to start integrate Sass and Bootstrap 4

Best regards,

Diego

 

0
Sebastian
Telerik team
answered on 08 Mar 2016, 11:45 AM
Thanks for chiming in, Diego. We'll do everything possible to make our (currently) private github repos public a bit in advance before the expected first Angular 2/React previews in May.

Regards,
Stefan Rahnev,
PM for Kendo UI, Telerik
 
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
 
0
alfred
Top achievements
Rank 1
answered on 16 Mar 2016, 08:47 AM

Thanks Diego and Jason for your input.  Wonder anyone sorted out how to load options template into KendoUI? I am not sure how to use dynamicComponentLoader to load angular component into the option.

Many Thanks

Eg. I want to display {{this._test}} inside the items in the ToolBarOptions. 

    private getTopNavBarTopOptions():kendo.ui.ToolBarOptions{
      let component=this;
      let options:kendo.ui.ToolBarOptions={
        items: [
          { template: "<label>{{this._test}}<label>"},
        ]
      }
      return options;
    }

    ngAfterViewInit() {
        try {
            this.createUIControls();
            window['TopNavBarComponent'] = this; //not the best way to get the component reference to the global scope.  Is there another way?
        }
        catch (e) { console.log(e);}//Log.error(e); }
        finally {
        }
    }

    private createUIControls(): void {
        this._uiControls.topNavBarTop =      $("#topNavBarTop").kendoToolBar(this.getTopNavBarTopOptions()).data("kendoToolBar");
        this._uiControls.isLoaded = true;
    }

with template:`

<div class="topNavBarTop" id="topNavBarTop"></div>

`

0
Jason
Top achievements
Rank 1
answered on 16 Mar 2016, 04:44 PM

I am not sure if you can.  Inside of Templates you have to use the Kendo template syntax and not Angular.

In your scenario it would be  { template: "<label>#=window['TopNavBarComponent']._test#<label>"},

There may be a way to load your current component into the template world that kendo has made but I have not found a way.  Does anyone at Telerik know if this can be done?  

 

 

 

0
alfred
Top achievements
Rank 1
answered on 17 Mar 2016, 11:57 PM

Thanks Jason for your fast response.

I sorted out my own question with dynamic component loader. Here is my temporary solution, which kind of work but is clumsy. Thanks for your suggestion above, which make small twist of local variables alot easier than making lots of sub component just for injecting into the kendo template.

 

...

 try {
 this.createUIControls();

 let topNavBarTop = $("#topNavBarTop");
 this.loader.loadNextToLocation(childComponent, this.elementRef)

 .then((result:ComponentRef) => {

 this.childComponent=result.instance;

this.childComponent._test="xxx";

topNavBarTop.append(result.location.nativeElement);


      });

            window['TopNavBarComponent'] = this; //not the best way to get the component reference to the global scope.  Is there another way?
        }
        catch (e) { console.log(e);}//Log.error(e); }
        finally {
        }

0
alfred
Top achievements
Rank 1
answered on 18 Mar 2016, 12:49 AM

By the way Jason, I tried your suggestion of  using inside the items of toolbar for eg.

{ template: "<label>#=window['TopNavBarComponent']._test#<label>"},

 

This normally would work in plain old kendo with our without angular1. However, this doesn't seems working in this hacked version after converting the kendo widget in ngAfterViewInit block. Above code just gives me plain "#=window['TopNavBarComponent']._test#" without any substitution as content of the label item of the toolbar.

0
Hugo
Top achievements
Rank 1
answered on 30 Mar 2016, 02:26 PM

Hi,

is there any chance that Kendo UI can be used with Angular2 upgrade adapter ? Right now, it cannot as directives doesn't follow the basic rules (see Using Component Directives here: Angular2 Upgrade) and directives are registered both as 'E' and 'A' which is simply not supported by the upgrade adapter (cannot have more than one type of restrict). Supporting this would allow early development in Angular2 with Kendo UI still working in AngularJS.

Thanks

0
Jessica
Top achievements
Rank 1
answered on 02 Aug 2017, 02:32 PM

Hi Jason,

did you by any chance managed to implement the onSelect of the kendo.treeview with the TreeViewSelectEvent? I am completely desperate, I am not able to get the orignially folderData from the e.node. I am able to get the internal uid of the li element that was selected, but it seems impossible to grab the treeview from my typescript code to search the right folderData like this: treeview.dataSource.getByUid(uid). I am currently working with Angular4. 

Any advice would be great!

Cheers, Jessica

 

0
Nencho
Telerik team
answered on 04 Aug 2017, 11:46 AM
Hello Jessica,

I noticed that you had submitted a similar question in another forum thread, which I had already replied. Please refer to it, in order to continue the correspondence there and hence avoid duplication.

http://www.telerik.com/forums/kendo-treeview-for-jquery-used-in-angular2-apps-with-typescript

Thank you in advance.

Regards,
Nencho
Progress Telerik
Try our brand new, jQuery-free Angular 2 components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.
Tags
General Discussions
Asked by
Vasil
Top achievements
Rank 1
Answers by
Sebastian
Telerik team
Vasil
Top achievements
Rank 1
Aaron Jessen
Top achievements
Rank 1
Lisa
Top achievements
Rank 1
VasVas
Top achievements
Rank 1
Jason
Top achievements
Rank 1
Diego
Top achievements
Rank 1
Bruce Denham
Top achievements
Rank 1
Petyo
Telerik team
alfred
Top achievements
Rank 1
Hugo
Top achievements
Rank 1
Jessica
Top achievements
Rank 1
Nencho
Telerik team
Share this question
or