« first day (49 days earlier)      last day (3154 days later) » 

00:07
@LuisMendo Alright I've got a beta site up for now. It's mostly functional. I'm still working few a few strange quirks with the octave installation so you may get dropped requests occasionally. If it becomes non-responsive let me know because that would likely mean that the works all got hung up or something.
I've got it at a temporary subdomain of my site until we figure out a real home for it. For now We'll just keep it between the frequenters of this chatroom because I need to figure out how it works under minimal load before we open it up to others. I'm also working on a docker container for it for testing offline (i.e. you could spin up an instance on your local machine).
I'm open to any/all feedback at this point
@LuisMendo There's the link to the (I should really be calling it "alpha") beta site ^^
00:21
Here's the windmill one if you want to kick the tires at all
 
21 hours later…
20:52
@Suever It looks terrific! How nice! I'll do some tests, trying to find corner cases :-)
@Suever A subdomain of your sites seems to me like a perfect place. You've done the compiler, so it should be under your name!
Hey, the search updates on the fly! No need to press enter! :-D
If I search for Z" it seems to give too many results (maybe the quote symbol is ignored?). Z' works fine.
Maximum width of the text output window (without horizontal slider) is 56 chars on my computer. Does that depend on the client? Could it be made bigger? For example reducing the ledt and right margins
I like how help is displayed. I think it looks better now than with columns
The images look great matl.suever.net/…
The question mark in the source code is a nice touch!
What a great work you've done!!
2
Test with [text](URL) format:
This is a link%2F3YG&inputs=200%0A150&versi‌​on=18.3.0)
It doesn't seem to work?
Maybe there's some symbol that SE doesn't like in the URL
Are images automatically scaled? Some challenges require to output an image with a fixed size. For example, here the size is smaller than given by the input
Not that it matters much, though. I'm just commenting things as I see them
21:09
@LuisMendo Wow thanks for the feedback. I'll definitely look at all of these things
Hmmm yea that's strange that link doesn't work
The language looks much more "serious" with all the statements on the right :-)
So I have a few options for "saving" that I'll probably run by you
No, thanks to you!!
I actually really don't like the # in the URL when you hit save
but that's really the only way to get it to work on everyone's browser reliably
Well, if it works...
21:11
but do we actually need to have it modify the URL or would it be enough to have the save button just copy it to your clipboard?
The other option is have the save button do a quick page refresh
I was wondering if "Sym" is the best name for the first column of the help. Maybe "source"? "Statement" is the most correct, but probably won't fit
Yea wasn't sure what to put there :)
Any and all feedback welcome at this point
is it fairly responsive all the way from Spain?
@Suever I think modifying the URL is more intuitive. Is it more difficult that way?
@Suever Indeed!
well it just means that I have to parse the URL in the browser rather than parsing it on the server
Not a big deal, I'll play with it more
@Suever Ah, I see. The other option is probably fine then
21:13
Yea it's actually strange, the server never actually see's anything after the #
We should test which symbols of the URL cause the SE parser to break (not show the link properly)
yea I was thinking about that
we could always base64 encode it
I believe that's what TIO does
Ah, that must be it
Oh, sure
I hadn't noticed
You put the code as is
We can ask Dennis
yea that's what Pyth and others do
sorry the Pyth online interpreter
oh Dennis's encoding is viewable in the javascript
@Suever True. He has in on GitHub
So no need to ask :-)
If you know JS, that is :-)
yea so he does some basic sanitization of the inputs and then encodes it
I'll play around with it and come up with a few options
they're all easy
but links working on SE would be ideal
At the very least, base64 should work, even if URL's become a little longer
Also about the images, yes they are scaled to fit in the output window
but if you use imwrite then the "raw" image data is the correct size
but see in that example you linked to, you used imshow
which in Octave is always going to be the same physical dimension in pixels
regardless of how big the image is
imwrite is the only one that has a variable output image size
So if you actually open that image in a new tab you'll see that it's 12 pixels by 12 pixels
Also about Z" yea it ignores the " It works if you escape it with Z""
@Suever Hey, you have an "image preview" pop up!
It's full of surprises :-)
21:23
Hahaha
It's the small things
So in your example how would I see a 12x12 image? Meaning 12 screen pixels, is that possible?
Alright well I've gotta run but feel free to post more feedback. If I don't respond to something mention it again! Once I clean up this code, I'll open source the repo and we can discuss stuff there if that's easier
Oh yea, right click when you see the preview and say "view image in new tab"
That should work. You're on windows though (Chrome?) so I'm not sure if the options are different. Regardless the image is pushed to the browser as literal pixels
@Suever It doesn't seem to work here (Chrome on Windows 7). I get an image with pixels scaled up, more or less like in the preview
Hey, this is funny! :-)
http://matl.suever.net/#?code=32hO511-3-12-16-32O6-64-6O25%2013-38%2017%2040%2070-511Nq%24hYs10H%24Bt!P!hi1%24lX*Q)20%3A%220wYctcD.1Y.Xx&inputs='%23'%0A%5B1%202%5D&version=18.3.0
Escaping Z" as Z"" works
We should have a small help for the online compiler telling all these things
Again, amazing job!!

« first day (49 days earlier)      last day (3154 days later) »