Suggestion: remove edit and copy fields in examples

[pgundlach]

A suggestion: please remove the edit and copy buttons at the top of the examples:

IMO it is better to allow editing right away and copying can be done with the keyboard or push the button to the bottom.

I think the second is easier to follow.

I know that design will be added later on, so can just take this as a suggestion and close the issue.

This is for example how the Go documentation look in "Dash":

Still obvious that you can "run" the code, but IMO less obtrusive to the user.

[dbitouze]

copying can be done with the keyboard

And the mouse. I'm in favor of the "copy" button: that's something which is missing e.g. in SE: selecting the code with the mouse is sometimes painful, especially when the code is long enough to not being entirely displayed.

Otherwise, I second the suggestion about the "edit" button.

[josephwright]

This really is one for Jonas, as it's about design/user access.

[pgundlach]

(@jonasjacek feel free to just close this issue, I don't think it needs to stay around as open)

[josephwright]

@pgundlach It's an important question, so I think we keep the issue open until @jonasjacek has made some mock-ups: probably we need to see how different interfaces 'feel'.

[davidcarlisle]

@pgundlach yes I wondered about this. As Joseph said Jonas will probably want to move things around anyway, but I'll mention a couple technical things that lead to the current interface.

The copy button is mostly a convenience to avoid having to select large blocks with a mouse, but it also places the plain text on the clipboard with all syntax highlighting stripped. If you copy the formatted version what you get when you paste depends on the receiving client.

The edit button is similar, with the syntax highlighting being used (the default one on github pages) if you simply enable the <pre> element to be conteteditable=true then most editing works but you can not add a newline as every line is in a formatted span and the return key is disabled (at least in some browsers). So when you click on edit, the content is replaced by its text content and you lose all syntax highlighting but you can add newlines as expected.

So (with the current systems) having edit always on would mean no syntax highlighting on the site.