Its a little thing, but i like how you literally don't need to click on any buttons to save / create a new one / etc. I also like how you can create your own customized path to help you remember the link... just type in a new path and start editing, and you now can share that custom URI.
I think its important to create as little friction to usage as possible, and you've done that.
What's cool is that feature was completely intuitive and you didn't need to point it out. Again, a little thing, but the little bit of delight users experience when they "discover" these types of features goes a long way.
I also like the URL feature, but unlike the other person I did not intuitively expect to type in a a random url and have that work. Its not something people typically do. That said, its pretty cool. You should edit your how to use to include that.
The first thing that I loved about this, that drives me crazy on other real-time online editors, is that pressing "tab" actually creates a tabbed space, and doesn't change the active textarea. Nice job!
Any plan on open sourcing the code to do the real-time editing? I would love to use this real-time editing concept in a project I'm working on.
Basically on keyup I ship the whole contents of the editor and the cursor position to firebase. I'm also keeping track of all the active connections to a scratchpad document so I know who is typing. Anytime the code changes on the server, it triggers a callback function on each client that will update the contents of the textarea. If someone else is typing, the document is locked so only 1 person can type at a time. This way I can avoid all the potential merge conflicting type things that can happen.
Not sure what server architecture you're using, but in Node.js there is a pretty amazing package that integrates with ACE called ShareJS (http://sharejs.org/).
Have you experimented with synchronizing cursors at all?
Thanks! I'll have to read up on OT. Our backend is totally hosted by Firebase, other than a simple Sinatra app that generates the unique IDs.
When you say synchronizing cursors, do you mean having multiple cursors (google docs style) or having a single cursor be in the same position for all clients? We are doing the latter, and I wasn't aware it was possible to do the former with ace but I would love to do it if I can
Seems that I can't reply to the child of my sibling comment so I'm replying here.
ACE is quite ridiculously powerful. On its primary implementation (http://c9.io), it supports multiple cursors with concurrent editing.
I've been able to use ShareJS to get concurrent editing working (see: http://plnkr.co/edit/?p=preview&s=HN4933608) but haven't had a chance to display visual cursors for all simultaneous users. I was thinking that I could get that working using Firebase.
Hi, I'm one of the Firebase engineers working on keeping clients connected.
We use a mix of different methods to maintain a connection. We normally start with our custom long polling implementation and move to websockets when they are available. We do not currently make use of any flash sockets.
That has nothing to do with Scratchpad, it's in the spec for HTML frames: "Infinite recursion is prevented. Any frame that attempts to assign as its SRC a URL used by any of its ancestors is treated as if it has no SRC URL at all (basically a blank frame)."
Thats awesome. Also looking at the source, I discovered it's using keymaster.js and firebase.js, which are new to me. And the implementation of scratchpad.io is very simple and elegant. The design is beautiful, and the code (in scratchpad.js) is so simple that it makes for a good tutorial on using firebase and ace.js.
In fact, if anyone else is interested in forking the code and experimenting with it, feel free to fork my plunk and go to town:
(Hope you appreciate the irony of forking scratchpad.io via Plunker. Also, it'd be wicked if Plunker could automatically "fork" html webpages, pull in all the required resources and/or updating path references).
For a first time coder, being able to see your page change live is very helpful in getting to learn HTML and CSS. This is an amazing complement to the book you are writing - nice work Nathan!
This is really great, especially as a compliment to the learning tools coming to market.
For front-end designers looking for a similar effect within your own text editor and browser window, I can not live without the CodeKit app now. It does a similar real-time effect each time the template files are saved. Also supports less, js debugging/minification, and other production processes.
Slightly off topic: You use "enough to be dangerous" with a positive meaning, as in enough to make a real difference in the world, while Alexander Pope quote you use is probably negative: "A little learning is a dangerous thing." as in, someone who knows little can do more harm than good.
I don't wanna down a nice looking project, very well done on the interface but, another one? There are already like 7+ of these I don't really see the need to produce another one especially one that is HTML+CSS only when many of the others feature JavaScript and more.
I think the key extra feature is that you can share what you're working on with someone else and have both people collaborate in real-time (i.e. changes on either end show up near-instantly on the other side). Supplemented by a voice channel, this could potentially be useful.
JSFiddle et. al. don't have this, but I'm sure there are others out there that do.
Because none of them are the right solution for every use case. http://cssdeck.com/ comes closest but OP's solution is much more simple and to-the-point.
You can modify Emacs so that it does something on every change in the current buffer, like for example save the change to disk if it's a file-backed buffer.
You could then have a script refreshing the browser on every file change (do it from outside Emacs, calling shell scripts from Emacs or anything 'non-Emacsy' from Emacs is too slow for the usecase here).
However you'll probably have to find a way for the 'save file on every buffer modification' to be very fast otherwise it's going to annoy you and prove impractical.
Btw I can't wait for someone to implement at least part of Emacs in JavaScript so that, eventually, users used to Emacs shall have the possibility to have a Web text editor that doesn't s*ck. Maybe using ClojureScript + the implementation of Emacs redone in Clojure (I think there's a project trying to do that right now).
This is awesome! I constantly look for live editors but haven't found a good one for front-end. I tried Adobe Brackets, Firebug (for in-window editing) but all had their complexities and constraints. Scrathpad.io is by far the most intuitive and best one for HTML and CSS out there!
Not to detract from what is a pretty cool project, and I hope OP had fun making it, but: http://codepen.io is this and quite a bit more. It supports HTML+JS+CSS as well as e.g. Jade, SASS and CoffeeScript- if that's what floats your boat- and some nice social features, like featured pens and saving to Gists.
Other commenters have pointed out a myriad of similar such services. I'm surprised Codepen hasn't come up already.
@brycecolquitt, you are obviously very talented, and I look forward to whatever you come up with in the future. I just hope it's not in a space as hotly contested as this.
Thanks, but this was actually made by my friend Nathan Bashaw (nbashaw). I just submitted it because I think it's awesome :) I think the tool is great for a certain group of people: beginners and front-end folks who want to quickly see what something looks like or do some debugging.
I'm not sure if codepen supports the realtime google-docs-style collaboration, either, which Scratchpad is good for. It's simple product with no superfluous features.
Yeah but it's nowhere near as nice to edit with. The textarea's are short, the content frame is short... I think this is a case where simplicity wins out.
SASS would be a cool feature though.. (as long as it came with Compass)
Very nice. Love the responsiveness and good use of (OS-aware?) keyboard shortcuts.
Bug: (Chrome Version 23.0.1271.97 on OSX)
Expand the side panel and select a document from the RECENT list. The editor area doesn't update completely; the text loads, but there are only line numbers up to the length of the previously viewed document and it's impossible to move the cursor below the last line number (http://i.imgur.com/h9nMh.png).
EDIT: Correction, the line numbering is correct, the problem is with the line-height in the editor.
Absolutely amazing.
A couple things that bother me, and they might just be from Ace.js:
When typing text into a <p> or an <h1> for example, if I type "I'm", I get the smart double quote feature, and end up typing:
I'm going to the zoo'
Likewise, if I go back into the stream of some text in a <p>, and want to wrap it in a span, if I click at the start of it and type <span id="foo">, I get another span on the other side of my cursor, pushing the existing text over.
Otherwise, utterly fantastic tool. Trying to use it for real work already :)
Pretty nice, I'll probably be using this for debugging and examples.
Bug:
Open the about panel by clicking the icon in top left (three horizontal bars). Close the panel by clicking the same icon.
Maximize the preview window by clicking the arrow in the top right of the edit panel. Click the arrow to view the code panel again.
The about panel pops out as well and the arrow button covers the show/hide about (three horizontal bars) button. Expected behavior: it should return to the view that I had before maximizing.
I would love to be able to work in realtime (a la Etherpad) with someone else - would take pairing to a whole new level. Also, style management could quickly get messy - I know you are trying to keep the UI as simple as possible, but I would love to be able to quickly toggle between HTML and CSS on different tabs (instead of scrolling).
Nicely done on Scratchpad. The interface seems to be the right combination of simple and intuitive. It would be great to see the source code as many others have said.
I'm particularly curious as to how you've done the collaborative bit given that you don't have explicit control over the order of operations of edits.
Quick thing: I have a page quickramen.com/test/test that has links that navigate around the page. If you click those now, it loads the code again in another mini-window and doesn't go anywhere.
JUST a bug to be aware of if you're keeping a log!
I'm building a similar one (it also allows you to inspect html elements like using Firebug or Webkit's Dev tools), and it's a native Windows app (and really fast one!) http://liveditor.com
Nice work and all, but what's wrong with a local .html file your favorite text editor, and a browser? I've been doing that for years to play around with html, css, and js.
1. Create a file
2. Open it in your text editor
3. Edit code
4. Switch to browser
5. Open up the file
6. Switch back to editor
7. Edit code
8. Hit save
9. Switch back to browser
10. Hit refresh
11. GOTO 6
I use Livejs for the same effect, but this is much smoother obviously since it can trigger on key press rather than polling the resource constantly from the web page.
I think its important to create as little friction to usage as possible, and you've done that.