On the flip side, it is styled very much to mimic Chrome's own editor. And that makes me wonder. When or why would I use this over what is already built into Chrome?
Actually the Chrome DevTools can save your changes back to disk! It's not well known, and its fairly new so I don't blame ya.
Here's how it works: (1) make changes to styles as you do (2) you can click through to the Sources pane and live-edit styles there, just like a text editor. (3) Right click and save to disk. choose where to save the file (4) Make some more changes (5) Just hit ctrl-s (or cmd-s) to immediately save back to disk in the same location.
I just made a screencast to show this in action: http://www.youtube.com/watch?v=Qy5obNItQiQ
Sounds super hard to me, but what you built looks super hard too :)
Is the audience not these professional people? Is it aimed more at the shallower end of the learning curve?
A lot of people just use a text editor, their browser and firebug, so we want to serve those people but with a much faster and streamlined experience.
Not to say it doesn't look neat, I'm just honestly having trouble finding the differentiating factor.
Right now, web development is carried out with an array of disparate tools which vaguely connect to each other, if at all, plus you have to know how to set them up. pixelJET is not trying do anything new, or anything that can't be done by some existing combination of tools, but it brings them all together in an easy to use package, available anywhere in the world, on any browser.
livereload doesn't just refresh the page, it also updates css/js on the fly also through ajax without any lag.
Our code editor is actually the open source "Ace editor" (http://ace.ajax.org).
Of course, not everybody wants to code inside their browser, and that's fine. For those that do, we aim to make pixelJET the best way to do that.
Full iPad support is not ready yet but should be coming soon.
A bug is currently preventing the code editor from loading on the iPad browser. Quickfire (the panel down the bottom, that replaces the browser debugger) will load fine, but the interface is slightly awkward to use because it is not touch optimised yet.
Can you explain the hosting aspect?
Where do the files sit?