Yes I did. It does not support keyboard. As I wrote, "implementing keyboard support requires side effects and state".
On Mon, Apr 24, 2017 at 3:50 AM, Lourens Rolograaf <[email protected]> wrote: > Hi Fransesco, did you read this? > https://medium.com/elm-shorts/a-reusable-dropdown-in-elm-part-1-d7ac2d106f13 > part 2 > https://medium.com/elm-shorts/a-reusable-dropdown-in-elm-part-2-9659ef988441 > > > Op donderdag 20 april 2017 23:45:07 UTC+2 schreef Francesco Orsenigo: >> >> >> I would add a dropdown. >> Even a simple dropdown poses some interesting challenges to the >> architecture: >> - Dropdowns are ubiquitous in web apps. >> - Dropdowns interact: when opening one, any other dropdown must close. >> - Implementing keyboard support requires side effects and state. >> - Dropdowns can have many different options; it can be disabled, it can >> have a button to clear its selection, it can require a selected value or the >> selected value can be a Maybe. >> - Dropdowns requires styling: how do you distribute style with an Elm >> package? More importantly, how do you organize it within the app? >> >> >> We might want to also consider a numerical input element. >> - How do I ensure that the input element always produces a number while, >> at the same time, allowing the user to use Backspace to delete the last >> cipher in the input? >> There are going to be different ways of doing this, it would be very good >> to be able to compare examples. >> >> >> >> >> >> On Wednesday, April 19, 2017 at 7:11:05 PM UTC+10, Peter Damoc wrote: >>> >>> Hello community, >>> >>> Scaling Elm apps seams to be a recurring topic. >>> >>> I was wondering if maybe we could negotiate a minimal set of >>> functionality, something similar to ToDoMVC, that could be implemented using >>> different approaches to explore what could be the best way to structure the >>> code. >>> >>> What should this minimal example cover and what this minimal example >>> should be (topic)? >>> >>> I'll start the list with some bits of functionality that I would like: >>> >>> - multiple pages with common structure (sidebar/navbar) >>> - navigation without reloading the app (SPA routing without the hash) >>> - authentication >>> - complex widget reuse (a module/widget that generates side-effects; e.g. >>> a weather widget, some stock ticker, an ad provided by a third party) >>> - styling (CSS) >>> >>> I would also like the example to cover real world concerns of: >>> - using a build manager to integrate with other technologies >>> - development mode - deployment build >>> - testing >>> >>> As for topic, I was thinking about an interface to the MusicBrainz >>> Database (a simplified interface). >>> >>> What do you think? >>> What bits of functionality would you like to see exemplified? >>> Are you aware of any other project (in other languages) that exemplifies >>> a minimal set of functionality and could be used as a template? >>> >>> >>> -- >>> There is NO FATE, we are the creators. >>> blog: http://damoc.ro/ > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Elm Discuss" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/elm-discuss/WDDrFq-uP58/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
