TabStrip with angular controller

[Mahmut]

Hello,
I'm experiencing a problem with TabStrip. With 2014 Q2 version, I can use tabstrip without a problem, in which its
contents bind angular controllers, and I can see that bound controller is activated when the tabstrip content is
loaded. But, yesterday I've tried to upgrade to 2015 Q1 version. After that, I see that the controller is no more activated.
Is there a difference between 2014 Q2 and 2015 Q1 versions? Or am I missing something?

Mahmut Zemheri

[Mahmut]

Hello again,
I've added a plunker sample.
(Working sample breaks down when you comment out the lines with 2015.* version)

Thanks,
Mahmut Zemheri

[Kiril Nikolov]

Hello Mahmut,

You are missing the correct script reference. Please see the updated example here:

http://dojo.telerik.com/idiHA

Regards,
Kiril Nikolov
Telerik

 

 

[Mahmut]

Hi Kiril,
Thanks for your reply.
Unfortunately, there is no difference. Again, while the sample with 2014 Q2 is working, 
the sample with 2015 Q1 is not working (even with the script reference which you gave).

Thanks
Mahmut Zemheri

[Kiril Nikolov]

Hello Mahmut,

 

There was an error in the way widget is initialized, please note that you do not need to initialize the tabstrip widget with jQuery when AngularJS directives are used. Please see the updated example here:

 

http://plnkr.co/edit/kWoej5HcQaSPagceyQkp?p=preview

 

Regards,
Kiril Nikolov
Telerik

 

 

[Mahmut]

Hello Kiril :(,

I think, there is a serious problem with communication. Let me try to be as clearest as possible.
With 2014 Q2, the result is "Tab 1 Content" (in evidence 1).
With 2015 Q1, the result is "{{name}}" (in evidence 2, and the sample prepared by yourself).
Why on earth, the result is "{{name}}" with 2015 Q1 version (regardless of the script reference or the widget initialization method you choose)?
I feel that there is a bug in 2015 Q1 version with a great possibility.

Mahmut Zemheri

[Mahmut]

Hello again,

Just another sample with 2014 Q2 and 2015 Q1.
Please, do notice that initialize function does not work with 2015 Q1 (in contrast with 2014 Q1).

Mahmut Zemheri

[Mahmut]

The same problem with kendo window.
2014 Q2 vs 2015 Q1.
Is there any workaround for this problem?

Mahmut Zemheri

[Petyo]

Hello Mahmut,

I am sorry for the delayed response. the change you refer to is intentional. The Q2 2014 behavior was, in fact, an incorrect one. Widgets not instantiated as directives interfered with the AngularJS compilation. After several customer requests we had to change that.

Like Kiril suggested, if the tabstrip is instantiated with an AngularJS directive, the problem should be addressed.

Regards,
Petyo
Telerik

 

 

[Mahmut]

Thanks Kiril and Petyo,

What if, you have to instantiate a kendo-widget that bound an angular controller at runtime (for example, by user preference)?
Anyway, if it is intentional and requested by several customers, we have nothing to do but review whole project
and hope that upcoming versions not to include this kind of surprises.

Mahmut Zemheri

[Petyo]

Hello,

there are plenty of means to achieve that. In fact, the topic has been broadly covered under the "AngularJS for jQuery developers" title, which discusses such cases in details.

Regards,
Petyo
Telerik

 

 

[Mahmut]

Hello Petyo,

Thank you very much, for your kindness.
I'll examine the link carefully.
We're just having some difficulties in changing the design pattern in the middle of the development process.
In fact, there were no problem, if we began with 2015 Q1. 

Best regards,
Mahmut Zemheri

[Mahmut]

Hello Petyo,

Thank you very much, for your kindness.
I'll examine the link carefully.
We're just having some difficulties in changing the design pattern in the middle of the development process.
In fact, there were no problem, if we began with 2015 Q1 version :)

Best regards,
Mahmut Zemheri

[Mahmut]

Hello Petyo,

Thank you very much, for your kindness.
I'll examine the link carefully.
We're just having some difficulties in changing the design pattern in the middle of the development process.
In fact, there were no problem, if we began with 2015 Q1 version :)

Best regards,
Mahmut Zemheri

[Mahmut]

Note: Sorry for multiple messages with the same content (resulting from 500 internal server errors).

[Kiril Nikolov]

Hello Mahmut,

Apologies for any inconveniences.

If something comes up - please do not hesitate to contact us.

Regards,
Kiril Nikolov
Telerik