The most popular versions among HyperTerminal users are 7.0, 6.3 and 6.2. The latest version of HyperTerminal is supported on PCs running Windows XP/7/8/10, 32-bit. The program's installer is commonly called HyperTerminal.exe, UNWISE32.EXE, Terminal.exe, RunDll32.exe or Project1.exe etc. The actual developer of the software is Hilgraeve, Inc. Hyper Terminal Preferences According to the dev team’s goal statement, they started the Hyper project in order to create a, a beautiful and extensible experience for command-line interface users, built on open web standards. HyperTerminal Private Edition 7.0 Free Download Secure HyperTerminal Private Edition Download Options. HyperTerminal Private Edition 7.0 (External server) Popular Downloads. Macromedia Flash 8 8.0 Macromedia Flash 8 Professional. Tally.ERP 9 3.7 Tally is a.
Driver InstallationInsert the iLoad Digital USB Driver CD OR the LoadVUE or LoadVUE Lite CD into your computer's drive. If you have downloaded the driver files from our web site onto a location in your hard disk, substitute that location instead of the CD drive in the instructions below. Drivers for Windows XP and Windows Vista are available here. If you have purchased LoadVUE or LoadVUE Lite software with your iLoad Digital USB load cell, please ensure that you install the drivers as described in this document before you install the LoadVUE software. Also note that the screen shots in this document are for Windows XP, but the process is the same with Windows Vista although the appearance of screens is different. Note: The iLoad series load cells are intended for use with an NRTL approved device such as a computer or regulated power supply. Plug in your iLoad Digital USB load cell into an available USB port on your Windows computer. The New Hardware Wizard window will come up in a few seconds. Select the option for 'No, not this time' and click Next. On the next screen select the option for 'Install the software automatically' option and click Next. Your computer should scan the CD to find appropriate drivers for the load cell. On the next dialog box click Continue Anyway. Windows installs the driver for your iLoad Digital USB load cell. Click Finish. The load cell will appear as a COM port to Windows whenever you plug it in to the same USB port on your computer. If you use a different physical USB port, you may need to go through this procedure again to associate a COM port with that USB port. However, you will usually not have to insert the CD again. To verify the COM port number that has been assigned to the load cell, open the Hardware Device Manager. You can do so by going to the Control Panel in Windows and double-clicking on System. On the System dialog box click on the Hardware tab and select the Device Manager button. When your iLoad Digital USB load cells is connected and correctly installed, you should see a COM port assigned to it as shown highlighted in the following screen shot (next page). If you have more COM ports than you have load cells connected, you can double-click on the entry for a COM port. The ports associated with iLoad Digital USB load cells will indicate that they have a Loadstar Sensors driver as shown below. You are now ready to start using your iLoad Digital USB load cell. Hyperterminal OperationIn Windows XP, launch the Hyperterminal program. Start..All Programs..Accessories..Communications..Hyperterminal Note: Windows Vista does not include a terminal client. However, free terminal client software like Teraterm is available. Set up a new connection to connect to the iLoad Digital USB load cell's COM port. In the 'Connect To' window, select the appropriate COM port. In the 'Port Settings' dialog box, accept the defaults. The baud rate is not applicable to the iLoad USB load cells. Click OK to accept the settings. Then click 'Enter' a few times. You should see the load cell respond with an 'A'. Type 'O0W1' and hit . The load cell will respond with the current load on the load cell in millipounds. In the figure below the load is 2.853 pounds. Type 'CT0' to tare the load cell. This will zero the load (all further readings will subtract the load sensed at this point.) Type 'O0W0' to output the load continuously. Hitting at any time will stop outputting the readings. The iLoad Digital USB load cell can be used through LoadVUE or LoadVUE Lite software from Loadstar Sensors. It can also be used directly as a COM port using any terminal emulation software such as HyperTerminal that is included with Windows XP. To set up Hyperterminal or other terminal emulation program to communicate with the load cell, select the appropriate COM port in the program and connect. Once connected, a few simple commands are all that are needed to operate the load cell:
Since the iLoad Digital USB Load cells present themselves to Windows as COM ports, it is very easy to write your own program to read the load cells loads. Simply open the COM port from your application and send the string O0W1. Then read the returned string back in millipounds. We recommend the following steps:
If callbacks (or events) are available, it is preferable to use them instead of polling the load cells in step 7 above. This way Windows will inform the application that there is data to be read. Examples for Labview and Matlab are available on our support pages. | |||||||||||||
If you cannot find what you're looking for or have any other questions please call or This email address is being protected from spambots. You need JavaScript enabled to view it. us and we will be glad to be of further assistance. |
Installation
latest version: 3.0.264-bit | |
macOS (.app) | 3.0.2 |
Windows (.exe) | 3.0.2 |
Debian (.deb) | 3.0.2 |
Fedora (.rpm) | 3.0.2 |
Other Linux distros (.AppImage) | 3.0.2 |
Project Goals
The goal of the project is to create a beautiful and extensible experience for command-line interface users, built on open web standards. In the beginning, our focus will be primarily around speed, stability and the development of the correct API for extension authors.
In the future, we anticipate the community will come up with innovative additions to enhance what could be the simplest, most powerful and well-tested interface for productivity.
Extensions
Extensions are available on npm. We encourage everyone to include
hyper
in the keywords
field in package.json
.Then edit
.hyper.js
and add it to plugins
Hyper
will show a notification when your modules are installed to .hyper_plugins
.Hyperterminal For Windows 7
Keymaps
All command keys can be changed. In order to change them, edit
.hyper.js
and add your desired change to keymaps
. Then Hyper will change the default with your custom change.
Example:
'window:devtools': 'Cmd+Alt+O'
Default keymaps:
Hyperterminal Download
Configuration
Config location
macOS | ~/Library/Application Support/Hyper/.hyper.js |
Windows | $Env:AppData/Hyper/.hyper.js |
Linux | ~/.config/Hyper/.hyper.js |
Note: config at
~/.hyper.js
still supported, but will be ignored, if config in application directory present. Otherwise it will be moved to the application directory at first run.The
config
object seen above in.hyper.js
admits the followingProperty | Default | Description |
updateChannel | 'stable' | The update channel to receive updates from |
fontSize | 12 | The default size in pixels for the terminal |
fontFamily | 'Menlo, DejaVu Sans Mono, Lucida Console, monospace' | The font family to use with optional fallbacks |
uiFontFamily | '-apple-system, BlinkMacSystemFont, Segoe UI, Roboto, ..' | The font family to use for the UI with optional fallbacks |
fontWeight | 'normal' | The default font weight: 'normal' or 'bold' |
fontWeightBold | 'bold' | The font weight for bold characters: 'normal' or 'bold' |
cursorColor | 'rgba(248,28,229,0.8)' | The color of the caret in the terminal |
cursorAccentColor | '#000' | The text color under BLOCK cursor |
cursorShape | 'BLOCK' | The shape of the caret in the terminal. Available options are: 'BEAM', 'UNDERLINE', 'BLOCK' |
cursorBlink | 'false' | If true, cursor will blink |
foregroundColor | '#fff' | The color of the main text of the terminal |
backgroundColor | '#000' | The color and opacity of the window and main terminal background |
selectionColor | 'rgba(248,28,229,0.3)' | The background color/opacity of the text selection in terminal |
borderColor | '#333' | The color of the main window border and tab bar |
css | ' | Custom CSS to include in the main window |
padding | '12px 14px' | CSS padding values for the space around each term |
colors | { black: '#000000', red: '#ff0000', .. } | A list of overrides for the color palette. The names of the keys represent the 'ANSI 16', which can all be seenin the default config. |
shell | ' | A path to a custom shell to run when Hyper starts a new session |
shellArgs | '['--login']' | An array of shell arguments |
env | {} | An object of environment variables to set before launching shell |
windowSize | [540, 380] | The default width/height in pixels of a new window |
scrollback | 1000 | The number of rows to be persisted in terminal buffer for scrolling |
copyOnSelect | false | If true, selected text will automatically be copied to the clipboard |
quickEdit | false | If true, on right click selected text will be copied or pasted if no selection is present (true by default on Windows) |
defaultSSHApp | true | If true, Hyper will be set as the default protocol client for SSH |
modifierKeys | {altIsMeta: false} | Change the behaviour of modifier keys to act as meta key |
showHamburgerMenu | true on Linux/Windows, false on macOS | Change the visibility of the hamburger menu. Available options are: true, false |
showWindowControls | ' | Change the position/visibility of the window controls. Available options are: true, false, 'left' |
Extensions API
Extensions are universal Node.js modules loaded by both Electron and the renderer process.
The extension system is designed around composition of the APIs we use to build the terminal:
React
components andRedux
actions.Instead of exposing a custom API method or parameter for every possible customization point, we allow you to intercept and compose every bit of functionality!
The only knowledge that is therefore required to successfully extend
Hyper
is that of its underlying open source libraries.You can find additional details about plugin developmentin the Hyper repository.
Your module has to expose at least one of these methods:
Method | Invoked from | Description | ||||||
onApp | Electron | Invoked when the app first loads. If a plugin reloads, it's invoked again with the existing app. Parameters:
| ||||||
onWindow | Electron | Invoked when each window is created. If a plugin reloads, it's invoked again with the existing windows. Parameters:
| ||||||
onUnload | Electron | Invoked when a plugin is removed by the user. Parameters:
| ||||||
decorateConfig | Electron / Renderer | v0.5.0+. Allows you to decorate the user's configuration. Useful for themeing or custom parameters for your plugin. Parameters: Adobe photoshop elements 2020 18 1.
| ||||||
decorateEnv | Electron | v0.7.0+. Allows you to decorate the user's environment by returning a modified environment object. Parameters:
| ||||||
decorateMenu | Electron | Invoked with the Electron's Menu template. If a plugin reloads, it's called again and the menu is refreshed.Parameters:
| ||||||
decorateBrowserOptions | Electron | Allows you to decorate Electron's BrowserWindow options when a new window is created.Parameters:
| ||||||
onRendererWindow | Renderer | Invoked when a plugin is first loaded or subsequently reloaded in each window. Parameters:
| ||||||
middleware | Renderer | A custom Redux middleware that can intercept any action. Subsequently we invoke the thunk middleware, which means your middleware cannext thunks. | ||||||
reduceUI reduceSessions reduceTermGroups | Renderer | A custom reducer for the ui ,sessions or termgroups state shape.
| ||||||
getTabsProps | Renderer | Passes down props from <Tabs> to the <Header> component. Must return the composed props object.
| ||||||
getTabProps | Renderer | Passes down props from <Tab> to the <Tabs> component. Must return the composed props object.
| ||||||
getTermGroupProps | Renderer | Passes down props from <Terms> to the <TermGroup> component. Must return the composed props object.
| ||||||
getTermProps | Renderer | Passes down props from <TermGroup> to the <Term> component. Must return the composed props object.
| ||||||
mapHyperState mapTermsState mapHeaderState mapNotificationsState | Renderer | A custom mapper for the state properties thatcontainer componentsreceive. Note that for children components to get these properties, you have to pass them down using the corresponding methods (like getTermProps ).Must return an extended object of the map passed.
| ||||||
mapHyperDispatch mapTermsDispatch mapHeaderDispatch mapNotificationsDispatch | Renderer | A custom mapper for the dispatch properties. Must return an extended object of the map passed.
| ||||||
decorateHyper decorateNotifications decorateNotification decorateHeader decorateTabs decorateTab decorateTerms decorateTermGroup decorateSplitPane decorateTerm | Renderer | Invoked with the React Component to decorate. Must return a Higher Order Component.Parameters:
|
Module loading
The user can hot-load and hot-reload plugins by pressing Command + R (refresh). Please strive to make plugins that don't require a complete restart of the application to work.
Notice
Plugins affecting the `BrowserWindow` will the effect on new windows after hot-reload.
In the future we might do this automatically.
When developing, you can add your plugin to
.hyper_plugins/local
and then specify it under the localPlugins
array in.hyper.js
. We load new plugins:- Periodically (every few hours)
- When changes are made to the configuration file (
plugins
orlocalPlugins
) - When the user clicks Plugins > Update all now
The process of reloading involves
- Running
npm prune
andnpm install
in.hyper_plugins
. - Pruning the
require.cache
in both electron and the renderer process - Invoking
on*
methods on the existing instances and re-rendering components with the fresh decorations in place.
Plugins location
macOS | ~/Library/Application Support/Hyper/.hyper_plugins |
Windows | $Env:AppData/Hyper/.hyper_plugins |
Linux | ~/.config/Hyper/.hyper_plugins |
Note: plugins at
~/.hyper_plugins
still supported, but will be ignored, if plugins in application directory present. Otherwise they will be moved to the application directory at first run.Note: on the main process, plugins are registered as soon as possible (we fire
onLoad
). On the browser, it's up to the user to trigger their load by pressing command+R. We put the user in control of the loading in this way to prevent them from losing critical work by extensions that reset state or don't preserve it correctly.Decorating components
We give you the ability to provide a higher order component for every piece of the
Its structure is as follows:
Hyper
UI.Its structure is as follows:
All the
decorate*
methods receive the following references in an object passed as the second parameter:React | The entire React namespace. |
notify | A helper function that shows a desktop notification. The first parameter is the title, the second is the optional body of the notification, and the third is another optional parameter which can be used to log details to the development console. To pass these details, simply provide and object with an error property containing the information to log. |
Notification | The Notification component in case you want to re-use it. |
All the components accept the following two properties to extend their markup:
customChildren | An array of Element or a singleElement to insert at the bottom of the component. |
customChildrenBefore | The same as the above property, but inserted as the first child element(s) of the component. |
Your higher order component can supply a
onDecorated
property to the decorated component to get a reference to its instance.Your Term higher order component can supply an
onCursorMove
handler property that be called when cursor has moved with an object parameter representing its relative position to Term origin:x | Horizontal position in pixels |
y | Vertical position in pixels |
width | Cursor width in pixels |
height | Cursor height in pixels |
col | Horizontal position in columns |
row | Vertical position in rows |
We encourage you to maintain compatibility with other decorators. Since many can be set, don't assume that yours is the only one.
For example, if you're passing children, compose potential existing values:
Or if you use
onDecorated
property![Hyper Terminal Hyper Terminal](https://www.researchgate.net/profile/Frank_Fitzek/publication/227943078/figure/fig6/AS:668617825865759@1536422320743/A-screenshot-of-the-Windows-Hyper-Terminal-that-allows-to-send-and-receiving-data-to-the.jpg)
Actions and Effects
All theRedux actionsare available for you to handle through your middleware and reducers. For an example, refer to the Hyperpowerreference plugin.
Side effects occur in two fundamental forms:
- Some actions dispatch other actions based on state.
- Some actions do async work by communicating over the RPC channel to the main process
In all cases, the side effect is passed as the
effect
key in the action and later handled by our middleware.This means that you can override, compose or completely eliminate effects! In other words, this is how you can change the default functionality or behavior of the app.
As an example, consider the action we use to increase the font size when you press
Command+=
:The underlying terminal
Hyper
achieves a lot of its speed and functionality thanks to the power ofxterm.jsAdditional APIs
The Electron
app
objects are extended with the following properties:config | An Object with the config block from.hyper.js . |
plugins | An Object with helpers for plugins. |
getWindows | A Function that returns an Set of all the open windows. |
createWindow | A Function that will create a new window. Accepts an optional callback that will be passed as the new window's init callback. |
Electron
BrowserWindow
objects are extended with the following parameters:rpc | An EventEmitter that allows for communication with the window process. |
sessions | A Map of Session objects which hold the communication with each term's pty. |
Renderer windows are similarly extended with:
rpc | An EventEmitter that allows for communication with the window process. |
store | The Redux Store object. This allows access todispatch actions or read the global state withgetState . |
The
rpc
object is symmetrical between browser and renderer process. The API is the same as Node.js, with the exception that it only admits a single object as its parameters only:Example theme: Hyperyellow
The following extension simply alters the config to add CSS and yellow colors! Here's thecode.
Themes are simply plugins! Only one hook,
decorateConfig
is needed:I grabbed the class names by inspecting the term with Devtools, which you can trigger from
View -> Toggle Developer Tools
. When you do so, notice that some classes are automatically generated and followed by a random nonce (e.g.: term_13hv8io
). Ignore those: they change with every new window!Notice the emphasis on playing nice with other extensions. Specifically, we create a new object, extend only the keys we are interested in, and we compose the CSS to preserve the user's setting and that of other authors':
Hyper Terminals
Example extension: Hyperpower
The following extension renders particles as the caret moves:
Let's walk throughits code.
First, we intercept the Redux action
First, we intercept the Redux action
SESSION_ADD_DATA
. You can find the full list of actionsin the repository.Hyper Terminal Ssh
Notice that we don't re-dispatch the action, which means we never render the output of the command to the terminal. Instead, we dispatch an action of our own, which we grab in the
uiReducer
and later map:We then want to decorate the
<Term>
component so that we can access the underlying caret.However,
<Term>
is not a container that we can map props to. So we use getTermProps
to pass the property further down:The extension thenreturnsa higher order component to wrap
<Term>
. Notice we pass the onDecorated
property to access the base Term component and its DOM ref, and theonCursorMove
property to use Hyper cursor API: