Skip to content

Notifications #290

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

Closed

Conversation

LucasLeandro1204
Copy link
Contributor

I'm working on the notifications, we need that to #271, #270 and #279. But I'm not a good designer, so I need help before getting deep into it xd

It's using vue, he will turn the job easier later.

This is how it looks now

image

The first one are in the hover state, the last one are marked as read.

@driesvints
Copy link
Member

This is amazing! I'll try to look at this as soon as I have the time.

@atgg
Copy link
Contributor

atgg commented Jul 11, 2017

It's using vue, he will turn the job easier later.

Any reason to use Vue instead of the traditional server-side rendering?

@LucasLeandro1204
Copy link
Contributor Author

@atgg It's not that necessary, however is easier to manipulate the dom and make ajax requests with it, thinking about the "mark as read" and "delete" triggers, and later will be easier to add real time notifications.

But what is better, that page or a modal?
reference:

image

@atgg
Copy link
Contributor

atgg commented Jul 11, 2017

@LucasLeandro1204

however is easier to manipulate the dom [...] thinking about the "mark as read" and "delete" triggers

I think it would be better to mark every notification as read after rendering the notifications page. Also, I have mixed feelings about being able to delete a notification.

But what is better, that page or a modal?

I would go for the page just because it's possible for users who refuse to run JavaScript to see the notifications.

@LucasLeandro1204
Copy link
Contributor Author

LucasLeandro1204 commented Jul 11, 2017

@atgg

I think it would be better to mark every notification as read after rendering the notifications page.

Yeah, it's a nice idea to, so I will add an aside menu like Github Notifications

@driesvints
Copy link
Member

@LucasLeandro1204 modal looks nicer.

I personally think it's best to let the user manually mark notifications as read like Github does.

@driesvints
Copy link
Member

@LucasLeandro1204 actually I think both the modal and screen can be useful. Perhaps a "view all" button at the bottom of the modal?

@LucasLeandro1204
Copy link
Contributor Author

@driesvints I agree, both are great. The modal will show only unread notifications.

@LucasLeandro1204
Copy link
Contributor Author

@driesvints I downsized the sizes to match the modal

image

That's how the modal looks like (ignore the read notifications).

image

When empty

image

I used the same header background color in notification hover, but seems too dark for me, and the "view all" button aren't the best too.

To mobile I think it's better to hide the modal and link the button to /notifications, what you say?

@LucasLeandro1204
Copy link
Contributor Author

Added a small toggler to subscribe a Thread.

image

@driesvints
Copy link
Member

@LucasLeandro1204 I think it's best that we do that in another PR so this one doesn't becomes to large. I also had something else in mind for that. Just a subscribe/unsubscribe button on the left.

@LucasLeandro1204
Copy link
Contributor Author

@driesvints I added it here to have something to test the notifications in hand, but I can split it into another pull request to this branch.

@driesvints
Copy link
Member

@LucasLeandro1204 heya, unfortunately I won't have time to look at this until next week. I'll keep you posted.

@LucasLeandro1204
Copy link
Contributor Author

@driesvints I guess you already can review this pull request, feel free to when you have time =)

@driesvints
Copy link
Member

@LucasLeandro1204 heya! So sorry I haven't gotten to this yet. It's been pretty hectic for me lately and I still have quite a busy month ahead so it might be a while before I get to this. But I haven't forgotten about it yet, just so you know :)

I saw that you closed your other PR? Any reason for that?

@LucasLeandro1204
Copy link
Contributor Author

@driesvints It's a bit messy (all the commits from here are there) and unfinished, I will let it closed until we finish this one.

@inesarmadabras
Copy link

Hi @LucasLeandro1204 ! Any news on this pull request? Anything missing or just waiting for review?

@driesvints
Copy link
Member

@inesarmadabras waiting for review from me.

@LucasLeandro1204
Copy link
Contributor Author

@inesarmadabras I have to review this one again, probably some rework, is already too old xd.

@driesvints driesvints mentioned this pull request Oct 18, 2017
@BobbyBorisov
Copy link
Contributor

@LucasLeandro1204 these notifications look so cool! 🥇

@driesvints driesvints mentioned this pull request Mar 25, 2018
@driesvints
Copy link
Member

Hey @LucasLeandro1204. I'm gonna close this for now since the PR is out of date with the current codebase. Maybe we can salvage some things in the future on a fresh attempt. Thanks for your work and sorry for getting back so late.

@driesvints driesvints closed this Nov 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

5 participants