Check this out: on http://dlang.org you can actually click in the code example and edit it, then click "Run" and pronto, you see the output!

Damian is actively working on the UI as I'm writing this. Feel free to chime in with feedback!


Andrei

On 2012-07-05 18:26, Andrei Alexandrescu wrote:
> Check this out: on http://dlang.org you can actually click in the code
> example and edit it, then click "Run" and pronto, you see the output!
>
> Damian is actively working on the UI as I'm writing this. Feel free to
> chime in with feedback!
>
>
> Andrei

That is really cool.

-- 
/Jacob Carlborg

On Thu, Jul 05, 2012 at 12:26:01PM -0400, Andrei Alexandrescu wrote:
> Check this out: on http://dlang.org you can actually click in the code example and edit it, then click "Run" and pronto, you see the output!
> 
> Damian is actively working on the UI as I'm writing this. Feel free to chime in with feedback!
[...]

Won't that be open to abuse? Like if somebody wrote a fork bomb and tried to run it...

Unless the backend server has tight resource control over the code sample executor, of course


T

-- 
Nothing in the world is more distasteful to a man than to take the path that leads to himself. -- Herman Hesse

On Thu, 05 Jul 2012 09:51:50 -0700, H. S. Teoh wrote:

> On Thu, Jul 05, 2012 at 12:26:01PM -0400, Andrei Alexandrescu wrote:
>> Check this out: on http://dlang.org you can actually click in the code example and edit it, then click "Run" and pronto, you see the output!
>> 
>> Damian is actively working on the UI as I'm writing this. Feel free to chime in with feedback!
> [...]
> 
> Won't that be open to abuse? Like if somebody wrote a fork bomb and tried to run it...
> 
> Unless the backend server has tight resource control over the code sample executor, of course
> 
> 
> T

It appears to at the very least strip out calls to shell(). I just tried adding:

writeln(shell("whoami"));

and just got a blank line.

On 5 July 2012 17:51, H. S. Teoh <hsteoh@quickfur.ath.cx> wrote:
> On Thu, Jul 05, 2012 at 12:26:01PM -0400, Andrei Alexandrescu wrote:
>> Check this out: on http://dlang.org you can actually click in the code example and edit it, then click "Run" and pronto, you see the output!
>>
>> Damian is actively working on the UI as I'm writing this. Feel free to chime in with feedback!
> [...]
>
> Won't that be open to abuse? Like if somebody wrote a fork bomb and tried to run it...
>
> Unless the backend server has tight resource control over the code sample executor, of course
>

If it's using the same engine as dpaste ( http://dpaste.dzfl.pl ),
then it is fairly locked down.


-- 
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0';

Great tool!

Just a small layout bug: On Firefox 3.6.4 (on Mac) the [your code
here] tags is misplaced after clicking the "Run" button. It then
overlaps the appearing output box.

Cheers,
André

On Thursday, 5 July 2012 at 16:59:33 UTC, Iain Buclaw wrote:
> On 5 July 2012 17:51, H. S. Teoh <hsteoh@quickfur.ath.cx> wrote:
>> On Thu, Jul 05, 2012 at 12:26:01PM -0400, Andrei Alexandrescu wrote:
>>> Check this out: on http://dlang.org you can actually click in the code
>>> example and edit it, then click "Run" and pronto, you see the output!
>>>
>>> Damian is actively working on the UI as I'm writing this. Feel free to
>>> chime in with feedback!
>> [...]
>>
>> Won't that be open to abuse? Like if somebody wrote a fork bomb and
>> tried to run it...
>>
>> Unless the backend server has tight resource control over the code
>> sample executor, of course
>>
>
> If it's using the same engine as dpaste ( http://dpaste.dzfl.pl ),
> then it is fairly locked down.

On Thursday, 5 July 2012 at 16:26:02 UTC, Andrei Alexandrescu wrote:
> Check this out: on http://dlang.org you can actually click in the code example and edit it, then click "Run" and pronto, you see the output!
>
> Damian is actively working on the UI as I'm writing this. Feel free to chime in with feedback!
>
>
> Andrei

Great!

On 05-Jul-12 20:26, Andrei Alexandrescu wrote:
> Check this out: on http://dlang.org you can actually click in the code
> example and edit it, then click "Run" and pronto, you see the output!
>
> Damian is actively working on the UI as I'm writing this. Feel free to
> chime in with feedback!
>
>

Wonderful! It's fast and fluid, looks good.

Still I would request adding interactive console input.

Some magic with WebSockets & some server daemon on worker machines should do the trick. And being able to run for some time if network client is active.

Browsers without WebSockets can just use non-interactive input with some text area which contents are fed to the program.



-- 
Dmitry Olshansky

Nice.

Should probably remove the references to local files when compilation fails. Not very user friendly to see:

/home/jail/compileme369.d(14): expression expected, not '}'

Would probably suffice just to switch the filename with something less distracting.

2012/7/5 "André" <nospam@spambog.com>:
> Great tool!
>
> Just a small layout bug: On Firefox 3.6.4 (on Mac) the [your code here] tags is misplaced after clicking the "Run" button. It then overlaps the appearing output box.
>
> Cheers,
> André
>

same bug with chrome