Re: [elm-discuss] Sublime Text 3 highlighting in 0.17

[Noah Hall]

The maintainer for the plugin is sadly unresponsive. There's been a
couple of offers to take it over, and it's been forked to
elm-community, but apparently the process to get it updated upstream
with sublime package control is complex. I'm not sure.

for now, you can add a `--where` as a comment after the `exposing`
bit, like this: `module Something exposing (..) -- where`. Hacky but
works until this is resolved

On Mon, May 23, 2016 at 7:23 PM, kgashok  wrote:
> Specifically after the changeover fro m
> module XXX where
> to
> module XXX exposing (..)
>
> the highlighting in Sublime Text 3 is all screwed up. How do I
> update/upgrade the Elm support settings in Sublime Text 3?
>
> --
> 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.

-- 
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] Documentation for packages removed from Core is too hard to find

[Joey Eremondi]

Perhaps there could be an option for a "landing page" or multi-version
README, so the documentation for the old versions can point to the new
versions? Like, a PackageInfo.md in master on GitHub?

Or maybe, when a library is deprecated, it should be good practice to
release a "dummy" version with all contents removed, an unsatisfiable
version constraint, and a README pointing to the new library?

In any case, we can't control how Google presents our documentation, so
there will probably need to be some kind of workaround.

On Mon, May 23, 2016 at 10:09 AM, Noah Hall  wrote:

> (not saying it can't be improved - but this is where the info for
> core/evan's packages live)
>
> On Mon, May 23, 2016 at 7:09 PM, Noah Hall  wrote:
> >
> https://github.com/elm-lang/elm-platform/blob/master/upgrade-docs/0.17.md#update-elm-packagejson
> >
> > On Mon, May 23, 2016 at 7:06 PM, Alexander Biggs
> >  wrote:
> >> If I google "elm keyboard" today, here is the series of steps I follow
> >> before figuring out how to do keyboard input in my Elm game:
> >>
> >> 1. Click on first result, "Keyboard - core 2.1.0" packages page
> >> 2. Click on "go to latest version"
> >> 3. Get redirected to a 404 page
> >> 4. Scratch my head for a bit before realizing that the package was
> moved out
> >> of Core in Elm 4
> >> 5. Click on "elm-lang" at the top navigation to go to the frontpage for
> elm
> >> documentation
> >> 6. I lied, it actually brings me to the elm-lang github
> organization(?!?).
> >> Search for "keyboard" there
> >> 7. It brings me to a github repo for Keyboard, whose README has no info
> on
> >> how to install the package or what types are exposed, just a general
> >> overview of what the package is
> >> 8. Go back to the elm package website, click on the "Elm Packages" icon
> on
> >> the topleft to go to the documentation homepage
> >> 9. Search for "keyboard", click on first result.
> >>
> >> The page this shows me still has no documentation on how to install the
> >> package, for that I have to click back and go to "Using Packages" from
> the
> >> package homepage. However, finally I can find the documentation for what
> >> types are available in the Keyboard package by clicking on "Keyboard"
> on the
> >> right side of the page.
> >>
> >> This process can be improved a lot:
> >>
> >> 1. The "go to latest version" for packages removed from core should
> redirect
> >> to the new page for that package
> >> 2. Pages for packages that are not in Core should have a link to the
> >> installation instructions
> >> 3. The "elm-lang" link at the top of the packages navigation should go
> to
> >> the documentation frontpage, to avoid breaking the idea of a navigation
> >> tree.
> >>
> >> Any thoughts on other ways we can improve the process for getting
> started
> >> with elm packages?
> >>
> >> --
> >> 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.
>
> --
> 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.
>

-- 
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] Documentation for packages removed from Core is too hard to find

[Noah Hall]

https://github.com/elm-lang/elm-platform/blob/master/upgrade-docs/0.17.md#update-elm-packagejson

On Mon, May 23, 2016 at 7:06 PM, Alexander Biggs
 wrote:
> If I google "elm keyboard" today, here is the series of steps I follow
> before figuring out how to do keyboard input in my Elm game:
>
> 1. Click on first result, "Keyboard - core 2.1.0" packages page
> 2. Click on "go to latest version"
> 3. Get redirected to a 404 page
> 4. Scratch my head for a bit before realizing that the package was moved out
> of Core in Elm 4
> 5. Click on "elm-lang" at the top navigation to go to the frontpage for elm
> documentation
> 6. I lied, it actually brings me to the elm-lang github organization(?!?).
> Search for "keyboard" there
> 7. It brings me to a github repo for Keyboard, whose README has no info on
> how to install the package or what types are exposed, just a general
> overview of what the package is
> 8. Go back to the elm package website, click on the "Elm Packages" icon on
> the topleft to go to the documentation homepage
> 9. Search for "keyboard", click on first result.
>
> The page this shows me still has no documentation on how to install the
> package, for that I have to click back and go to "Using Packages" from the
> package homepage. However, finally I can find the documentation for what
> types are available in the Keyboard package by clicking on "Keyboard" on the
> right side of the page.
>
> This process can be improved a lot:
>
> 1. The "go to latest version" for packages removed from core should redirect
> to the new page for that package
> 2. Pages for packages that are not in Core should have a link to the
> installation instructions
> 3. The "elm-lang" link at the top of the packages navigation should go to
> the documentation frontpage, to avoid breaking the idea of a navigation
> tree.
>
> Any thoughts on other ways we can improve the process for getting started
> with elm packages?
>
> --
> 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.

-- 
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] WebSocket and Phoenix Channels

[Magnus Rundberget]

I know I sound like a party pooper, but I thought/hoped that packages in 
Elm was about providing one really good lib/package for a particular 
concern (at least as a general rule). 
Maybe you could help each other out and make the "awesomest ever" phoenix 
package for Elm.

A quick peak on reddit and I find this too: 
https://www.reddit.com/r/elm/comments/4kkjly/elmphoenixsocket_a_pure_elm_implementation_of_the/

I think it's super that folks are enthusiastic about providing Phoenix 
integration support in Elm. So if people still go ahead and do their own 
thing (which of course they are entitled too), it would be great as a 
end-user/consumer to get a rationale about why their package was created 
and how it differs/improves on what's already there.  


cheers
-magnus






On Monday, 23 May 2016 11:05:26 UTC+2, Simon wrote:
>
> Actually no, and it looks like Noah has put more effort into the helpers, 
> and faced the same complexity in actually extracting messages incoming
> On 23 May 2016 12:14 a.m., "Magnus Rundberget"  > wrote:
>
>> Did you notice this before you set out on your quest ?
>> http://package.elm-lang.org/packages/NoRedInk/elm-phoenix/1.0.0/
>>
>> Cheers
>> -magnus
>>
>> --
>> 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/n06mRcIiesI/unsubscribe.
>> To unsubscribe from this group and all its topics, 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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[elm-discuss] Re: Looking for people experienced with elm-html's "key" function

[gera]

I'm not sure if the lazyDict approach applies, but I'm hitting a much 
simpler (IMO) issue that I've reported 
at https://github.com/elm-lang/html/issues/21.

I'm honestly surprised that no one has run into it yet, specially since the 
documentation for `key` in 0.16 specifically provides this exact issue as 
the reason for its existence.

It's entirely possible and highly likely that I'm missing something basic. 
I would be glad to receive any pointers, but I would also argue that the 
documentation could be improved in that case.

Cheers,
--gera.

On Monday, February 29, 2016 at 7:38:56 PM UTC+1, Evan wrote:
>
> You use Html.Attribute.key 
> 
>  
> when you have a sequence of items where you may be inserting and removing 
> from the middle. I took this API pretty much directly from the virtual-dom 
> implementation that backs the currently released version of elm-html. I am 
> doing a rewrite for various reasons, and realized that the current API 
> clashes with the laziness optimizations.
>
>
> Problem
>
> If you have a big list, you’d likely want to make each entry lazy. It 
> would suck to have to build 1000 virtual nodes. If you want keys, you need 
> to add them as an attribute, but lazy takes no attributes! This means you 
> need to add an extra DOM node with a key where it has one child that’s lazy.
>
>
> Alternative
>
> I am considering getting rid of Html.Attribute.key entirely and replacing 
> it with this function:
>
> lazyDict
>   : String
>   -> List Attribute
>   -> (a -> Html)
>   -> Dict comparable a
>   -> Html
> lazyDict tagName attributes viewItem items = ...
>
> It is somewhat similar to the normal Html.node 
>  
> function in that it is just about creating virtual DOM nodes, but in this 
> case you give a Dict instead of a List. You might create a news feed like 
> this:
>
> viewNewsFeed : Dict Time Story -> Html
> viewNewsFeed stories =
>   lazyDict "div" [class "news-feed"] viewStory stories
>
> Each entry would also be done lazily, so you only need to create the Html 
> if the dictionary entries are not reference equal.
>
> This means it would be easy to treat the stories as a dictionary in your 
> model. When you want to add something, you add it with a timestamp. If it's 
> sorted by name, you have a (Dict String Person) or whatever.
>
>
> Question
>
> If you have personally used keys for a specific scenario, would this new 
> API cover things as well? Would it be better or worse? Can you elaborate on 
> the details of your case?
>
> *Note:* I am looking for *specific* experience. *If you don't have a 
> concrete example, you are off-topic.* Take it to another thread. If you 
> are reading this and the thread is long, feel free just to respond to my 
> initial question. The goal here is to gather data, not opinions.
>

-- 
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] WebSocket and Phoenix Channels

[Hot Belgo]

Actually no, and it looks like Noah has put more effort into the helpers,
and faced the same complexity in actually extracting messages incoming
On 23 May 2016 12:14 a.m., "Magnus Rundberget"  wrote:

> Did you notice this before you set out on your quest ?
> http://package.elm-lang.org/packages/NoRedInk/elm-phoenix/1.0.0/
>
> Cheers
> -magnus
>
> --
> 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/n06mRcIiesI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> elm-discuss+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [elm-discuss] Will ELM become a general purpose language?

[Peter Damoc]

Julian,

I also have a Python background :)

Elm will not replace Python anytime soon as a *general* purpose language.
Python has way more libraries and documentation, plus some problems are
just easier to solve with an imperative approach.
That being said, Elm needs not replace Python.
I see myself still doing small, utility scripts in python and serious work
in Elm for years to come.
Elm has a very solid design so, after it reaches 1.0 I see it start to eat
a lot from the jobs of other languages.
It will get alternative backends and this might open the door for even more
applications.

As for Haskell, Erlang, Elixir... Elm was designed to be friendlier than
either of those.
So, it makes no sense to learn Haskell first if you want to work in Elm and
it makes a lot of sense to learn Elm first if you want to end up using
Haskell.




On Mon, May 23, 2016 at 3:58 AM, julian ebeli 
wrote:

> Hi All
> I've just discovered ELM as part of a general interest in Functional
> Programming.
> I'm a Python programmer and have just recently started to do Python
> Functionally, I'm a slow learner!
> Will ELM ever be something I can replace Python with?
> I realize its early days but is it part of the plan for this language or
> will it be the best way to do SPAs
>
> Also should I be learning Haskell, Erlang, Elixir or other if I want to
> develop my general purpose Functional Programming skills and stay on an ELM
> pathway?
>
> 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 elm-discuss+unsubscr...@googlegroups.com.
> 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 elm-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.