Maybe just updating ones?

Visually indicate it, somehow

I don't think people will accept having to write + 3 4 instead of 3 + 4. :(

1. first pass parse into cons-list
2. run active parse filters (use monad to activate a filter for the current file)
3. run macros

[a b c d] instead of [a, b, c, d]

This is more friendly for indented code and for vararg macros.

Define or[, and[, any[, all[, etc.

Right now, they produce a Leisure file -- needs markup

User should freely be able to use save-as

Allow HTML in comments, use WYSIWYG editor when you click on them

Cloud collaboration using Xus. Hosts: https://github.com/joyent/node/wiki/Node-Hosting

some standard services: shared notebooks

Editing either side should update the other

Clicking top apply SVG node shows problem for fred = 1 + 2 + 3

SVG rendering of AST with links and stuff

Type assertions work, but more general patterns would be nice. This is a decent way to allow extending definitions.

allow function definitions in do:

do
  fred x y = x + y
  fred 1 2

Autobuild should replace the button anyway, but this will probably still be a problem

Our dogfood is good. We should taste it!

Also, demo integrating with a few things, like D3, Raphael, jQuery UI, etc.

Use type assertions for printing

Need to be able to block bootLeisure from running on a require

keep set of all asts, recursively

remove ast from set when it runs

Show all functions with incomplete coverage and highlight source regions that didn't execute

Use File System API

highlight macros and functions with different colors

Start with a reference implementation for local machine

Later, make some for g-drive, drop-box, orion, etc.

• Add parse tree button to exprs
• Add parse tree button to test cases

Done

• Failed test cases should show expected vs actual results
• Successful test cases should show expected result on hover
• Pencil next to test cases to show/hide source and show the current expected value
• Storage
  • Should explain to the user that it can only access files it creates or world-readable files

Triggered after autobuild

• backspace/delete in a definition box frequently seems to position itself at the end the text
• Get highlighting working, again
• Function doesn't box in when you partially apply
• Names in definitions don't highlight properly
• Many primitive funcs are missing arity
• Switching to a codeDef should mark the function name

Fixed

• Pressing tab after an edit seems to screw things up -- make it like shift-enter
• When the parse tree is showing and you edit the definition, it scrunches the pencil over

Use ``` code fences

C-enter to evaluate

Click nodes to display values from test case

And sometimes close brackets don't highlight, either

Integrate with Cloud9 for git repos

Should update errors all over the place. This doesn't really work, yet.

Clicking between func and expr does weird stuff -- teleports the text cursor, duplicates characters, etc

-- Should this just be full pattern matching, with first-arg type constraints being just an optimization case?

Type constraints:

Introduce type constraint operator, '::', like in Julia. This means to use the dispatch mechanism when calling the function. Calls to polymorphic function with unhandled type produces an error, so this also provides type checking.

printString x::list = printString-list x

Subtypes -- used in dispatch and type constraints

subtype type subtype -- monad to declare a subtype

isSubtype type subtype -- returns boolean

JS prototypes

Dispatch on first arg can be implemented as JS method

Dispatch on other args can be done like in Xtend

Use an eyeball icon

Leisure needs to start a Xus server.

Xus needs to support web sockets and serve up a page for an iframe that reverse-connects to a xus proxy

Each file should have the ability to enable or disable parsing filters and operators.

By default, only the "standard" filters and operators should be in place -- keep naked parse filter monads in separate files (not in library imports).

clearParseFilters -- clear parse filters and operators
leisureParsing -- only use standard filters and operators

We need more of a paste-board feel, so you can click the background and it makes a sticky note that can be a document

Also, searches should return linked, editable content, so if you edit a search result, it also edits the original sticky note

Change setType and getType to use JS prototypes, with Function as the root -- metadata can be stored in prototype

shows info on the current selection:

• selection position
• brackets
• code box info