Azurency / Azurency/CQUI_Community-Edition

New Feature/Toolset: Paradox Bar!

Open
#104 23 comments 0 reactions 0 assignees View on GitHub
enhancement in progress
Dominant language
Lua
Stars
397
Forks
93
PR merge metrics
No merged PRs in 30d

Description

**Issue by [chaorace](https://github.com/chaorace)**
_Sunday Apr 30, 2017 at 00:40 GMT_
_Originally opened as https://github.com/CQUI-Org/cqui/pull/514_

----

## _What is this_?
Okay, so there's the name... It's basically an imitation of the the notification scheme found in the grand-strat games published by Paradox, like Crusader Kings, Europa Universalis, and Stellaris. It looks [like this](http://i.imgur.com/cV8nr2K.png) if you're drawing a blank.

Right, so that's the idea, implementing a saner notification scheme that's easier to read. How far along is this pie-in-the-sky dream? It's _complete_! So, why is this a PR instead of just going direct-to-game? Well... there's only two notifications implemented so far, and they're both purely for debugging purposes. That being said, the internals have been tested extensively and the "API" of this element has been engineered specifically for robustness, flexibility, and ease of use. It's ready for people to start throwing things at it now!

Seeing as we've run short on low-hanging fruit recently, which has dried out the flow of commits somewhat, I've decided to put this PR up as an additional avenue for both the @CQUI-Org/feature-team and outside contributors to quickly and easily extend CQUI.

## So, _what's the plan_?
The plan is to implement notifications that do not exist currently into this new notification system. Once we're confident with the number of notifications implemented, we'll soft-launch this while keeping the old notification system. This way we'll have a chance to gather some user feedback on performance, bugs, and usability without really risking bricking up the notifications that already exist in the base game. After that, we'll see about moving over all notifications to this new notification platform, along with implementing much-requested features like snoozing notifications and muting specific notification groups

## _Why abandon the existing notification bar_?
It's difficult to mod, plain and simple! The difficulty present in extending the existing notification system makes it a very unpleasant proposition and is the reason we've been unable to tackle the many existing requests for adding new notifications. It's at the point where we had to instead hijack the gossip popups instead, even when they weren't necessarily the best choice. Moving over to our own custom solution also comes with the added benefit of being able to add notification stacking, a much requested feature.

## _Beta_
It's been too long, I've been putting off the beta tag since November. Let's finish up this last feature and finally release the first beta build 😎

----

_**[chaorace](https://github.com/chaorace)** included the following code: https://github.com/CQUI-Org/cqui/pull/514/commits_

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the commits from PR 514 and comparing the Paradox Bar with CQUI’s existing notification bar. The issue describes a new notification platform with two debugging notifications; done means implementing additional notifications, validating performance, bugs, and usability, and preparing the first beta build.

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
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.