| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
|
|
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.
|
|
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.
|
|
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`
|
|
|
|
|
