{"action":"created","issue":{"url":"https://api.github.com/repos/PrismLibrary/Prism/issues/3","labels_url":"https://api.github.com/repos/PrismLibrary/Prism/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/PrismLibrary/Prism/issues/3/comments","events_url":"https://api.github.com/repos/PrismLibrary/Prism/issues/3/events","html_url":"https://github.com/PrismLibrary/Prism/issues/3","id":60236042,"number":3,"title":"Modularity","user":{"login":"Michael-DST","id":2931376,"avatar_url":"https://avatars.githubusercontent.com/u/2931376?v=3","gravatar_id":"","url":"https://api.github.com/users/Michael-DST","html_url":"https://github.com/Michael-DST","followers_url":"https://api.github.com/users/Michael-DST/followers","following_url":"https://api.github.com/users/Michael-DST/following{/other_user}","gists_url":"https://api.github.com/users/Michael-DST/gists{/gist_id}","starred_url":"https://api.github.com/users/Michael-DST/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Michael-DST/subscriptions","organizations_url":"https://api.github.com/users/Michael-DST/orgs","repos_url":"https://api.github.com/users/Michael-DST/repos","events_url":"https://api.github.com/users/Michael-DST/events{/privacy}","received_events_url":"https://api.github.com/users/Michael-DST/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":23,"created_at":"2015-03-08T01:44:47Z","updated_at":"2015-03-23T01:00:08Z","closed_at":"2015-03-11T16:44:00Z","body":"Back on this thread:\r\n\r\nhttp://compositewpf.codeplex.com/discussions/581235\r\n\r\nThis was said:\r\n> Keep in mind, that not every platform has the concept of modularity or composition, and/or does not support it. For example, mobile apps don't support this concept, instead a navigation framework would be needed.\r\n\r\nI would like to challenge this statement.  Modularity to me is being able to succinctly compartmentalize a portion of an application.  It doesn't necessarily need to be something that is loaded dynamically.  I think of it is as clean separation of concern... an actual module, or perhaps an application \"content\" module.  I really enjoyed this in Prism 4.1 and utilized it extensively.  I was really able to modify the infrastructure around this feature to really build some awesome loading and initialization within my own framework.\r\n\r\nWhat ends up happening is that each \"page\" (or \"section\" or \"primary screen\") turns into a module, and each module has its own configuration (comprised of commands that are executed when the module loads).\r\n\r\nI used to have a project on CodePlex that was an outstanding example of this but then completely hosed it when I switched over to Git (and was sure that Silverlight was dead, and my code was no longer of value... D-O-H!).  I wish I could show it to you now so you can get an idea of what I am talking about.  It was pretty rad. :)\r\n\r\nAnyways, having this functionality (outside of the definition provided above) in a cross-platform manner would be pretty useful/valuable."},"comment":{"url":"https://api.github.com/repos/PrismLibrary/Prism/issues/comments/84741110","html_url":"https://github.com/PrismLibrary/Prism/issues/3#issuecomment-84741110","issue_url":"https://api.github.com/repos/PrismLibrary/Prism/issues/3","id":84741110,"user":{"login":"brianlagunas","id":835562,"avatar_url":"https://avatars.githubusercontent.com/u/835562?v=3","gravatar_id":"","url":"https://api.github.com/users/brianlagunas","html_url":"https://github.com/brianlagunas","followers_url":"https://api.github.com/users/brianlagunas/followers","following_url":"https://api.github.com/users/brianlagunas/following{/other_user}","gists_url":"https://api.github.com/users/brianlagunas/gists{/gist_id}","starred_url":"https://api.github.com/users/brianlagunas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brianlagunas/subscriptions","organizations_url":"https://api.github.com/users/brianlagunas/orgs","repos_url":"https://api.github.com/users/brianlagunas/repos","events_url":"https://api.github.com/users/brianlagunas/events{/privacy}","received_events_url":"https://api.github.com/users/brianlagunas/received_events","type":"User","site_admin":false},"created_at":"2015-03-23T01:00:08Z","updated_at":"2015-03-23T01:00:08Z","body":"While I would love to address each and every one of your concerns regarding why I think trying to configure a Prism application using nothing but XAML is a bad idea, I would rather do other things with my very limited free time.\r\n\r\nNot everything in WPF is done declaratively in XAML, so trying to support your position by implying that it is, doesn't help your cause.  XAML has its place, but this is not one of them.  Don't assume you were the first person to ever think about a declarative bootstrapper.\r\n\r\nBut, that's the beauty of open source.  While we will never do this in Prism, you have the complete freedom to spend the time and effort to do whatever you want to our framework in your own fork.\r\n\r\nTo end this conversation I will say, it doesn't really matter what I, or anyone else, thinks.  Just work on what gives you enjoyment, and if that's writing a framework that lets you configure Prism apps in XAML, go for it."}}