{"action":"created","issue":{"url":"https://api.github.com/repos/MvvmCross/MvvmCross-AndroidSupport/issues/43","labels_url":"https://api.github.com/repos/MvvmCross/MvvmCross-AndroidSupport/issues/43/labels{/name}","comments_url":"https://api.github.com/repos/MvvmCross/MvvmCross-AndroidSupport/issues/43/comments","events_url":"https://api.github.com/repos/MvvmCross/MvvmCross-AndroidSupport/issues/43/events","html_url":"https://github.com/MvvmCross/MvvmCross-AndroidSupport/issues/43","id":93768901,"number":43,"title":"Improvements for showing Fragments","user":{"login":"Cheesebaron","id":249719,"avatar_url":"https://avatars.githubusercontent.com/u/249719?v=3","gravatar_id":"","url":"https://api.github.com/users/Cheesebaron","html_url":"https://github.com/Cheesebaron","followers_url":"https://api.github.com/users/Cheesebaron/followers","following_url":"https://api.github.com/users/Cheesebaron/following{/other_user}","gists_url":"https://api.github.com/users/Cheesebaron/gists{/gist_id}","starred_url":"https://api.github.com/users/Cheesebaron/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Cheesebaron/subscriptions","organizations_url":"https://api.github.com/users/Cheesebaron/orgs","repos_url":"https://api.github.com/users/Cheesebaron/repos","events_url":"https://api.github.com/users/Cheesebaron/events{/privacy}","received_events_url":"https://api.github.com/users/Cheesebaron/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-07-08T11:42:15Z","updated_at":"2015-09-22T23:51:02Z","closed_at":null,"body":"@martijn00 wrote this here #41:\r\n\r\n> The main problem with this change is that you use a new activity to show login. Currently the CachingFragment implementation is limited that you first need to show some ViewModel that is connected to the Hosting Activity to show other fragments.\r\n\r\n> To work around that it is possible to just use 1 Activity and for everything else use Fragments. The real solution would be to change the code of the FragmentsPresenter to allow to navigate to the correct ViewModel directly.\r\n\r\n> Let's say you start the app, depending on if you are already logged in you want to show the LoginViewModel, or the NewsViewModel(let's imagine a news app). It doesn't make sense then that you need to show MainViewModel first in order to show the NewsViewmodel.\r\n\r\n> My guess would be we need to turn the registering of fragments around. When we call ShowViewModel we should search for if it is a fragment, and if it is so, we should search for it's parent. I was thinking that could be done by adding an attribute to fragments containing it's parent."},"comment":{"url":"https://api.github.com/repos/MvvmCross/MvvmCross-AndroidSupport/issues/comments/142455464","html_url":"https://github.com/MvvmCross/MvvmCross-AndroidSupport/issues/43#issuecomment-142455464","issue_url":"https://api.github.com/repos/MvvmCross/MvvmCross-AndroidSupport/issues/43","id":142455464,"user":{"login":"vvolkgang","id":542036,"avatar_url":"https://avatars.githubusercontent.com/u/542036?v=3","gravatar_id":"","url":"https://api.github.com/users/vvolkgang","html_url":"https://github.com/vvolkgang","followers_url":"https://api.github.com/users/vvolkgang/followers","following_url":"https://api.github.com/users/vvolkgang/following{/other_user}","gists_url":"https://api.github.com/users/vvolkgang/gists{/gist_id}","starred_url":"https://api.github.com/users/vvolkgang/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vvolkgang/subscriptions","organizations_url":"https://api.github.com/users/vvolkgang/orgs","repos_url":"https://api.github.com/users/vvolkgang/repos","events_url":"https://api.github.com/users/vvolkgang/events{/privacy}","received_events_url":"https://api.github.com/users/vvolkgang/received_events","type":"User","site_admin":false},"created_at":"2015-09-22T23:51:02Z","updated_at":"2015-09-22T23:51:02Z","body":"Usage idea: Set the Activity + ContentId target as an attribute. Presenter would know how to deal with that, enabling the Core to navigate directly.\r\n\r\nGiven a Drawer + List & Detail + Phone & Tablet scenario, your `AppStart.cs` would be as simple and direct as:\r\n\r\n```csharp\r\npublic void Start(object hint = null)\r\n{\r\n    ShowViewModel<MenuViewModel>();\r\n    ShowViewModel<ListViewModel>();\r\n    if (Tablet)\r\n        ShowViewModel<DetailViewModel>();\r\n}\r\n```"}}