Azurency / Azurency/CQUI_Community-Edition
New Feature: Omnibar
- Dominant language
- Lua
- Stars
- 397
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
**Issue by [chaorace](https://github.com/chaorace)**
_Saturday Jan 07, 2017 at 07:17 GMT_
_Originally opened as https://github.com/CQUI-Org/cqui/issues/225_
----
So, if you've used an editor like Sublime or an IDE like IntelliJ, you've probably encountered a bar like this:

It's a bar which contains all of the available commands for the application and allows you to dynamically search for them. I'd like to add something like that to CQUI, because I think there's lots of potential for dramatically improving UI speed for powerusers this way.
Example: open omnibar, start typing city name, tab to autocomplete, type "pro", tab to autocomplete "produce", type "hor", tab to autocomplete "horseman", enter to send a new horseman entry to the start of the selected city queue.
The possibilities are basically endless here, so I definitely think it's worth the effort investment. Still, it's a considerable undertaking that would come at the cost of other features if I started working on it right now, which is why I'm hoping to gauge excitement for something like this. So what do you guys think? What kind of actions would you like to be completeable using an omnibar, and what kind of syntax do you think would work best?
Contributor guide
No contributing guide indexed for this repository
Research direction
No source files, tests, or entry points are named. Start by clarifying which commands and syntax the omnibar must support, then locate the existing CQUI UI command and city-queue entry points. Done means a searchable omnibar is integrated with an agreed initial command set and behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- frontend, game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100