| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Trailing whitespace was falsely recognized as a separate argument and as such led to resetting configuration values without obvious cause.
|
|
|
|
This enables the user to straight forwardly change all application settings via command mode.
During the implementation of this change I discovered that the way I was passing around `StateHandler` and `SettingsHandler` instances using properties was unnecessary. If all object instances are created in a common hierarchy they can access each other by their `id` property - i.e. `settings` and `mode` are available to the whole application without property trickery.
|
|
Otherwise they are not accessible to JS commands, i.e. they can not be changed in command mode.
|
|
`list` holds the components of the central list UI element.
`command` holds the UI and implementation parts of the command mode.
`widget` holds more or less general purpose elements that may also be of use in other circumstances.
|
|
|
|
|
|
This suggested adding an `iterate` helper method to `TerminalList` as well as line break logic to the command output log.
|
|
While `color` would obviously be the correct type to store a color value it is serialized as a `QVariant` value which is not easily changeable by the user.
This requirement is satisfied by `string` and as such this type is - at this point in time - a superior replacement of `color`.
Should the QML settings module be changed to serialize color values in a human readable fashion these types should be changed back to their formally correct value.
|
|
|
|
|
|
`output` text item reference is passed to all command implementations.
|
|
|
|
Requires new `executed` signal in `CommandInput` component to correctly trigger the state change.
|
|
Requires type dependent conversion in TerminaList's `selectItem` method as values passed through `eval` are of type `QJSValue` which is not implicitly convertible to Int.
|
|
Moved command implementation into separate ressource.
Commands are plain JavaScript functions in this separate ressource and as such callable via a simple call to `eval`.
Introduced the concept of a command prefix to enable implementation of e.g. a search command analogously to _vim_.
|
|
|
|
Exposes access to the application via JavaScript to the user.
This will enable easy configuration changes as well as make more complex commands possible.
All JavaScript entered in command mode is evaluated at the application root.
|
|
This was done to reflect that they concern the whole insert mode and don't only control the terminal focus.
|
|
|
|
|
|
This provides further visual feedback to the user that she has hit a limit.
Reduced ease out animation duration to match duration of the highligher focus / defocus animations.
|
|
This further discourages flickering during continuous terminal resize operations.
Overlay is now only enabled for resize operations after the terminal instantiation.
|
|
|
|
This is required as the default white on black may not fit e.g. bright color schemes.
|
|
The animation is now restarted on every height and width change event.
In practice this leads to the overlay being displayed continuously during multiline resize operations but only briefly on single line resize operations.
|
|
Needs further fiddling concerning the animation curve and display duration
|
|
|
|
Otherwise each runtime change of a property leads to storing the new value to disk which we don't want - setting changes should be explicit and visible as such.
|
|
|
|
|
|
Pressing `d` in normal mode causes the current embedded terminal to be destroyed and the containing terminal item to be reset into its initial state.
This allows for much more flexible usage of _MetaTerm_.
To prevent unnecessary terminal item instantiations the `onExecuted` signal was extended to provide a `index` argument containing the sender terminal's index.
|
|
|
|
|
|
`ApplicationWindow` doesn't offer QML State support but as this functionality lends itself quite well to the _Vim like_ UI mode paradigm it was moved into a `Item` based component.
|
|
The background color is set accordingly to the color scheme by the widget itself.
|
|
Terminal width is now automatically adjusted to use all available space.
Commands to control horizontal terminal height were removed correspondingly.
|
|
|
|
|
|
Makes it easier to access the `QMLTermWidget` instance from both outside and inside `TerminalItem`
|
|
|
|
|
|
List expansion only happens when a new item is added and as such the `onHeightChanged` signal allows for bringing the new item into view.
This work around is necessary as all my attempts to scroll with the output by e.g. using the `onExecuted` signal of `TerminalItem` failed.
Reasons for this include both the async nature of JavaScript which makes it inconvenient to enforce execution of a function at exactly the right time, as well as the height value of `terminalList` seemingly not being updated instantly.
|
|
They are active in normal mode and move the focus to the last respectively first element of the list.
|
|
|
|
|
|
Normal mode allows for selecting the a terminal or newline text input.
Insert mode sets the keyboard focus to the currently selected item.
This transforms _MetaTerm_ into a fully keyboard driven application.
|
|
MetaTerm is a meta terminal in the sense that it allows launching multiple terminal shells and applications in a unified interface that is in itself reminiscent of a terminal shell.
|
