1) I just wanted the console, not the HTML output pane.
So to "maximize" the console pane, I clicked to close the HTML output pane.
Turns out that closed both panes.
Or, rather, they were 2 parts of the same pane. Fine.
2) The real issue here is that I now cannot find any way to re-open the console / html output pane(s).
And there is no "Run" button. Not that that matters, if I cannot see the results ;-)
EDIT/UPDATE:
Ok, now I found the "Preview" button, and that "Preview" supposed to toggle the console/html pane??. But it's not obvious because:
1) it's next to the login and sign-up buttons.
Definitely not looking there. My brain knows that is Login location and immediately looks there for that type of function. Only. Brain ignores that location otherwise. That's website-level and account-leven stuff. Nothing to do with the code I'm running, or page-level, or transient level settings or visual elements visibility for a page load level stuff. Not even in the ballpark.
2) Preview is not the word I'm looking for. Who says that when running code. I may want to "preview" markdown formatted text, but "preview coded" doesn't even make sense. "View Output", "Run" "console" are related terms. "preview" is a formatting thing, not a "running" thing.
3) I'm looking at the same icons in the same location to the ones I used to close the console/html pane. They seem to be the SAME icons, but there isn't one to re-open. I'm looking there to re-open the panes. Evidently, "these icons are not the ones I think they are. They look the same. They are in the same location. They are in the space previously representing the console/html pane.
But they now belong to the code editing pane.
Once I Finally figured this out, I can see why. But only in hindsight.
As a UI, it's not obvious. It's just not how our location memory works. And there is no other visual marker or animation that triggers our minds to realize the other panes icons have moved over.
And even then, we look amongst those icons for a button to re-open the other pane.
I get trying to save screen real estate. And I get l the object oriented nature that put the icons for one pane now in the location previously occupied by the same icons of the other pane.
But animal's brains, and people's brains, are wired to record information to location.
Better to have a narrow button to the right of the screen to re-open the pane that was just closed, if that pane was on the right, and vice-versa to the left if the pane was on the left.
"Preview" has nothing to do with Login. On ANY website. They are completely unrelated. And the SIZE difference for that button (as well as its name) doesn't fit with the other related buttons. It'd be more natural to place this button at the left, with New, Save, Fork, or with the settings. That's the next location I went looking in order to Open the console/html output panes, or to find a Run button.
Finally, using "Refresh" to mean "Run" is terrible. It redefines both the symbol, and the definition of the word. These terms and symbols mean something very specific for decades across all platforms. This is not it. More commonly is the "Play" arrow button.
I honestly thought there was NO way to re-run the code without making an edit.
I actually thought "refresh" was akin to Clearing the window. Which is usually indicated by a (/) symbol, or even a delete symbol.
Clear Window is a missing item that I kept looking for. Yes, I often want to clear output Before re-running. And I want to do that without actually re-running at that moment.
These are the standards already defined and present in all browsers. Best to use the standard:
1) prevents context switching anytime one switches back to any browser, and also whenever one uses this tool. 2) prevents a learning curve when using this tool for the first several times. 3) don't re-invent the wheel on little, widely known and understood stuff like this.
Aside from these little UI confusing missteps, the Alpha version is Great - much better than the old version.
1) I just wanted the console, not the HTML output pane.
So to "maximize" the console pane, I clicked to close the HTML output pane.
Turns out that closed both panes.
Or, rather, they were 2 parts of the same pane. Fine.
2) The real issue here is that I now cannot find any way to re-open the console / html output pane(s).
And there is no "Run" button. Not that that matters, if I cannot see the results ;-)
EDIT/UPDATE: Ok, now I found the "Preview" button, and that "Preview" supposed to toggle the console/html pane??. But it's not obvious because: 1) it's next to the login and sign-up buttons.
Definitely not looking there. My brain knows that is Login location and immediately looks there for that type of function. Only. Brain ignores that location otherwise. That's website-level and account-leven stuff. Nothing to do with the code I'm running, or page-level, or transient level settings or visual elements visibility for a page load level stuff. Not even in the ballpark.
2) Preview is not the word I'm looking for. Who says that when running code. I may want to "preview" markdown formatted text, but "preview coded" doesn't even make sense. "View Output", "Run" "console" are related terms. "preview" is a formatting thing, not a "running" thing.
3) I'm looking at the same icons in the same location to the ones I used to close the console/html pane. They seem to be the SAME icons, but there isn't one to re-open. I'm looking there to re-open the panes. Evidently, "these icons are not the ones I think they are. They look the same. They are in the same location. They are in the space previously representing the console/html pane.
But they now belong to the code editing pane.
Once I Finally figured this out, I can see why. But only in hindsight.
As a UI, it's not obvious. It's just not how our location memory works. And there is no other visual marker or animation that triggers our minds to realize the other panes icons have moved over.
And even then, we look amongst those icons for a button to re-open the other pane.
I get trying to save screen real estate. And I get l the object oriented nature that put the icons for one pane now in the location previously occupied by the same icons of the other pane.
But animal's brains, and people's brains, are wired to record information to location.
Better to have a narrow button to the right of the screen to re-open the pane that was just closed, if that pane was on the right, and vice-versa to the left if the pane was on the left.
"Preview" has nothing to do with Login. On ANY website. They are completely unrelated. And the SIZE difference for that button (as well as its name) doesn't fit with the other related buttons. It'd be more natural to place this button at the left, with New, Save, Fork, or with the settings. That's the next location I went looking in order to Open the console/html output panes, or to find a Run button.
Finally, using "Refresh" to mean "Run" is terrible. It redefines both the symbol, and the definition of the word. These terms and symbols mean something very specific for decades across all platforms. This is not it. More commonly is the "Play" arrow button.
I honestly thought there was NO way to re-run the code without making an edit.
I actually thought "refresh" was akin to Clearing the window. Which is usually indicated by a (/) symbol, or even a delete symbol.
Clear Window is a missing item that I kept looking for. Yes, I often want to clear output Before re-running. And I want to do that without actually re-running at that moment.
These are the standards already defined and present in all browsers. Best to use the standard:
1) prevents context switching anytime one switches back to any browser, and also whenever one uses this tool. 2) prevents a learning curve when using this tool for the first several times. 3) don't re-invent the wheel on little, widely known and understood stuff like this.
Aside from these little UI confusing missteps, the Alpha version is Great - much better than the old version.