Feed Aggregator Page 655
Rendered on Mon, 05 Oct 2020 23:03:22 GMT
Rendered on Mon, 05 Oct 2020 23:03:22 GMT
via Elm - Latest posts by @eiro Marc Chantreux on Mon, 05 Oct 2020 16:10:43 GMT
i just had to seat there and read the thread! still not in my terminal
but zeal is much closer than what i expected and there are other docs i
can download that way.
thanks to both of you.
regards
marc
via Elm - Latest posts by @MarkHamburg Mark Hamburg on Mon, 05 Oct 2020 15:17:52 GMT
More use of let definitions is probably a better thing much of the time. How well it works, however, depends on how well one names the local definitions. That, of course, then touches on one of the two hard problems in computer programming: cache invalidation, naming things, and off-by-one errors.
Mark
via Elm - Latest posts by @kraklin Tomáš Látal on Mon, 05 Oct 2020 14:16:16 GMT
Cool, enjoy your offline docs then
via Elm - Latest posts by @malaire Markus Laire on Mon, 05 Oct 2020 14:09:06 GMT
The “Feed URL (.xml)” there worked:
EDIT: The URL must be “Feed URL (.xml)” and not “Feed URL”. Both will add the docset, but without .xml
in URL it will be saved as .docset
instead of Elm.docset
.
via Elm - Latest posts by @jfmengels Jeroen Engels on Mon, 05 Oct 2020 14:05:11 GMT
Episode 014: The Life of a File is out! We revisit Evan’s classic talk and dive into the process for how and when to split out Elm code into modules.
via Elm - Latest posts by @kraklin Tomáš Látal on Mon, 05 Oct 2020 13:53:46 GMT
Or even better, I have found this app with the link to the XML feed:
via Elm - Latest posts by @kraklin Tomáš Látal on Mon, 05 Oct 2020 13:52:16 GMT
So the address you are looking for is probably this one:
http://newyork.kapeli.com/feeds/zzz/user_contributed/build/Elm/Elm.tgz
via Elm - Latest posts by @kraklin Tomáš Látal on Mon, 05 Oct 2020 13:50:07 GMT
OK, this should help:
via Elm - Latest posts by @malaire Markus Laire on Mon, 05 Oct 2020 13:47:44 GMT
There is only one place in Zeal for downloading docsets and Elm is not listed there. “User Contributed” docsets is not mentioned anywhere.
via Elm - Latest posts by @kraklin Tomáš Látal on Mon, 05 Oct 2020 13:45:48 GMT
I don’t use Zeal, so I can’t tell you that for sure - but you should be able to do it like this:
You can do this using Edit > Options > Docsets > Download.
It is a User Contributed docset, so maybe it will be somewhere deeper than on the main page, hard to tell. Let me know if you have found it and how, please.
via Elm - Latest posts by @malaire Markus Laire on Mon, 05 Oct 2020 13:30:44 GMT
Where can I download the Elm docset for Zeal?
via Elm - Latest posts by @valery111 Valery Prince on Mon, 05 Oct 2020 07:13:15 GMT
Now it is difficult and practically impossible to imagine our life without a gadget. No iPhone. For many, it will not be a secret that updates are released every few months. And new models are released once a year.
But few people know that they are being developed in conjunction with the company’s platforms https://aduk.de/services/smart-connectivity/… A company that develops hardware and software. And few people guess what kind of mechanism is behind all this.
Thank you for attention.
via Elm - Latest posts by @DullBananas on Mon, 05 Oct 2020 06:10:00 GMT
don’t get me wrong, i love rust too. but not javascript
via Elm - Latest posts by @system system on Sun, 04 Oct 2020 19:21:45 GMT
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
via Elm - Latest posts by @NicolasGuilloux Guilloux Nicolas on Sun, 04 Oct 2020 17:56:38 GMT
Thank you for the extension! It works really well!
via Elm - Latest posts by @lydell Simon Lydell on Sun, 04 Oct 2020 17:39:18 GMT
@rupert Off topic question – do you miss |.
and |=
in your parsing example? Since you can’t define your own operators I see you use |> PR.ignore
and |> PR.keep
instead. (See Chat about elm/parser operators |. and |= for my previous topic about this.)
via Elm - Latest posts by @kraklin Tomáš Látal on Sun, 04 Oct 2020 17:32:57 GMT
Or you can use Dash or Zeal and download Elm docset. I’m trying to keep it updated on the newest version on monthly basis.
If you would like to dig deeper, you can take a look at the python script I’m using to generate the docset and bend it to your needs
via Elm - Latest posts by @kraklin Tomáš Látal on Sun, 04 Oct 2020 16:42:12 GMT
Elm Debug Helper is finally out
Browser extension that is helping you with making Debug.log messages more readable by parsing them and transforming them into JS object which is collapsible.
The extension comes in two flavours, both are downloadable from official extension stores
Source code is available in GitHub repository.
Big thanks for all beta-testers, you are my personal heroes
via Elm - Latest posts by @evelios Tommy Waters on Sun, 04 Oct 2020 14:16:20 GMT
Thank you for expanding on this for me. You bring up a lot of good points that I have struggled with as well.
All of these assumptions, unfortunately, break down very quickly
This was something that was at the heart of the issue as you brought up. I think for me, the path I was going to go down was to make simple tools that made these kinds of egregious assumptions and hold each tool in a rigid compositional box.
- A melody uses only one scale
- A melody uses only pitches contained in the scale
- Each pitch in a scale is an equally viable possibility
- A variation should maintain the same scale steps, in the same directions, as in the original
Make all of these assumptions explicit from the outset so that the user of the tool understands the limitations and scope of when this tool would be useful.
I have been thinking of these in terms of my own musical compositional understanding. For example,
when starting to write a composition, I follow these explicit rules.
Then create a tool that follows these rules.
Then as my understanding grows, I would create a tool that would have less assumptions, and less rules. However, every tool by nature of automation is always working within a box of pre-defined assumptions.
This would allow me to ignore the problems of each assumption initially to create a framework that works well in some contexts. Also, making all of these assumptions bold and clear to the user so that they knew that they were being creatively limited in some context. As long as they are aware of the limitations, they then had the ability to choose a different tool, or use it as a framework to then manipulate and create their true work. This is where the true works are, when people work within a framework, but then know what assumptions they are working with so that they can then break those rules to accomplish their true goals.
I think by nature of music, no tool will cover all contexts, nor should they.
There is also one more big problem lurking in the background. I know you are focused on western music and notation which does help limit this problem a lot. However, different genres and cultures have different means of understanding harmony. It seems like your training is heavily into the jazz culture of harmonic ideas which then brings with it it’s own framework for understanding these relationships of diatonic and chromatic harmonies. I don’t think that there will ever be the one model to rule them all to model.
I do think you already have a strong understanding of what the limitations are for each are which gives a good basis for the context in which each tool is most applicable to the particular composer which is using it.
Every time you remove one of those assumptions, the model complexity explodes. This also breaks each large assumption into many smaller assumptions, each with their own baggage.
via Elm - Latest posts by @opvasger Asger Nielsen on Sun, 04 Oct 2020 10:49:14 GMT
I won’t be very helpful in providing occasional support the way you need - I misunderstood. But I bet someone else on here can help out!