You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 15, 2019. It is now read-only.
I had an idea that I could isolate all the kendo directives and code into nested angular directives so that I essentially "wrap" kendo and deal with only "pure" angular code above the directive layers. Then, an angular developer could be brought in and consume my directives without having to learn the kendo suite ... kind of the whole "wrap expert systems" approach.
But it seems like the wiring up of the directives would be tricky due to the events and datasources.
Am I heading down a deep, dark rabbithole that I shouldn't? In your opinion of course.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
just getting into kendo angular and excited about it.
I was reading this article ... great stuff from Burke Holland
http://blogs.telerik.com/kendoui/posts/14-02-26/a-few-angular-kendo-ui-best-practices
I had an idea that I could isolate all the kendo directives and code into nested angular directives so that I essentially "wrap" kendo and deal with only "pure" angular code above the directive layers. Then, an angular developer could be brought in and consume my directives without having to learn the kendo suite ... kind of the whole "wrap expert systems" approach.
But it seems like the wiring up of the directives would be tricky due to the events and datasources.
Am I heading down a deep, dark rabbithole that I shouldn't? In your opinion of course.
The text was updated successfully, but these errors were encountered: