[elm-discuss] Re: Scaling Elm

[Lourens Rolograaf]

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 the Google Groups "Elm 
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elm-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[elm-discuss] Re: ANN/Request for review: elm-graph

[Lourens Rolograaf]

Hi Sebastian,

After some deep thinking I concluded my world is modelled best in a graph 
datastructure. 
What is in elm-community/graph the way to get the only the siblings of a 
node?
When I use breadth-first traveling with `ignorepath` it gives me far too 
many nodes. 
probably due to "ignoring distance parameters"
It seems I need an example for `BfsNodeVisitor`, any chance for a tutorial 
with some more examples to get me started?

Or are you far gone from this project? it is almost half a year old now

thanks anyway!
Lourens

Op vrijdag 7 augustus 2015 11:56:47 UTC+2 schreef Sebastian Graf:
>
> Hi,
>
> today I'd like to open my developments of a graph library in Elm 
>  to a broader public. 
> It's not quite there yet, but most of the stuff for a 1.0 is in there 
> except for BFS (which won't take that long).
> I would really appreciate some short code review and help with what is 
> seemingly a bug in elm-make (or myself):
>
> Trying to compile the Graph module with elm-make results in module 
> documentation errors for every single export ('The module exports `export` 
> but it is not in the module documentation'), except that I really have 
> supplied documentation.
> I don't know what this is about, documentation generation worked for some 
> other packages I published earlier.
>
> So, some questions regarding code organization:
>
>1. Should I leave the Foci in the main module? Should I even supply 
>them in an extra library?
>2. I feel a little partial wrt. having most of the code in one module, 
>but love the name spacing that way. Should I split up e.g. traversals into 
>their own module anyway? That might help with the elm-make bug.
>
> I really enjoyed the neatness of Elm, although somewhat verbose. Every 
> library I released gives me a warm cozy gut feeling :)
>
> Thanks for your time! 
>

-- 
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 elm-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [elm-discuss] Re: The Style Elements Library: a different approach to styling

[Lourens Rolograaf]

Hi Matt,

For using a div as if it were a button, I would like to make the 
caption-text un-selectable when there is any mousemovement during click. 
This could be done with vendor-prefixed `user-select: none` according 
https://stackoverflow.com/questions/826782/how-to-disable-text-selection-highlighting-using-css
Any chance of this feature in Style-elements-lib?

Thx
Lawrence

Op maandag 31 oktober 2016 16:04:24 UTC+1 schreef Matthew Griffith:
>
> Yeah, this library is more about smart styling in elm rather than 
> interfacing with polymer.  Since we can do mixins in elm, native mixins 
> probably won't be supported :/
>
> I have thought that you could make a polymer or mdl type library in pure 
> elm using the style-elements library, though it would just cover the 
> styling/animation portion, not full behavior type stuff.
>
> You've probably seen the thread discussing elm and polymer, the result of 
> that discussion might fit your needs more closely once they finish.
>
>
>
>
>
> On Monday, October 31, 2016 at 9:40:37 AM UTC-4, Ed Ilyin wrote:
>>
>> yeah, but to use polymer elements, native css mixins are required :(
>>
>> Il giorno lun 31 ott 2016 alle ore 14:51 Matthew Griffith <
>> mdg.gr...@gmail.com> ha scritto:
>>
>>> No, it won't render as a native css mixin, it just gives you the 
>>> functionality of a mixin in your elm code.
>>>
>>>
>>>
>>> On Monday, October 31, 2016 at 7:55:38 AM UTC-4, Ed Ilyin wrote:
>>>
 Will it render native CSS mixin?

 Actually I can't figure out how to create native CSS mixins even using 
 elm-css module.

 Il giorno lun 31 ott 2016 alle ore 13:49 Matthew Griffith <
 mdg.gr...@gmail.com> ha scritto:

> You can create a mixin as a function.
>
>
>
> myMixin : Style.Model -> Style.Model
> myMixin style =
> { style
> | visibility = hidden
> }
>
> myMixinColor : Style.Model -> Style.Model
> myMixinColor style =
> { style
> | colors = palette.blue
> }
>
>
> dropDown : List (Html.Attribute a) -> List (Element a) -> Element a
> dropDown =
> element
> ({ base
> | width = px 300
> , padding = all 20
> , spacing = topBottom 40
>  }
> |> myMixin
> |> myMixinColor
> )
>
>
>
>
>
>
>
>
>
>
> On Monday, October 31, 2016 at 5:16:43 AM UTC-4, Ed Ilyin wrote:
>
>> I'm actively using Polymer Paper Elements. And they accept mixings 
>> like this:
>> ```css
>>   paper-dropdown-menu {
>> --paper-input-container-input: {
>>   color: white;
>> }
>> --paper-input-container-underline: {
>>   display: none;
>> }
>> --paper-dropdown-menu-icon: {
>>   color: white;
>> }
>> --paper-input-container-focus-color: white;
>>   }
>> ```
>> how to do the same using style-elements library?
>>
>> Il giorno ven 28 ott 2016 alle ore 19:34 Matthew Griffith <
>> mdg.gr...@gmail.com> ha scritto:
>>
> So, taking a look at it, direct support for keyed will be super easy 
>>> and will absolutely show up in v1.1.0.
>>>
>>> And I believe I have a way to directly support lazy as well, though 
>>> I want to try it out before confirming completely.
>>>
>>>
>>>
>>>
>>> On Friday, October 28, 2016 at 12:28:17 PM UTC-4, Mark Hamburg wrote:
>>>
 On Oct 28, 2016, at 7:28 AM, Matthew Griffith  
 wrote:

 2.  You can use Keyed and Lazy on a parent element (the one created 
 by *Style.Elements.build*).  You could use *Style.Elements.build* in 
 a child view and then use *Style.Elements.html *to integrate it 
 into the main view, using keyed or lazy in the process.   That feels a 
 bit 
 roundabout and I believe there could be a better way.  I'll just have 
 to 
 give it some thought as to how it'd work :).   


 Keyed as it turns out is central to getting stateful DOM elements 
 to behave reliably.

 But I'm looking forward to trying this library out.

 Mark

 -- 
>>> 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 elm-discuss...@googlegroups.com.
>>
>>
>>> 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 

[elm-discuss] Re: Feature: 'where' expressions (continued from GitHub)

[Lourens Rolograaf]

Please no. Not every Haskell feature should have a place in elm, especially 
if there is already a construct that works (and overlaps 100%?) 
Please do not make elm2016, elm2017 or coffeeElm, with all kinds of 
syntactic sugar because some user from another language still thinks this 
way.

Op vrijdag 30 december 2016 18:10:52 UTC+1 schreef Will White:
>
> Continued from https://github.com/elm-lang/elm-compiler/issues/621.
>

-- 
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 elm-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.