Adding the ability to click on the images in the history and have that load

Adding the ability to click on the images in the history and have that load the code and image back into the editor space.

BUG=skia:

Committed: http://code.google.com/p/skia/source/detail?r=14310

[mtklein, 2014-04-22 17:24:17]

https://codereview.chromium.org/246393002/diff/30001/experimental/webtry/js/r...
File experimental/webtry/js/run.js (right):

https://codereview.chromium.org/246393002/diff/30001/experimental/webtry/js/r...
experimental/webtry/js/run.js:91: // The response is JSON of the form:
I love this kind of note.  Thank you.

https://codereview.chromium.org/246393002/diff/30001/experimental/webtry/js/r...
experimental/webtry/js/run.js:97: console.log(e.target.response);
Intentionally leaving the console.log in there?

https://codereview.chromium.org/246393002/diff/30001/experimental/webtry/webt...
File experimental/webtry/webtry.go (right):

https://codereview.chromium.org/246393002/diff/30001/experimental/webtry/webt...
experimental/webtry/webtry.go:447: code, _ = getCode(hash)
Might as well handle this error?  Even if this is logically impossible, it still
could happen due to network error or something like that right?

[jcgregorio, 2014-04-22 18:02:08]

https://codereview.chromium.org/246393002/diff/30001/experimental/webtry/js/r...
File experimental/webtry/js/run.js (right):

https://codereview.chromium.org/246393002/diff/30001/experimental/webtry/js/r...
experimental/webtry/js/run.js:97: console.log(e.target.response);
On 2014/04/22 17:24:18, mtklein wrote:
> Intentionally leaving the console.log in there?

Done.

https://codereview.chromium.org/246393002/diff/30001/experimental/webtry/webt...
File experimental/webtry/webtry.go (right):

https://codereview.chromium.org/246393002/diff/30001/experimental/webtry/webt...
experimental/webtry/webtry.go:447: code, _ = getCode(hash)
In case of error getCode returns the empty string, which is what I want. Also,
getCode will log any errors it encounters, so I don't need to do that here.

On 2014/04/22 17:24:18, mtklein wrote:
> Might as well handle this error?  Even if this is logically impossible, it
still
> could happen due to network error or something like that right?

[mtklein, 2014-04-22 18:16:50]

On 2014/04/22 18:02:08, jcgregorio wrote:
>
https://codereview.chromium.org/246393002/diff/30001/experimental/webtry/js/r...
> File experimental/webtry/js/run.js (right):
> 
>
https://codereview.chromium.org/246393002/diff/30001/experimental/webtry/js/r...
> experimental/webtry/js/run.js:97: console.log(e.target.response);
> On 2014/04/22 17:24:18, mtklein wrote:
> > Intentionally leaving the console.log in there?
> 
> Done.
> 
>
https://codereview.chromium.org/246393002/diff/30001/experimental/webtry/webt...
> File experimental/webtry/webtry.go (right):
> 
>
https://codereview.chromium.org/246393002/diff/30001/experimental/webtry/webt...
> experimental/webtry/webtry.go:447: code, _ = getCode(hash)
> In case of error getCode returns the empty string, which is what I want. Also,
> getCode will log any errors it encounters, so I don't need to do that here.
> 
> On 2014/04/22 17:24:18, mtklein wrote:
> > Might as well handle this error?  Even if this is logically impossible, it
> still
> > could happen due to network error or something like that right?

lgtm

[jcgregorio, 2014-04-22 18:18:29]

The CQ bit was checked by jcgregorio@google.com

[commit-bot: I haz the power, 2014-04-22 18:18:42]

CQ is trying da patch. Follow status at
https://skia-tree-status.appspot.com/cq/jcgregorio@google.com/246393002/50001

[commit-bot: I haz the power, 2014-04-22 19:32:09]

Change committed as 14310