@hozn 39320 wrote:
OMG – it’s in Haskell. That’s awesome.
I know about as much about Haskell as I do about heaven, but the last couple lines of this block appear to explain the “flooring” and cast to int:
[COLOR=#990000][B]renderScores[/B][/COLOR] scores [B]=[/B] ol [B]$[/B] [B]do[/B]
mapM_ row [B]$[/B] reverse [B]$[/B] sort scores
[B]where[/B]
row us [B]=[/B] li [B]$[/B] [B]do[/B]
a [B]![/B] href (toValue [B]$[/B] [COLOR=#DD1144]”http://app.strava.com/athletes/”%5B/COLOR%5D [B]++[/B] (show [B]$[/B] uid us)) [B]$[/B] toHtml [B]$[/B] name us
[B]_[/B] [B]<-[/B] [COLOR=#DD1144]": "[/COLOR]
td [B]$[/B] toHtml [B]$[/B] userScore us
[B]_[/B] [B]<-[/B] [COLOR=#DD1144]" points ("[/COLOR]
toHtml (days us)
[B]_[/B] [B]<-[/B] [COLOR=#DD1144]" days, "[/COLOR]
toHtml (floor [B]$[/B] miles us [B]::[/B] [COLOR=#445588][B]Int[/B][/COLOR])
[COLOR=#DD1144]" miles)"[/COLOR]
[/CODE]
That said, that looks like it's just for display, so it's possible the full values are being stored (?) I'm sure rcannon can illuminate.
I too build my work life around open-source software; I love that this is open-source.
It looks like he’s also flooring when calculating the score itself:
[CODE]userScore score = 10 * days score + floor (miles score)[/CODE]
But it also looks like if you were to do two rides in a single day, say 4.9mi and 1.1mi, it would be scored “correctly” as 6mi. If you were to do those same rides on separate days, they would be scored as 4mi and 1mi respectively. I’m not 100% sure about my interpretation of the code, so I’d be interested in hearing from the author.
Ben[CODE]
renderScores scores = ol $ do
mapM_ row $ reverse $ sort scores
where
row us = li $ do
a ! href (toValue $ “http://app.strava.com/athletes/” ++ (show $ uid us)) $ toHtml $ name us
_ <- “: “
td $ toHtml $ userScore us
_ <- ” points (“
toHtml (days us)
_ <- ” days, “
toHtml (floor $ miles us :: Int)
” miles)”
[/CODE]
That said, that looks like it’s just for display, so it’s possible the full values are being stored (?) I’m sure rcannon can illuminate.
I too build my work life around open-source software; I love that this is open-source.
It looks like he’s also flooring when calculating the score itself:
userScore score = 10 * days score + floor (miles score)[/CODE]
But it also looks like if you were to do two rides in a single day, say 4.9mi and 1.1mi, it would be scored “correctly” as 6mi. If you were to do those same rides on separate days, they would be scored as 4mi and 1mi respectively. I’m not 100% sure about my interpretation of the code, so I’d be interested in hearing from the author.
Ben[CODE]userScore score = 10 * days score + floor (miles score)[/CODE]
But it also looks like if you were to do two rides in a single day, say 4.9mi and 1.1mi, it would be scored “correctly” as 6mi. If you were to do those same rides on separate days, they would be scored as 4mi and 1mi respectively. I’m not 100% sure about my interpretation of the code, so I’d be interested in hearing from the author.
Ben
