Skip to content

General

58 results found

  1. Support Markdown in text cells

    Notebooks like https://tonicdev.com/tonic/welcome/ highlight the strength of having both text & code cells.

    Support for basic text formatting features like ordered/unordered lists, emphasis, etc would make this advantage over, says, Gists even stronger.

    89 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Support compile-to-js languages

    It would be nice to add, perhaps using some annotation syntax if it could make things simpler to implement, source processing directives such as Coffeescript, Livescript or Typescript.

    E.g.
    `
    // :coffee

    sayHi = ->
      'Hello from Coffesescript."

    do sayHi
    `
    ... could just work. 

    38 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Running TonicDev locally

    I want to be able to run TonicDev locally. For two reasons mainly:

    1. Performance with the network latency is too much for TonicDev to be a pleasant developing experience.
    2. Without any internet connection, I can no longer access my things.
    28 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Code completion

    It should be great to have some code completion while typing

    26 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Support executing frontend javascript

    Would be awesome to be able to have a snippet of javascript and chose it to be evaluated in a browser environment below the editor, so I could demonstrate how to built React components for example. Using something like babel (on your side), would probably make it simpler to implement.

    25 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Local files / private modules

    Sometimes you have a private module (not published on npm), or just a local project or group of files that would be useful to interact with in Tonic. We should make that possible.

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Coffeescript

    As surely expected us fringe Coffee coders want it everywhere. Github seem to like it, so maybe tonicdev can support it too!

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Dark/custom theme

    Should you have resources to spare, please add an optional dark css theme.

    Should you have more available, please add the ability for users to create and upload custom css themes to their profile.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Provide a badge for GitHub readme

    A badge for GitHub with something like "Try on Tonic" would be a great idea :)

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Support requiring an npm package directly from a github repo

    Npm allows you to install packages directly from github. It would be nice if there were a way to do this in tonic as well. For me, it would be particularly useful for checking out changes that have been made to a package on github but not yet on npm.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Vim Keybindings

    I love everything about the idea of this app, but each time I try using it I find myself inevitably pulled back to my editor where I can comfortably use the Vim keybindings that I'm used to. Perhaps I'm just odd, but how difficult would it be to add Vim support?

    It seems you are using CodeMirror, and I believe they support Vim Keybindings ( https://codemirror.net/demo/vim.html ) along with Along with Emacs / Sublime Text.

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    under review  ·  Ross Boucher responded

    You’re definitely not alone. Unfortunately, this is one of those things where people have strong preferences.

    Eventually, we’d like to support user preferences like this and font size. But it’s not on our immediate roadmap.

  12. Support for NPM packages installed from git repos "git+https://github.com/..."

    Some NPM packages you want to use require dependencies installed from Github

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Support seeing stack traces

    The viewer for Error types doesn't allow seeing the stack trace which makes it largely useless. See https://tonicdev.com/sethwklein/56631b6ab9d5f30d00d6b5c8

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Ability to prompt users for CLI input

    I'd like to be able to ask the user for a username and password to authenticate to an API. This is a necessary step in demonstrating my NPM package, but I have to resort to hardcoding these or using process.envs which are not easy for users to understand or change.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Embed into READMEs

    This would revolutionize NPM package pages and GitHub repos.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Add a chart display setting

    Every time I run a tonic document where snippets return an array of numbers that I want to display as a line chart, I have to change the view every time from a property explorer to a chart, and then select line chart. This is getting really annoying when I'm adding extra functions to the document all the time. It'd be really great to be able to save the view I've selected.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Allow users to specify custom user script with npm support in preferences

    Allow registered users to specify a js script in preferences (alongside environment variables) to be executed when viewing notebooks. Similar to greasemonkey scripts but with npm support and saved in user's profile. Can be used for fine-tuning of users' environment

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Document the formatting options for text cells

    URLs appear to be automatically converted to links. Are there any other formatting options?

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Open existing literate markdown or JS files as a notebook

    Embedded notebooks are great, but it'd be even easier if you could load (from github/gist) existing documentation with code examples, or existing code with comments, as a live notebook.

    For markdown, the obvious way to split into cells is turning any code blocks into code cells. Docco seems to be the commonly used convention:
    https://stackoverflow.com/questions/4462706/how-can-i-create-annotated-source-code-like-underscore-js

    For JS splitting into cells involves more guesswork. Literate JS via code-with-comments seems not so common, and anyway it's more important what it'll do on regular code not expecting such use.
    But there is one obvious answer: the inverse of how you already export the…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Support sqlite (sqlite3 package)

    Is it possible to support sqlite in examples? Currently I'm getting: https://tonicdev.com/jakubknejzlik/sqlite3-test

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3
  • Don't see your idea?

General

Categories

Feedback and Knowledge Base