On Tuesday, 20 December 2016 at 02:25:06 UTC, Joakim wrote:
> When all tests pass, would be better if it said that, rather than "No output," which it says now.

Excellent idea -> https://github.com/dlang/dlang.org/pull/1527 :)

On Monday, 19 December 2016 at 17:44:29 UTC, Andrei Alexandrescu wrote:
> Take a look e.g. at https://dlang.org/phobos-prerelease/std_algorithm_iteration.html. Examples now have "Edit" and "Run" buttons that allow you to play with them online and see what they output. Changes for the ddox version forthcoming.

Nice!

On Monday, 19 December 2016 at 17:50:17 UTC, Seb wrote:
> I would like to add that this is in an experimental/testing stage and hopefully will get stable with the next release ;-)

Great work, Seb!

On Monday, 19 December 2016 at 17:50:17 UTC, Seb wrote:
> On Monday, 19 December 2016 at 17:44:29 UTC, Andrei Alexandrescu wrote:
>> Take a look e.g. at https://dlang.org/phobos-prerelease/std_algorithm_iteration.html. Examples now have "Edit" and "Run" buttons that allow you to play with them online and see what they output. Changes for the ddox version forthcoming.
>>
>> Related: https://github.com/dlang/dlang.org/pull/1297, https://issues.dlang.org/show_bug.cgi?id=16984, https://issues.dlang.org/show_bug.cgi?id=16985.
>>
>> Many thanks to Sebastian Wilzbach who took this to completion, and to Damian Ziemba for working on the online compiler code!
>>
>>
>> Andrei
>
> I would like to add that this is in an experimental/testing stage and hopefully will get stable with the next release ;-)

Awesome.

On Tuesday, 20 December 2016 at 07:04:38 UTC, Seb wrote:
>
> https://github.com/dlang/dlang.org/pull/1527

Nice. It's pretty awesome!

When clicking the "edit" button, a new box appears with the example's code in it but editable. Then when clicking "run", the editted code disappears (it's saved for future use, pfew!).

How about this: when clicking _either_ "edit" or "run", the non-editable code box disappears, and the edittable code box appears and stays there forever.

(also, the height of the editable-code-box is too small; should fit the whole example's code?)

cheers,
  Johan

On Friday, 23 December 2016 at 23:52:48 UTC, Johan Engelen wrote:
> On Tuesday, 20 December 2016 at 07:04:38 UTC, Seb wrote:
>>
>> https://github.com/dlang/dlang.org/pull/1527
>
> Nice. It's pretty awesome!
>
> When clicking the "edit" button, a new box appears with the example's code in it but editable. Then when clicking "run", the editted code disappears (it's saved for future use, pfew!).
>
> How about this: when clicking _either_ "edit" or "run", the non-editable code box disappears, and the edittable code box appears and stays there forever.
>
> (also, the height of the editable-code-box is too small; should fit the whole example's code?)
>
> cheers,
>   Johan

Hehe, that's already in the queue:

https://github.com/dlang/dlang.org/pull/1529

On Saturday, 24 December 2016 at 00:04:54 UTC, Seb wrote:
> On Friday, 23 December 2016 at 23:52:48 UTC, Johan Engelen wrote:
>> On Tuesday, 20 December 2016 at 07:04:38 UTC, Seb wrote:
>>>
>>> https://github.com/dlang/dlang.org/pull/1527
>>
>> Nice. It's pretty awesome!
>>
>> When clicking the "edit" button, a new box appears with the example's code in it but editable. Then when clicking "run", the editted code disappears (it's saved for future use, pfew!).
>>
>> How about this: when clicking _either_ "edit" or "run", the non-editable code box disappears, and the edittable code box appears and stays there forever.
>>
>> (also, the height of the editable-code-box is too small; should fit the whole example's code?)
>>
>> cheers,
>>   Johan
>
> Hehe, that's already in the queue:
>
> https://github.com/dlang/dlang.org/pull/1529

This is really wonderful. An excellent feature for new users – lowers the cost of "just try it out".

Feedback:

1. It will be aesthetically better if the edit/run buttons are inside the code box, say just inside the right top corner.

2. Could we add a "open in an external website/new window" icon/button (for example: http://findicons.com/files/icons/2315/default_icon/256/open_in_new_window.png ) to open the example in say a dpaste window or an equivalent playground.

Thanks,
Saurabh

On Saturday, 24 December 2016 at 06:08:49 UTC, Saurabh Das wrote:
>
> Feedback:
>
> 1. It will be aesthetically better if the edit/run buttons are inside the code box, say just inside the right top corner.

I agree the button placement should be improved, I think they should be immediately to the right of "Examples:"

e.g. "Examples: [Edit][Run]"

Which makes it more clear that the examples can be run & edited.

On Saturday, 24 December 2016 at 06:15:16 UTC, safety0ff wrote:
>
> I agree the button placement should be improved, I think they should be immediately to the right of "Examples:"
>
> e.g. "Examples: [Edit][Run]"
>
> Which makes it more clear that the examples can be run & edited.

I didn't see that there could be text between the "Examples:" line and the code box. Anyways, I agree with the feedback that the buttons off to the right is difficult to notice.

On Saturday, 24 December 2016 at 06:08:49 UTC, Saurabh Das wrote:
> On Saturday, 24 December 2016 at 00:04:54 UTC, Seb wrote:
>> Hehe, that's already in the queue:
>>
>> https://github.com/dlang/dlang.org/pull/1529
>
> This is really wonderful. An excellent feature for new users – lowers the cost of "just try it out".
>
> Feedback:

Thanks for your feedback :)

> 1. It will be aesthetically better if the edit/run buttons are inside the code box, say just inside the right top corner.

Sure - that should be fairly trivial.

> 2. Could we add a "open in an external website/new window" icon/button (for example: http://findicons.com/files/icons/2315/default_icon/256/open_in_new_window.png ) to open the example in say a dpaste window or an equivalent playground.

Yes, that would be pretty nice to have.
Unfortunately the maintainer of DPaste has been quite unresponsive in the past, so it's not possible with DPaste (e.g. we would need a simple POST API which returns a URL).
If someone is planning to reboot sth. like DPaste (e.g. with DUB support, fast caches, ...), please let us know!