Well get to PR'ing into `elm-mdl`, or make a new one based on `elm-parts` (which is what `elm-mdl` is built off of)? ^.^
On Thursday, September 1, 2016 at 12:22:31 PM UTC-6, Zachary Kessin wrote: > > I for one would love to see a really nice nestable component library > somewhat similar to the good parts of ExtJS in elm. The problem is that I > think how to do that with a great API and in a type safe way is probably > not as obvious as I think it is. I think it would need to have someone put > 12-18 months of work into it to get it going. > > I at least can not do that even if Ihad the skills > > Zach > ᐧ > > On Thu, Sep 1, 2016 at 8:06 PM, Peter Damoc <[email protected] > <javascript:>> wrote: > >> I'll venture a personal opinion regarding your 4 questions: >> >> 1. Elm compiles to something like ECMAScript3 so... no modules in the >> output. Also, the JS output is designed to me more like an assembly kind of >> thing and it is planned to maybe someday move beyond JS. I don't think that >> Elm output was designed to be used as a library from JS. >> >> 2. This is an issue for the minimizer. You can import your icons module, >> use the 3 you need and the minimizer should remove the ones you are not >> using. In other words, currently, Elm will include everything but it will >> do it in such a way that tools like Closure compiler can remove the unused >> stuff. >> >> 3. Hot reloading / Hot swapping used to work in the old elm-reactor and >> will make a comeback RealSoonNow™. >> >> 4. Elm favors doing things the right way and CSS is a very complex topic >> so I guess it got on the back-burner. I have tried to start discussions on >> this subject before and there was simply not enough interest. There is a >> huge opportunity to do something interesting in that domain but that would >> involve designing a very large scale API and I've lost hope that we will >> see this in a foreseeable future. There is however an opportunity here: you >> can start a discussion about an approach that you might find >> intriguing/useful. >> >> Now, considering the title you picked for this topic, I want to point >> something else out. >> Elm doesn't have an official approach to building something like an UI >> toolkit (frequently used components library). >> This in itself is a very complex topic with a lot of moving parts that >> might have also ended up on the back-burner. >> >> The topic of components keeps resurfacing quite frequently and what I've >> seen so far is mostly a downplay of the issue. >> >> People who want to implement webapps with simple, CSS only, >> components/widgets can use an external CSS and classes in elm-lang/html. >> People who want more sophisticated components/widgets are out of luck. >> Either they need to use a hack like elm-parts that uses techniques >> actively discouraged by Evan or they submit to a world of boilerplate. >> I even went so far as to create an example of this boilerplate: >> https://github.com/pdamoc/elm-boilerplate-example >> It generated a small discussion on Slack but... no other effect. >> >> I guess people are using Elm to implement either CSS only kind of webapps >> with dynamic content served by Elm OR they have figured out how to >> integrate sliders, date pickers, light-boxes, dropdowns and other amenities >> available in the JS driven toolkits (I could not figure that out as I don't >> have a JS background). >> >> >> >> >> On Thu, Sep 1, 2016 at 6:49 PM, suttlecommakevin <[email protected] >> <javascript:>> wrote: >> >>> *Forgive me if I have missed something or am asking about something >>> that's been reposted frequently.* >>> >>> Let's use a simple example: a custom set of SVG icons, for use in >>> Buttons. >>> Here are my rookie questions: >>> >>> *Is the Elm compiler: * >>> >>> 1. aware of ES6 modules? >>> - asking this because I'm not sure how one would consume these in an >>> otherwise Elm-unaware env. >>> 2. able to do code splitting? >>> - The use case here being: I don't want a user to have to >>> download 100 SVG icons in one JS file if there are only 3 being used >>> on a >>> page. >>> 3. able to do hot reloading? >>> - Just curious here >>> 4. ready to start supporting CSS as a 1st class-citizen? >>> - Seems like if Elm is the front-end language of the future, it >>> can't be missing 1/3 of the stack. >>> - I am aware of Richard and others' efforts, and am willing to >>> help <http://kevinsuttle.com/posts/css-modules-a-review>. >>> >>> >>> Let's just leave it at that for now. Curious what the responses will be. >>> Thanks. >>> >>> -- >>> 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] <javascript:>. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> There is NO FATE, we are the creators. >> blog: http://damoc.ro/ >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Zach Kessin > SquareTarget <http://squaretarget.rocks?utm_source=email-sig> > Twitter: @zkessin <https://twitter.com/zkessin> > Skype: zachkessin > -- 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.
