Hi Krishna
Regarding the first part, the are several approaches that can be used to present a login screen. The one you are describing seems to be a valid one. Either you could show the Shell window only after the user is authenticated in the login screen or show the Shell from the beginning but only load the content after the authentication is completed.
Regarding the second part of the views and the regions, there is no specific rule about how to structure your views or how many regions you should use. Those parameters will change depending of each scenario and what you are trying to achieve. Hence, it would be helpful if you could explain for what each view and region is used for, the navigation flow of your application, etc.
If you want to post a sample in this thread, you could upload it to a file hosting service of your preference (e.g. SkyDrive) and post the link here.
Thanks
Damian Cherubini
http://blogs.southworks.net/dcherubini
Regarding the first part, the are several approaches that can be used to present a login screen. The one you are describing seems to be a valid one. Either you could show the Shell window only after the user is authenticated in the login screen or show the Shell from the beginning but only load the content after the authentication is completed.
Regarding the second part of the views and the regions, there is no specific rule about how to structure your views or how many regions you should use. Those parameters will change depending of each scenario and what you are trying to achieve. Hence, it would be helpful if you could explain for what each view and region is used for, the navigation flow of your application, etc.
If you want to post a sample in this thread, you could upload it to a file hosting service of your preference (e.g. SkyDrive) and post the link here.
Thanks
Damian Cherubini
http://blogs.southworks.net/dcherubini