# SWISH TODO list

## Query editor

  - Quickly create a query from a predicate?
    - Menu from source editor based on cursor position
      - If in head, create goal from current predicate
        - Can we do something with the arguments?
      - If in goal, copy goal to query window

## Runners

  - Get back to the associated source version (open new editor tab?).
  - Find source changes compared to current version (easy)

## Debugger

  - Show stack and choice-points?
  - Display constraints.  How?
  - breakpoints in notebooks (mostly needs to deal with source locations)

## Highlighting

  - Deal with multiple sources from a notebook (background programs).
    - Analyse all programs and queries using a single callback?

## Rendering framework

  - User provided rendering?
    - Allow for rewriting answer terms?
    - Allow generating HTML?  How to deal with security?

## Dashboard

  - Complete type support for parameters/1
  - Allow replacing the query with the dialog.  Can use query settings to
    switch between the two modes.

## Sharing

First option was TogetherJS.  Now doubting, as it may be much better to
_not_ see exactly the same UI for cooperation.  What about

  - Allow for sharing editors
  - Allow sharing runners (= query+program)

## Make teams

  - A team has a homepage, which is a notebook.
  - Workflow:
    - Save a copy of the "Team homepage" example notebook.
    - Turn into team homepage
      - Add "team" tag
      - Have a members query, returning a table.  Using an
        HTML cell?
      - Create as a copy from an example page?
    - Invite team members (is this a general page behaviour)
      - Input with look-ahead for searching people (or type
	email).
      - Text area for invitation
      - Sends e-mail.
  - Thus a team is
    - A page
    - Link to members
  - Small installations can automatically add all users to the
    one team.

## Saving files

  - Provide auto-save (in browser?)
    - How to recover?

## Search

  - Implement string search with result page
    - `Harmonica' with
      - Found files (including full text search inside them)
      - Found manual entries
      - Found source locations

## Tabbed editor

  - Source search: pass number of items being searched and
    if there are too many hits, balance over files.
  - Set tab-width per source?
  - Debug (trace) through included files
    - Works, except for following the source.
  - Deal with files/line numbers over multiple files
  - Staging
    Control-S (whatever) saves data to `staging area'.
    - In addition to HEAD, introduce STAGE (gitty solution)?

## Notebooks

  - Save notebook/program as new profile?
  - Organize in sections
    - Group by ## in markdown sections using super-divs.
      - Allow for collapsing a group.
    - Insert dynamic menu around cells.
  - Section actions
    - Collapse (keeps title)
    - Collapse all
    - Move (drag and drop)
  - Delete query from menu?  Better: undo for delete.

## SWISH as Prolog frontend for local usage

  - Improve source search
    - Full search
    - Search file names
    - Regex support
    - Select search targets
      - File names
      - Content
      - Gitty, filesys, examples
  - Debugger:
    - Set breakpoints in non-pengine sources
      - For shared operation this requires limiting a breakpoint to
        the pengine thread.
    - Get a stack overview.
  - Mark files as pengine_src, loaded, not_loaded
    - Only send pengine_src with pengines.
    - Detect pengine_src based on alias?

### Permalinks

  - Handle external storage state
  - Add permalink as metadata
    - To generated PDF (R integration)
    - To CSV

### Bugs

  - Colouring of /library/http/html_write.pl.  Broken sequences:
    - DCG exports
    - ?- [file].
    - Variable as goal.