Simple Console is nice clean command-line interface for the web. Check out the demo!
-
Light and dark styles
-
Easy rich HTML output
-
Command history accessible with up/down arrow keys, saved to
localStorage -
Command history menu for mobile accessibility
-
Doesn't create a duplicate history entry if you re-enter the last command
-
Lets you delete history entries with Shift+Delete
-
Includes
ariaattributes (although the accessibility could still use some work!)
Download simple-console.css and simple-console.js,
and include in the <head>:
<link rel="stylesheet" href="simple-console.css">and anywhere before you use SimpleConsole but probably in the <body>:
<script src="simple-console.js"></script>var con = new SimpleConsole({
placeholder: "Enter JavaScript",
handleCommand: function(command){
try {
con.log(eval(command));
} catch(error) {
con.error(error);
}
},
autofocus: true, // if the console is to be the primary interface of the page
storageID: "app-console"
});
// add the console to the page
document.body.appendChild(con.element);
// show any uncaught errors
con.handleUncaughtErrors();You should probably also include a charset and viewport like in the demo.
To make the console take up the entire page, use:
html,
body {
height: 100%;
margin: 0;
display: flex;
flex: 1;
}The dark styles take effect when the console element or any parent contains the class dark.
You could add a theme switcher like so:
var toggleDarkMode = function() {
if (console.element.classList.contains("dark")) {
console.element.classList.remove("dark");
} else {
console.element.classList.add("dark");
}
};
var button = console.addButton(toggleDarkMode);
button.textContent = "◐";
button.setAttribute("title", "Toggle dark theme");
button.setAttribute("aria-label", "Toggle dark theme");Creates a console instance.
Note: The SimpleConsole object is referred to as console below, but you should probably give it a different name so it doesn't conflict with the global console object.
options.handleCommand(command) is called when the user hits Enter.
You can handle the input however you want.
It's recommended that you catch errors and log them with console.error.
Other logging methods are documented below.
options.outputOnly specifies that there should be no input.
You must specify either outputOnly or handleCommand.
options.placeholder is strongly recommended especially with the default input styling as there is very little visual indication of the input (when it's not focused).
options.autofocus should be used within an application where the console is the primary interface.
options.storageID should be used to separate the command history of different consoles.
It's used as a localStorage key prefix.
You must use this to add the console to the page,
e.g. document.body.appendChild(console.element)
The console's <input> element.
Can be used to add controls/widgets
i.e. console.input.parentElement.appendChild(widget)
Adds a button to the right of the console's input area and returns the button element.
action should be a function.
Adds a button with a popup to the right of the console's input area and returns the button element.
updatePopup(popupElement) should update the contents of the popup.
Use addPopupMenuButton instead if the popup's contents are a standard menu.
Adds a button with a standard popup menu to the right of the console's input area and returns the button element.
getItems() should return an array of items, with each item either of the form {label, action} or {type: "divider"}.
Sets up a window.onerror event listener which logs any uncaught errors to the console.
Logs the given text or element to the console.
Logs the given HTML to the console.
Logs the given error message (or element) to the console.
Logs the given warning message (or element) to the console.
Logs the given info message (or element) to the console.
Logs the given success message (or element) to the console.
Returns the last logged entry as an HTMLDivElement for further manipulation.
Clears the console.
-
Support multiple arguments to
log,warnetc. -
Distinguish error/success/warning messages for screen readers (maybe with
cue-beforefrom the CSS Speech Module) -
Solarized and retro themes
-
Position menus better?
-
Rename project because "simple-console" is taken on npm. I'm thinking "cute-console"...
-
This seems like it would be an ideal candidate for a Web Component
-
Multiline input (i.e.
textarea) -
Autocomplete (
aria-autocomplete="inline") -
Syntax highlighting
-
Should probably just let you use your own input component
-
Fix duplicate reading of
aria-labelandplaceholderby some screen readers -
Fix input styling in Firefox with
font: inheritand something else to make stuff line up perfectly
The MIT License (MIT) Copyright (c) 2016 Isaiah Odhner
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.