Navigation like a site without framework

[eluser]Haskabab[/eluser]
[quote author="Crimp" date="1265482460"]I'm speaking generally. It's just a less (?) sinister variation of XSS. If values are not checked, external content of any kind can be loaded with the URL scheme. People interested in passwords and credit card numbers find this "feature" especially useful. CI, by default, checks if the controller and method exists and leaves it up to you to check and clean any arguments in further segments. FWIW: I do as brianw1975 above - split views into smaller parts for reuse. I stick a folder called /includes (carried over from EE) in the system /views folder and load those when and where needed. Remember that you can also load a view directly in the view - you do not need to pass it as a var from controller to view. Unless there is a really compelling reason to use GET and query strings, I'd go with the CI way of doing things. It's clean and easy.[/quote]

Okay understood, but let's say i want a dynamic user control panel included in my main view file. Which shows a login-form if the user is not logged in and a small control panel if the user IS logged in. Will i need to make 2 separate view files or can i check that in a view file? Because i think it's the job of the controller. Not sure about that, any thoughts?