aboutsummaryrefslogtreecommitdiff
path: root/src/command
AgeCommit message (Collapse)Author
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.