Git Product home page Git Product logo

browser-editor-tests's People

Watchers

 avatar  avatar

browser-editor-tests's Issues

Define selection criteria

Editors don't need to tick all these boxes, but we do want to know which editor supports what features so that a rational decision can be made about which one is the best fit.

  • feel like a code editor, not a text editor
  • line numbers
    • with code folding
  • unicode support (even in 2024, make sure to test)
  • document-change events
    • OT/diff based
      • sensibly debounced/aggregated (i.e. not every single letter its own OT/diff)
    • if not, at least in a way that's easily turned into OT/diff
  • mini/sidebar file view for fast navigation and file shape memorization
  • works properly on mobile
  • easy "multi file" (e.g. tabs)
    • if not, easy "multi doc per editor"
    • if not, at least easy "make multiple editors without them clobbering each other"
  • track record of fixing problems
  • good documentation
    • easy to understand methodology
    • real recipes (rather than toy examples)
  • good support
    • issue tracker
    • forum
    • async and/or real time chat (IRC, matrix, discord, whatever)
  • actual community (e.g. folks actually building things on top of this editor)
  • syntax highlighting
    • JS
    • JSON
    • HTML
    • CSS
    • Python
    • Rust
  • linting
    • JS
    • JSON
    • HTML
    • CSS
    • Python
    • Rust
  • error flags as you type
  • autocomplete
  • undo-redo
    • sensible undo-redo (i.e. not "every single letter is a state")
  • find in "all editors" rather than just current view
  • search and replace
    • with regex
  • pretty print
  • plugin system
  • "file preview" (markdown, html etc?)
  • collaborative editing

add some kind of simple rewind UI

Currently it's a combination of manual fetch(`/history`) and fetch(`/rewind/somehashhere`, { method: `post`}), but this should be a graph of some sort that we can just click -> "rewind?" -> [yes] -> call the rewind URL.

define a <file-tree> custom element?

This should really be a <file-tree> element with <file-entry> and <dir-entry> and baked in file moving, sorted presentation, drag-and-drop upload, etc.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.