Keep the examples and keep the theme consistent with purescript.org, but maybe draw inspiration from the go playground. As you can see most of the space is taken up by the code editor, some by the output window, and a small space at the top for related functions.

I think the examples could be a dropdown in the top bar. Perhaps we could even have a "play.purescript.org" which offers the same functionality of running code and sharing snippets.

As discussed in #57 the plan is to get rid of initial snippets. It would be good if the maintainers of the backends would create an initial gist (so that they have ownership of it) & include it here.

After we have all the gists we can get rid of the initial snippets.

@soupi already provided gist for purescript-slides: c62b5778a6a5f2bcd32dd97b294c068a.

The flare backend appears to be on version 3.0.0.

The bower says it's using 3.2.0:

I'm not sure what to do to fix it or I would have sent a PR.

The typeclasses example (http://try.purescript.org/example/typeclasses) generates JS that begins with

var PS = PS || {};
PS.Prelude = (function () {
    "use strict";
    return {
        "++": $plus$plus
    };
})();
var PS = PS || {};
PS.Main = (function () {
    "use strict";
    ...

which will throw a ReferenceError for $plus$plus. This code isn't even used, since Semigroup ++ on strings is compiled straight to JavaScript +.

Ace probably provides an API for this, we just need to expose it on the server.

• List my PureScript Gists (https://developer.github.com/v3/gists/#list-a-users-gists)
  • load into editor
  • get gist id
• Save Gist
  • as new (https://developer.github.com/v3/gists/#create-a-gist)
  • as update to loaded gist (https://developer.github.com/v3/gists/#edit-a-gist)

We should provide attribution for the libraries we depend on in the Help page.

Now that we have tooltips, we could use icons like the ones from FontAwesome to render the buttons in the toolbar.

@sharkdp The process for adding libraries has become much easier since last time we hosted Try Flare. We can also serve the client code from this repo too, like we do with Thermite and purescript-slides if you like. Would you be interested?

cc @garyb too, since we could potentially put together a "Try Halogen" too now.

See #39 for an example of adding a new library.

When browsing examples with Firefox the user has to click Back two/three times very quickly to go to the previous page.
In Chrome this works fine with one Back.

Tested with Firefox 52.0a2 (2017-01-24) (64 bit) and Chrome 56.0.2924.76 (64-bit)

purescript-validation package is available in the core engine.

Can we also add that to thermite engine?

I'm working on a mathbox backend for trypurescript (got a first version working locally). Is there interest (and server resources) to add it to http://try.purescript.org/ ?

It could be nice to have error annotations in the editor in addition to the error messages we have right now when compiling.

The API now returns suggestions for warnings. It would be nice to let the user apply them.

psc-ide supports this, so maybe we can reuse it.

cc @kritzcreek

It would be nice if you could scroll past the end in the text editor so that you don't have to bend your neck down when editing the last few lines in a large file. ST3, Vim, Emacs and Visual Studio have similar behavior.

Example:

Description

1. Visit http://try.purescript.org
2. Select Backend->Slides

Console:

POST https://compile.purescript.org/slides/compile 502 (Bad Gateway)
Failed to load https://compile.purescript.org/slides/compile: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:8080' is therefore not allowed access. The response had HTTP status code 502.

After some discussion with Phil about how we could improve documentation for PureScript libraries, we arrived at a design where we would like to have GitHub Pages-hosted documents easily embed runnable PureScript snippets, with something like script or pre tags, and a plugin that adds a "Run" button, posts the code to the Try PS API when the user clicks, and finally renders the output (below the snippet).

I have not had time to look into how this code is doing stuff right now, just throwing this out there. 😄

Thx!

Hey, thanks for this first of all!

I am having some problems getting to the point where I can run the example command you provided.

$ cabal --version gives me

cabal-install version 1.22.9.0
using version 1.22.8.0 of the Cabal library

I had to install the following packages

$ cabal install glob aeson http-types purescript scotty

Then I've run

$ cabal install
# takes quite some time, then I clearly see it doing
Downloading purescript-0.10.5...
Configuring purescript-0.10.5...
Building purescript-0.10.5...
# some more output

When I execute $ cabal run I get

Preprocessing executable 'trypurescript' for trypurescript-0.10.5...
Linking dist/build/trypurescript/trypurescript ...
Running trypurescript...
trypurescript: user error (Pattern match failure in do expression at server/Main.hs:164:3-27)

I know next to nothing about Haskell or PureScript, any help would be greatly appreciated!

UPDATE

I figured out I don't need to run cabal run, I just have to run the command from dist/, nevermind, are you willing to take a PR with some detailed instructions on how to use this from a newbie point of view?

cc @sharkdp

Just a thought. It would let us generate a client and documentation.

The current package-set used by TryPurescript is psc-0.11.6, if I'm reading correctly. That package-set doesn't have include "records", but it is in master, so we'll have to wait until that package-set gets a new tag, then we can send a PR here to update the package-set and add record.

When attempting to share, I receive an alert with the message:

From try.purescript.org
Failed to create gist

This is caused by a failed POST:

Request URL: https://api.github.com/gists
Request Method: POST
Status Code: 422 Unprocessable Entity

The response payload:

{
  "message": "Validation Failed",
  "errors": [
    {
      "resource": "Gist",
      "code": "missing_field",
      "field": "user"
    },
    {
      "resource": "Gist",
      "code": "missing_field",
      "field": "files"
    }
  ],
  "documentation_url": "https://developer.github.com/v3/gists/#create-a-gist"
}

submitted at purescript/purescript-console#11

psc-ide supports this, so maybe we can reuse it.

cc @kritzcreek

Possibly toggled. Inspired by CodePen.

maybe with tabs

It would be nice to be able to import Graphics.Drawing (..) and have a canvas display toggle!

Should use >>= instead of <$>.

@sharkdp First of all I wanted to say flare still looks awesome!

I have noticed a few CSS problems in the try purescript site:

1. in the temperature example the temperature picker goes over the temperature label (probably because the width for it is 100px). Perhaps a putting the components in a table will work?
2. Components like the font size for the title or hue and radius in the drawing example are invisible to me. I can manipulate them if i press where they are supposed to be but i can't see them.

This is using Firefox 50.

edit: I can, however, see the sliders for hue and radius fine on my phone (also firefox).

would be nice to have this on 0.11.5. Was trying to write some code with InstanceSigs.

I'd like to consider this so that we can add more interesting components more easily over time.

The one I'm interested in right now is adding a new panel with a list of errors and warnings.

I'd like to take this on, but it should probably wait until the full release (as in after release-candidate period), and there's a non-rc 0.12 package set.

EDIT:

Looking at this more, it seems some dependencies will need to be updated as well. This is a possibly nonexhaustive list:

• thermite and its dependencies:
  • aff
  • coroutines
  • dom
  • freet
  • profunctor-lenses
  • react-dom
  • react
• behaviors and its dependencies:
  • sets ordered-collections
  • filterable
  • nullable
  • drawing
  • effect
• flare (sparkle) and its dependencies:
  • const
  • exists
  • free
  • graphs deprecated, replaced by?
  • profunctor
  • quickcheck
  • semirings
  • validation
• mathbox and its dependencies:
  • console
  • foreign
  • free
  • globals
  • nullable
  • maps ordered-collections
  • lens
  • either
  • signal: bodil/purescript-signal#65

It would be nice to have a selector which would point the front end at the various backends.

I found myself wanting to typecheck an Aff code snippet. TryPS doesn't have Aff in the core package-set, which I find a little odd, as several libraries/UI frameworks depend on it.

Would be nice to add an option to see compiled JS output

I tried constructing a URL using the ID of my own secret gist.

I see the following:

Error 1 of 1

  Unable to parse module:
  unexpected end of input

While a phenomenal feature, I wrote some laggy synchronous code that intermittently froze the editor when I typed too slow. Alternatively a longer delay might help e.g. half a second.

If we can get the server to produce errors in a structured format instead of just an error message, we'd be able to do fancy things like turn various parts into links which move the editor cursor - for example if the error mentions a line number.
Could possibly have links to Pursuit for mentioned types/terms aswell. For example, if the error mentions the type Int, we could link to https://pursuit.purescript.org/packages/purescript-prim/0.8.0/docs/Prim#t:Int

When using iOS to view try.purescript.org the bottom of the coding pane is cut off at the bottom of the viewport, if there's more code than will fit in the pane it is cut off and no vertical scroll bar is displayed, scrolling does not work.

Additionally, tapping to set the focus in the box works (as does typing normal characters into that box), however the arrow keys on an iPad keyboard (physical) do not function: pressing them has no effect.

To get touch support for mobile devices.

Thanks!

And redirect to the gist, if appropriate.

I think we have enough JS code here now that we should port it to PureScript.

To get some fixes to touch support for mobile devices.

Several times I've refreshed the page (Super+R) instead of opening a new tab (Super+T) 😭

• Easy fix: ask whether to navigate away from an edited buffer.
• Nice fix: keep active buffer in local storage.

module Main where

import Data.Set as Set

f = Set.filter

gives error Unknown value Set.filter

http://try.purescript.org/?session=b41d7125-008d-3ca9-4a89-400ee47ad740