-
Notifications
You must be signed in to change notification settings - Fork 939
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A bit material design #654
Conversation
Huge thanks for this! The update on the Drawer Toggle is causing Travis CI to fail, please see the logfile. |
@SecUpwN There seems to be an error with the AVD on travis. I'll have a look at it later |
Thanks, I'll be wating with merging until a fix has been added here.
Since we likely cannot circumvent that our app gets displayed incorrectly some day when Google decides to changes more stuff and guidelines of the AOS (don't ask how much we hate that), we've been re-thinking the Icons in the navigation drawer and would be happy if you'd chime in on #512 to solve this. |
@SecUpwN you linked to peeking notification, but app uses ongoing notification now. Is anyone planning removing ongoing notification or am I missing something? |
@@ -99,11 +99,10 @@ android { | |||
dependencies { | |||
// DO NOT REMOVE BELOW COMMENTED-OUT CODE BEFORE ASKING! | |||
//compile 'com.github.amlcurran.showcaseview:library:5.0.0' | |||
//compile 'com.android.support:appcompat-v7:22.1.1' | |||
compile 'com.android.support:appcompat-v7:22.+' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this can cause unexpected behaviour depending on build machine. Please specify version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found it out really hard way...
@agilob @SecUpwN I think there should be one persistent notification with low priority (in order to keep the service alive) and an additional peeking notification with high priority on status changes. I like this Idea: #512 (comment) |
@larsgrefer, the idea from #512 (comment) is not final yet, let's discuss the usage of notifications there. Current priority on this PR is to solve the following things (thanks ahead for digging deeper):
|
67c758f
to
999f267
Compare
@SecUpwN what is tested by |
LOL |
@larsgrefer, partially. The main fix to show the colored notification was deb50bf, which will likely be removed when you update the Coming back to the failing Travis CI check, please see if you can fix this part of the PR:
@agilob, don't we need that |
#656 should fix the travis errors |
999f267
to
f64e404
Compare
Thanks, that indeed fixed the Travis CI check. @larsgrefer, last question regarding this PR: Will #479 come back when we merge this? The purpose was to keep the notification icon colored, I expect that with changing the |
If we merge this the statusbar-icon will be just a white shape like here: larsgrefer@5ac2763#commitcomment-14785284 But the icon of the full notification will be colored like here: #479 (comment) I don't think we should stay on pre-lollipop and block material design just to keep a colored status bar icon In order to inform about a status change i'd suggest to use a "peeking notification": |
Makes sense, but the reason I previously opened #479 was because users would always have to pull down the notification bar in order to see the current state of our our app (as long as we have not implemented peeking notifications). @larsgrefer, please add the link and your thaoughts about peeking notifications to #512. Regarding the merge of this PR, I would like to hear the opinion of @He3556 as well. |
In fact there is a running avd in an emulator —Reply to this email directly or view it on GitHub. |
No description provided.