From 43b065ec71fd1de43e5e397b9c639e5564fd6e22 Mon Sep 17 00:00:00 2001 From: milesfrain Date: Wed, 26 Aug 2020 18:28:00 -0700 Subject: [PATCH 1/2] Add note about IDE setup We should point this out to users. Not sure if this the best place for it. Could alternatively do: - Earlier in "Setting up the Development Environment" - Later in "What Next?" --- guides/Getting-Started.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/guides/Getting-Started.md b/guides/Getting-Started.md index c5f6470d..1bab9749 100644 --- a/guides/Getting-Started.md +++ b/guides/Getting-Started.md @@ -163,6 +163,8 @@ When you have finished using PSCi, type `:quit` to quit: Now that we've seen how to use the REPL to reach the answer, let's move our solution into a source file and compile it. +You may find it convenient to [setup an IDE](https://github.com/purescript/documentation/blob/master/ecosystem/Editor-and-tool-support.md) before continuing, but that tooling detour is optional. + Create a new text file `src/Euler.purs` and copy the following code: ```purescript From 6ac2a441e7d8a1f42b29436569f7527e65600170 Mon Sep 17 00:00:00 2001 From: milesfrain Date: Sat, 5 Sep 2020 21:54:38 -0700 Subject: [PATCH 2/2] Move IDE setup to What Next section --- guides/Getting-Started.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/guides/Getting-Started.md b/guides/Getting-Started.md index 1bab9749..534ed5ea 100644 --- a/guides/Getting-Started.md +++ b/guides/Getting-Started.md @@ -163,8 +163,6 @@ When you have finished using PSCi, type `:quit` to quit: Now that we've seen how to use the REPL to reach the answer, let's move our solution into a source file and compile it. -You may find it convenient to [setup an IDE](https://github.com/purescript/documentation/blob/master/ecosystem/Editor-and-tool-support.md) before continuing, but that tooling detour is optional. - Create a new text file `src/Euler.purs` and copy the following code: ```purescript @@ -326,7 +324,7 @@ The generated modules will be placed in the `output` directory by default. Each #### What Next? -If you're new to typed functional programming, your next stop should be [PureScript by Example](https://book.purescript.org/), which will walk you through learning PureScript by solving practical problems. +If you're new to typed functional programming, your next stop should be [PureScript by Example](https://book.purescript.org/), which will walk you through learning PureScript by solving practical problems. You may find it convenient to take a brief detour and [setup an IDE](https://github.com/purescript/documentation/blob/master/ecosystem/Editor-and-tool-support.md) before working through the exercises in the book. If you are already familiar with an ML-family language, like Haskell or Elm, PureScript by Example should still be appropriate as a starting point, but you may alternatively want to start by browsing the [language reference in the documentation repository](https://github.com/purescript/documentation/tree/master/language) instead. The language reference gives a more brief, reference-style description of the language, and is aimed at those who are already somewhat familiar with typed functional programming. There is also a [Differences from Haskell](https://github.com/purescript/documentation/blob/master/language/Differences-from-Haskell.md) page which Haskell programmers will find useful.