{"action":"created","issue":{"url":"https://api.github.com/repos/aurelia/ux/issues/19","repository_url":"https://api.github.com/repos/aurelia/ux","labels_url":"https://api.github.com/repos/aurelia/ux/issues/19/labels{/name}","comments_url":"https://api.github.com/repos/aurelia/ux/issues/19/comments","events_url":"https://api.github.com/repos/aurelia/ux/issues/19/events","html_url":"https://github.com/aurelia/ux/issues/19","id":191134134,"number":19,"title":"ux-select","user":{"login":"fkleuver","id":9655331,"avatar_url":"https://avatars.githubusercontent.com/u/9655331?v=3","gravatar_id":"","url":"https://api.github.com/users/fkleuver","html_url":"https://github.com/fkleuver","followers_url":"https://api.github.com/users/fkleuver/followers","following_url":"https://api.github.com/users/fkleuver/following{/other_user}","gists_url":"https://api.github.com/users/fkleuver/gists{/gist_id}","starred_url":"https://api.github.com/users/fkleuver/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fkleuver/subscriptions","organizations_url":"https://api.github.com/users/fkleuver/orgs","repos_url":"https://api.github.com/users/fkleuver/repos","events_url":"https://api.github.com/users/fkleuver/events{/privacy}","received_events_url":"https://api.github.com/users/fkleuver/received_events","type":"User","site_admin":false},"labels":[{"id":483620703,"url":"https://api.github.com/repos/aurelia/ux/labels/component","name":"component","color":"e62787","default":false},{"id":440377893,"url":"https://api.github.com/repos/aurelia/ux/labels/feature","name":"feature","color":"000000","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":17,"created_at":"2016-11-22T21:52:16Z","updated_at":"2016-11-24T19:54:41Z","closed_at":null,"body":"I worked with both Aurelia and Materialize for a while now, and I'd love to help out with a component or two.\r\n\r\nRecently I've made a sort of dropdownlist/autocomplete combo in Aurelia (from scratch).\r\n**A demonstration can be seen here**: http://fkleuver.azurewebsites.net/\r\n\r\nIt responds to different UI events like `arrow up`/`down` (or `mouse wheel`) for selecting items, `enter` to pick an item, `esc` to close it, and simply typing in it in order to filter the list. \r\n\r\nIt may be doing too much for a single usercontrol, I just had fun creating it with Aurelia.\r\nI'd like to try and make it fit in with the rest of the `ux` components.\r\n**Here is the source code so far:** https://github.com/fkleuver/aurelia-starter/tree/master/src/resources/elements/dropdownlist\r\n\r\nI'm thinking about \"cutting it in half\", making a normal `select` and a normal `autocomplete` component out of it.\r\nI didn't have the `ux` project in mind when I originally created it, so I will still need to make it look like this but I don't expect much trouble there: http://materializecss.com/dropdown.html\r\n\r\nWould something like this be functionally okay or is it preferable to stick to the native html `select` element?\r\nAny thoughts on which direction I should take this?\r\n\r\nMaterialize.js also does something similar to what I'm doing (discards the `select` and builds a custom list from scratch) and I find it a bit clumsy to work with (not a big fan of jQuery anymore), which is why I built my own version to begin with.\r\n\r\nFYI There is a dependency on GSAP but I'll get rid of that and replace it with native javascript (typescript)."},"comment":{"url":"https://api.github.com/repos/aurelia/ux/issues/comments/262837812","html_url":"https://github.com/aurelia/ux/issues/19#issuecomment-262837812","issue_url":"https://api.github.com/repos/aurelia/ux/issues/19","id":262837812,"user":{"login":"fkleuver","id":9655331,"avatar_url":"https://avatars.githubusercontent.com/u/9655331?v=3","gravatar_id":"","url":"https://api.github.com/users/fkleuver","html_url":"https://github.com/fkleuver","followers_url":"https://api.github.com/users/fkleuver/followers","following_url":"https://api.github.com/users/fkleuver/following{/other_user}","gists_url":"https://api.github.com/users/fkleuver/gists{/gist_id}","starred_url":"https://api.github.com/users/fkleuver/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fkleuver/subscriptions","organizations_url":"https://api.github.com/users/fkleuver/orgs","repos_url":"https://api.github.com/users/fkleuver/repos","events_url":"https://api.github.com/users/fkleuver/events{/privacy}","received_events_url":"https://api.github.com/users/fkleuver/received_events","type":"User","site_admin":false},"created_at":"2016-11-24T19:54:41Z","updated_at":"2016-11-24T19:54:41Z","body":"I made this one before: https://github.com/fkleuver/aurelia-starter/blob/master/src/resources/elements/dynamic-html.ts\r\n\r\nCould use that one as-is like so: `<dynamic-html html.bind=\"html\" />` but it feels like that wouldn't be much better than just using `compose`.\r\n\r\nIf it is (idk about the overhead of having to compile a custom element that encapsulates such logic), though, then wouldn't it be more useful to just add a component like that to `templating-resources` so it can be reused within the library and by other people? I see people asking for something like this on SO quite frequently. I also use it myself alot."}}
{"actor":{"display_login":"fkleuver"}}