This question is locked. New answers and comments are not allowed.
I've approached this several ways and none seem to be doing what I need.
I have several requirements.
The ability to call a modal view for login from a "button".(client requirement) on the "home page"
Upon authentication , I need a menu view with "buttons" to call up the other views. (these buttons will not show until after authentication.
I've tried having both views on the same page and on different pages, and I just can't load the home view with no menu buttons showing only the login button, and after authentication hide the login "button" and show the menu "buttons".
The "buttons" are actually anchor tags loaded in a list view. Though I've tried input buttons and button tags as well.
I tried having the both views on the same web page and having them on separate web pages, and nothing seems to work as required.
Any help would be appreciated.
I have several requirements.
The ability to call a modal view for login from a "button".(client requirement) on the "home page"
Upon authentication , I need a menu view with "buttons" to call up the other views. (these buttons will not show until after authentication.
I've tried having both views on the same page and on different pages, and I just can't load the home view with no menu buttons showing only the login button, and after authentication hide the login "button" and show the menu "buttons".
The "buttons" are actually anchor tags loaded in a list view. Though I've tried input buttons and button tags as well.
I tried having the both views on the same web page and having them on separate web pages, and nothing seems to work as required.
Any help would be appreciated.
1 Answer, 1 is accepted
0
Hi Alan,
The scenario you described looks doable. I think the best approach would be to have one view and have different elements/buttons visible or hidden depending on the state of the user - whether he is authorized or not. You can data bind these elements visibility to a boolean field in the view model. When the user authenticates successfully, you need to just set the field value to true and bound elements will hide/show depending on their binding. You can take a look at the Kendo UI binding mechanisms in this documentation article.
If you are experiencing a concrete problem with implementing this, please open a support ticket and provide your project or a sample project, so that we can take a look.
Regards,
Martin Yankov
Telerik
The scenario you described looks doable. I think the best approach would be to have one view and have different elements/buttons visible or hidden depending on the state of the user - whether he is authorized or not. You can data bind these elements visibility to a boolean field in the view model. When the user authenticates successfully, you need to just set the field value to true and bound elements will hide/show depending on their binding. You can take a look at the Kendo UI binding mechanisms in this documentation article.
If you are experiencing a concrete problem with implementing this, please open a support ticket and provide your project or a sample project, so that we can take a look.
Regards,
Martin Yankov
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.