aboutsummaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)Author
2015-08-31Adapt focus and input scoping to respect history viewerAdrian Kummerlaender
2015-08-30Prevent visual selection change on `kill` commandAdrian Kummerlaender
`TerminalItem`'s `reset` member method wrongly performed a visual selection change which led to inconsistency when calling `kill` on a non-selected index. Visual selection update is now performed on history view instantiation.
2015-08-30Add launcher program and argument to configurationAdrian Kummerlaender
2015-08-30Make command output selectable and rich by defaultAdrian Kummerlaender
2015-08-30Make text in history view selectableAdrian Kummerlaender
2015-08-30Only enter insert mode after history instatiation on last itemAdrian Kummerlaender
2015-08-30Defer command interpretation to `sh`Adrian Kummerlaender
Otherwise one can not easily enter more complex shell commands such as pipe chains and so on. The goal of _MetaTerm_ is not to implement a new shell language but to facilitate existing ones which is why this is best deferred to an existing application.
2015-08-30Ease consecutive non-interactive executions and fix mode changeAdrian Kummerlaender
If a non-interactive applications terminates the next item is automatically selected in insert mode as to make the behaviour in this context more simmilar to normal shells. Normal mode has to be entered explicitly for the highlighting to update on `HistoryViewer` instantiation.
2015-08-29Automatically destroy terminal when killed and display historyAdrian Kummerlaender
Child processes of _MetaTerm_ may be terminated using other ways that the integrated kill command. Automatic terminal widget destruction in such a event prevents the user from viewing the output of non-interactive applications. This requires _MetaTerm_ to display the application's output after it was terminated. This requirement is implemented via the new `HistoryViewer` widget that is instantiated after the terminal widget instance has been destroyed.
2015-08-22Use window background as `TerminalItem` selection text colorAdrian Kummerlaender
2015-08-22Replaced unnecessary `eval` calls in settings getter and setterAdrian Kummerlaender
2015-08-22Hide category property in `set` key suggestionsAdrian Kummerlaender
2015-08-21Implement automatic key suggestion in `set` commandAdrian Kummerlaender
2015-08-21Improve `exec` output type handlingAdrian Kummerlaender
i.e. serialize objects to JSON.
2015-08-21Add `q` command to close _MetaTerm_ in command modeAdrian Kummerlaender
2015-08-19Improve handling of non-existing properties in `set`Adrian Kummerlaender
2015-08-19Prevent trailing whitespace from resetting configuration valuesAdrian Kummerlaender
Trailing whitespace was falsely recognized as a separate argument and as such led to resetting configuration values without obvious cause.
2015-08-19Add `set` command to ease configuration changesAdrian Kummerlaender
2015-08-19Extract all settings into `SettingsHandler` objectAdrian Kummerlaender
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.
2015-08-15Expose component settings as propertiesAdrian Kummerlaender
Otherwise they are not accessible to JS commands, i.e. they can not be changed in command mode.
2015-08-15Restructure QML and JS sourcesAdrian Kummerlaender
`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.