| Age | Commit message (Collapse) | Author |
|---|
|
`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.
|
|
|
|
Requires new `executed` signal in `CommandInput` component to correctly trigger the state change.
|
|
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.
|
|
|
|
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.
|
