797479 - Implement stub editor for live samples in advance of JSFiddle integration

Status: RESOLVED INVALID

(developer.mozilla.org Graveyard :: Editing, defect, P1)

Description

[Les Orchard [:lorchard]]

In anticipation of jsFiddle API changes to use it as an editor, build an initial primitive editor for live samples. Say, just 3 text areas and an iframe: HTML, CSS, JS, and a rendered view

Comment 1

[Les Orchard [:lorchard]]

For bonus points, try to make this work with a POST API that anticipates jsFiddle. That is, mock up the editor as a service to the site, even though it lives on the same site.

Comment 2

[Les Orchard [:lorchard]]

And some quick top-of-head notes from our jsFiddle meeting about the round-trip POST API:

* Hit Edit on a live sample, generate a temporary ID

* submit a POST form with html,css,js + temp ID to jsFiddle using this API: http://doc.jsfiddle.net/api/post.html

(example http://jsfiddle.net/zalun/sthmj/embedded/result/)

* Hit Save in jsFiddle (or the stub editor), receive a POST at some URL with html,css,js + temp ID. (eg. POST /en-US/docs/samples/{ID})

* Create a new live sample revision based on the updated html,css,js

* Show updated sample

Comment 3

[Les Orchard [:lorchard]]

This can also be an incremental opportunity for better live sample editing, assuming it takes awhile to get JSFiddle working.

As it stands now, a live sample exists as a section + code listings, and those can be edited in the CKEditor WYSIWYG. But, that might not be the friendliest way to edit a sample. 

So, a stub editor implemented for this bug could improve things a bit by allowing the code listings of a particular sample to be edited in a kind of "JSFiddle-lite" that uses the ACE editor for each section.

Comment 4

[ali spivak]

Have Live Samples already implemented - if we still want to go in this direction then please reopen