Hello all, I wanted to start a thread to discuss suggestions for how Stinger OS is being designed. This discussion shouldn't be read as a complaint, this is an Alpha release after all, but it would be good to get this discussion going in the early stages as making the changes later on would likely result in a lot of extra effort that could be avoided. Playing through Alpha 0.4, there is a big stress on using multiple workspaces to run multiple tasks. This appeals to my power-user mentality and I tried to embrace it but I found I was slowed down by how I was forced to actually run tasks. For example, it's very common to run to run this series of commands at the start of a mission: search for hosts, portscan, fingerprint, and then foxacid. There's two ways you can do this: 1. Click through the menus to get to each tool 2. Type in the name of the command with all appropriate parameters into the current terminal window Both of these has its own issues. I'll start with case 2. This is very familiar command line interface behaviour but there are two things missing: a standard shell (terminal) and keyboard caret control. Since I always need to type in the commands, I'd like to be able to quickly open a blank terminal. I think this should be a main menu button; one click = terminal. This also presents in a different way in that each different command I enter automatically opens a new terminal. For the frequent command chain I mentioned above, that's four separate windows that are less useful than an extended terminal scroll history. As well, there's too many independent terminals, they should all share the command history and opening a new one should be optional, perhaps by prefixing a command like "term" before the actual command. All in the same terminal: portscan rosenews.com <- portscan results shown here fingerprint rosenews.com -p 80 <- fingerprint results shown here First terminal: portscan rosenews.com <- portscan results shown here term fingerprint rosenews.com -p 80 Second terminal opens: <- fingerprint results shown here "term" would also be a useful command to open and switch to a new terminal in the same workspace. That ties into keyboard caret control. Inevitably, I'm going to press enter on a mistyped command. Right now, I can press up to bring back previous commands but I can't edit the line with the keyboard, I need to switch to clicking with the mouse in the spot I need to change and then switch back to the keyboard. I can see the argument that this is faster but I'd like the option to stay on the keyboard. The issues concerning case 2 really connect to case 1, as the process of clicking through the menus to access extremely frequently used tools is cumbersome and, in the end, doesn't save you from having to type the commands again. Clicking a tools menu item provides a useful description of it's use but, after a couple of missions, I've already memorized the names and parameters for the commands. I suggest two ways to resolve this: Turn that menu into a series of manual entries so you can have a new window open with the usage for the command or give the commands their own inner shells. Here's an example of what I mean by inner shells: A: csh> nslookup google.ca Server: 188.8.131.52 Address: 184.108.40.206#53 Non-authoritative answer: Name: google.ca Address: 220.127.116.11 B: csh> nslookup > google.ca Server: 18.104.22.168 Address: 22.214.171.124#53 Non-authoritative answer: Name: google.ca Address: 126.96.36.199 > ^C In A, I typed the command and parameters together and got the response back, same as in Alpha 0.4. In B, I typed just the command name, pressed enter, then got the commands inner shell where I only needed to type the parameters. This is especially useful when you want to use the same command over and over but don't want to have to retype the command name (or press up). I'm eager for others' insights into these and other UI design choices.