On Wednesday, 4 January 2017 21:05:58 UTC+7, Bob Zhang wrote:
>
> Hi Gordon,
> As you can see, BuckleScript already did a very good good job here, of
> course, there are still places for improvement. To write extremely high
> performance code, you should avoid creating a closure in a tight
Dnia 2017-01-02, o godz. 17:50:41
Evan Czaplicki napisał(a):
> I recently talked with folks who moderate the various Elm discussion forums
> about the challenges that come up and how we can do better.
>
> The short version is: *we should start migrating more discussion to
On Wednesday, January 4, 2017 at 11:24:31 PM UTC, Noah Hall wrote:
>
> It does support custom and supports markdown as a special case -
>
> https://github.com/eeue56/elm-server-side-renderer/blob/master/src/ServerSide/Markdown.elm
>
> However, it doesn't convert it to html on the server side.
It does support custom and supports markdown as a special case -
https://github.com/eeue56/elm-server-side-renderer/blob/master/src/ServerSide/Markdown.elm
However, it doesn't convert it to html on the server side. That should be
trivial to add - just a called to marked, but I haven't needed it
On Wednesday, January 4, 2017 at 11:01:44 PM UTC, Rupert Smith wrote:
>
> When server side rendering Html I am trying to figure out why markdown
> processing is not working right.
>
I just get the unprocessed markdown appearing in the page. Perhaps:
On Wednesday, January 4, 2017 at 11:01:44 PM UTC, Rupert Smith wrote:
>
> I guess this invokes the https://github.com/chjj/marked javascript
> markdown processor somehow from the details in the "custom" Html model.
> Does that mean that marked needs to be included as a javascript library on
>
When server side rendering Html I am trying to figure out why markdown
processing is not working right. It fails to wrap a line of text in a
aragraph. So I tried this program:
import Html exposing (text)
import Markdown
main =
let
d = Debug.log "test" (Markdown.toHtml [] "test")
d1 =
As pointed out earlier, it is not true for *Haskell's* let and where.
> Am 04.01.2017 um 22:52 schrieb 'Andrew Radford' via Elm Discuss
> :
>
> Heh ok read it again I'll make it more programmer friendly:
>
> ( |> and <| ) and ( >> and << )
>
>
> They (each)
Heh ok read it again I'll make it more programmer friendly:
( |> and <| ) and ( >> and << )
They (each) have identical behavior in what they do, with a left/right
symmetry. (I guess you just confirmed it is the same for let/where, with a
top/bottom symmetry)
On Wednesday, 4 January 2017
>
> Kinda like how you currently have the freedom to chose between |> and <|,
> >> and <<
They're not really the same thing: << is function composition, and <| is
function application. There are cases where you can use either, but for
each there are cases where only one will do the trick.
Colin,
Thanks for this comprehensive post - very well thought out and reasonably
considered
TIL about 'where' - wow so much awesome stuff is in Haskell. Let...in now
seems to be upside down! 'Where' seems to closer suit describing *ideas* like
you would in Plain English:
Kinetic Energy is:
Martin are there any pros/cons to using extensible records for the game
entities? i.e closer conceptually to an OOP model where an entity might
inherit Collision/Physics properties from a common base class?
Andrew
>>
--
You received this message because you are subscribed to the Google
I can't speak to Evan's original intent in posting, but that's what I'd like to
see people do.
> On Jan 4, 2017, at 2:11 PM, Mark Hamburg wrote:
>
> So, this is really about "please go look at /r/elm too"?
>
> Mark
>
>> On Jan 4, 2017, at 11:08 AM,
So, this is really about "please go look at /r/elm too"?
Mark
> On Jan 4, 2017, at 11:08 AM, br...@brianthicks.com wrote:
>
> Killing elm-discuss is outside the scope of the discussion. The point is to
> emphasize an underused watering hole, not kill an existing one that works
> well for a
At least going through the mental exercise of "would you move elm-dev to
reddit" is a way to avoid the frequently fallacious mental trap of "I wouldn't
do this, but others should". In fact, for any move to any other system, it
might actually be a good thing for elm-dev to lead the way. That
Killing elm-discuss is outside the scope of the discussion. The point is to
emphasize an underused watering hole, not kill an existing one that works well
for a subset of the community.
> On Jan 4, 2017, at 2:00 PM, Martin DeMello wrote:
>
> I would argue very
I would argue very strongly against killing elm-discuss. I'm a heavy reddit
user, and I think it simply lacks the features necessary to support
mailing-list-style discussions:
1. if you subscribe to a lot of subreddits, there is no guarantee you'll be
shown new posts from /r/elm in your front
Part of my issue here is that the documentation for the Dom module makes no
promises about execution order and hence should presumably be viewed as free to
change in the future. That said, when I go look at the source, I see that it
ties execution to requestAnimationFrame which seems good but
I don't have a port. I'm just using the standard Dom package. But it would
presumably have similar issues with attempts to interact with elements that
aren't there yet.
Mark
> On Jan 4, 2017, at 9:30 AM, Sebastian Seilund wrote:
>
> Hi Mark. Try to send a message on your
I agree that this only works if elm-discuss gets killed. It might, however, be
necessary to also kill elm-dev because the leakage of elm-discuss traffic over
into elm-dev will likely become much worse if elm-discuss goes away.
Mark
> On Jan 4, 2017, at 9:34 AM, Rex van der Spuy
I'm well aware that the Elm subreddit can and will be moderated. The view point
I was hearing and relaying was basically a political statement about choosing
not to support Reddit.
Mark
> On Jan 4, 2017, at 8:38 AM, Charlie Koster wrote:
>
> Mark, Reddit is what you make
I, in my ungrammatical bubble, should perhaps use some Elm-based software to
keep me from becoming too casual in my writing. :-P
> On Jan 4, 2017, at 8:32 AM, Mark Hamburg wrote:
>
> Me, in my white male tech bubble, focused on user interface annoyances in
> Reddit. I
On Wednesday, January 4, 2017 at 12:05:33 PM UTC-5, Brian Hicks wrote:
>
> the fact remains that /r/elm is going to be a place that people go to ask
> questions, and if nobody is there to answer them we're giving people a
> really bad experience.
>
>
That was my problem: When I started
Hi Mark. Try to send a message on your port as a command in your `init`
function. In the port JS handler you run `requestAnimationFrame` and find
and focus your element there. Does that work?
On Wednesday, January 4, 2017 at 8:24:40 AM UTC-8, Mark Hamburg wrote:
>
> We just had a similar
Thanks, Richard.
I'm pretty sure I had tried that earlier, and the element wasn't there yet.
I had to nest two `requestAnimationFrame` calls within each other, or a mix
of `rAF` and `setTimeout` with 1 or 0 as delay. And I would see a short
flicker on the screen before my scroll code executed.
I understand the principle of wanting to avoid Twitter and Reddit. I feel
pretty conflicted about those two services myself. But the fact remains
that /r/elm is going to be a place that people go to ask questions, and if
nobody is there to answer them we're giving people a really bad
Mark, Reddit is what you make of it. Subreddits (such as /r/elm) are
self-moderated and it's easy enough to unsubscribe from the bad ones. I
think you can be rest assured that /r/elm will be devoid of hate speech.
Me, in my white male tech bubble, focused on user interface annoyances in
Reddit. I asked around with some other developers I work with and have worked
with and Reddit (along with Twitter) was viewed as a place that has been too
friendly to hate speech — particularly racist and misogynist hate
We just had a similar concern come up but with the existing Dom package. If the
init for a model wants to generate a focus command — the autofocus property is
proving unreliable for reasons as yet undetermined — how can we arrange to have
that command execute after the view has actually been
On Wednesday, January 4, 2017 at 12:27:11 PM UTC, John Orford wrote:
>
> That struck me as well - I am going to switch my name to the real one, if
> I can on Reddit...
>
Or create a new account so you can keep the nickname to use when you are
trolling us... :-P
--
You received this message
Hi Gordon,
As you can see, BuckleScript already did a very good good job here, of
course, there are still places for improvement. To write extremely high
performance code, you should avoid creating a closure in a tight loop, here
you can lift the `nxtc` into the toplevel, in the future, we will
That struck me as well - I am going to switch my name to the real one, if I
can on Reddit...
On Wed, 4 Jan 2017 at 12:54 'Rupert Smith' via Elm Discuss <
elm-discuss@googlegroups.com> wrote:
> On Wednesday, January 4, 2017 at 6:51:28 AM UTC, Richard Feldman wrote:
>
> I don't think that makes
On Wednesday, January 4, 2017 at 6:51:28 AM UTC, Richard Feldman wrote:
>
> I don't think that makes /r/elm the automatic best choice, but I do think
>> it makes it worth a shot.
>>
>
I like how on google groups everyone tends to use their real name. On
reddit most people post with nicknames. It
Somewhat late, but there is a nice exposition on this by Evan over here:
https://github.com/elm-lang/elm-compiler/blob/master/hints/recursive-alias.md
--
You received this message because you are subscribed to the Google Groups "Elm
Discuss" group.
To unsubscribe from this group and stop
34 matches
Mail list logo