{"action":"created","issue":{"url":"https://api.github.com/repos/lhorie/mithril.js/issues/413","labels_url":"https://api.github.com/repos/lhorie/mithril.js/issues/413/labels{/name}","comments_url":"https://api.github.com/repos/lhorie/mithril.js/issues/413/comments","events_url":"https://api.github.com/repos/lhorie/mithril.js/issues/413/events","html_url":"https://github.com/lhorie/mithril.js/issues/413","id":54279887,"number":413,"title":"Reusable components.","user":{"login":"vivekimsit","id":1201766,"avatar_url":"https://avatars.githubusercontent.com/u/1201766?v=3","gravatar_id":"","url":"https://api.github.com/users/vivekimsit","html_url":"https://github.com/vivekimsit","followers_url":"https://api.github.com/users/vivekimsit/followers","following_url":"https://api.github.com/users/vivekimsit/following{/other_user}","gists_url":"https://api.github.com/users/vivekimsit/gists{/gist_id}","starred_url":"https://api.github.com/users/vivekimsit/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vivekimsit/subscriptions","organizations_url":"https://api.github.com/users/vivekimsit/orgs","repos_url":"https://api.github.com/users/vivekimsit/repos","events_url":"https://api.github.com/users/vivekimsit/events{/privacy}","received_events_url":"https://api.github.com/users/vivekimsit/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":32,"created_at":"2015-01-14T03:25:08Z","updated_at":"2015-01-24T18:13:34Z","closed_at":null,"body":"Hi,\r\n\r\nWhat about creating a repo which contains a set of reusable UI components? something like [Angular-UI](https://angular-ui.github.io/) or [Khan Acacdemy](http://khan.github.io/react-components/)\r\n\r\nI am ready to contribute.\r\n\r\nCheers!"},"comment":{"url":"https://api.github.com/repos/lhorie/mithril.js/issues/comments/71330263","html_url":"https://github.com/lhorie/mithril.js/issues/413#issuecomment-71330263","issue_url":"https://api.github.com/repos/lhorie/mithril.js/issues/413","id":71330263,"user":{"login":"barneycarroll","id":83627,"avatar_url":"https://avatars.githubusercontent.com/u/83627?v=3","gravatar_id":"","url":"https://api.github.com/users/barneycarroll","html_url":"https://github.com/barneycarroll","followers_url":"https://api.github.com/users/barneycarroll/followers","following_url":"https://api.github.com/users/barneycarroll/following{/other_user}","gists_url":"https://api.github.com/users/barneycarroll/gists{/gist_id}","starred_url":"https://api.github.com/users/barneycarroll/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/barneycarroll/subscriptions","organizations_url":"https://api.github.com/users/barneycarroll/orgs","repos_url":"https://api.github.com/users/barneycarroll/repos","events_url":"https://api.github.com/users/barneycarroll/events{/privacy}","received_events_url":"https://api.github.com/users/barneycarroll/received_events","type":"User","site_admin":false},"created_at":"2015-01-24T18:13:34Z","updated_at":"2015-01-24T18:13:34Z","body":"I think Bootstrap fulfils a different role (as far as we're concerned) in\r\nthat it provides standard functionality and appearance for various standard\r\nUI components that native HTML doesn't do it off the box. Implementation is\r\nkind of besides the point (I'm looking at using a Stylus fork, for\r\ninstance, for the sake of isomorphic CSS logic).\r\n\r\nWhen I'm discussing how to represent a piece of functionality with a UX\r\nspecialist, it's trivial to be able to suggest a composition of Bootstrap\r\ncomponents that provide the necessary low-level functionality. Whether I'm\r\ngoing to use jQuery or SASS or the baked-in Bootstrap theme is besides the\r\npoint — what matters is that we can easily communicate in shorthand about\r\nstandard user interaction mechanisms in terms of end-user functionality\r\nwithout bike-shedding about implementation details.\r\n\r\nPolymer on the other hand says everything is possible, but has reduced\r\nvalue in that the specifics get lost.\r\n\r\nTo put it another way: people who want to reinvent the wheel with a\r\nstandardised low-level API for defining the roundness of the wheel will be\r\ninterested in Polymer. People who assume a generic roundness out of the box\r\nand just want a variety of different wheels (with some tweaking down the\r\nline) will want a Bootstrap. You could implement Bootstrap components via\r\nPolymer, and implement the Polymer runtime in Mithril for all I care, but\r\nBootstrap has (really) useful specifics.\r\n\r\nWhich do we want to work on? I think the problem here is one of PR — we\r\nwant to solve other people's problems but we're not sure who those people\r\nare.\r\n\r\nOn Saturday, 24 January 2015, vivek poddar <notifications@github.com> wrote:\r\n\r\n> I am also not a big fan of bootstrap, I like polymer more and after that\r\n> the material design implementation by react is awesome.\r\n>\r\n>    1. https://www.polymer-project.org/docs/elements/\r\n>    2. http://material-ui.com/#/components/buttons\r\n>\r\n> Also, one thing about polymer is that it doesn't depend on any other third\r\n> party library\r\n>\r\n> —\r\n> Reply to this email directly or view it on GitHub\r\n> <https://github.com/lhorie/mithril.js/issues/413#issuecomment-71326710>.\r\n>\r\n\r\n\r\n-- \r\nRegards,\r\nBarney Carroll\r\n\r\nbarney.carroll@gmail.com\r\n+44 7429 177278\r\n\r\nbarneycarroll.com"}}