add an article about notifications #10
Conversation
albertotirla
force-pushed
the
notifications
branch
from
a43f35c
to
ac3e1c4
Compare
|
alright, this is almost ready for merging, if you resolve the threads I attached to the file. Now, one more thing, I recommend you keep the conclusion as it was, because the so called fluf is important there, it's what characterizes our blog in a way, how we really show the reader that they are important to the project. |
|
I don't see the threads you are talking about? |
that's extremely weird, this happens on desktop too? |
content/news/notifications.md
Outdated
| ever since the [first release]({{<relref "release_0-1-0">}}), things appeared to be quite stagnant, especially from the outside. This is not an imagination of the public, this is actually true, things were quite stagnant for a while. | ||
| This is because, one of our maintainers, Tait, has something to say about that: | ||
|
|
||
| > I thought it would be easy, or at least not take very long, so I just went for it. |
There was a problem hiding this comment.
this is a bit too abrupt, people don't know what you're talking about, so before you do that, a bit of explanation would be required
content/news/notifications.md
Outdated
| > I thought it would be easy, or at least not take very long, so I just went for it. | ||
| > I spent probably a few thousand hours trying to figure out: | ||
| > - Where is the right place for this protocol (DBus spec, Wayland extention) | ||
| > - How would the specification bridge to other protocols? |
There was a problem hiding this comment.
what protocols? most of the readers don't know what that is
content/news/notifications.md
Outdated
| ## Diving Into The Hacks | ||
|
|
||
| In response to the absence of an accessibility dedicated API for system information in the freedesktop stack, various hacks have emerged over time. | ||
| Our approach, while different in to Orca, isn't too far off from existing solutions. |
There was a problem hiding this comment.
different from orca, not into. I would make it a suggestion, but I dk how, so it's a line comment
content/news/notifications.md
Outdated
| ### Odilia's Hack | ||
|
|
||
| Odilia's hack relies on the [freedesktop notifications specification](https://specifications.freedesktop.org/notification-spec/notification-spec-latest.html) to be implemented by notification daemons. | ||
| This required some up-front design work to essentially write our own notification daemon, but this will be extremely resilient to long-term change. |
There was a problem hiding this comment.
not at all, we didn't write our own notification daemon. Instead, we used monitoring to sniff the bus for calls to the methods which are used to post a notification to the existing daemon. We can't make a daemon, I think, because from what I read, having more than one notification daemon in the system means that one of them will get the signals, while the other won't, so odilia might read the notification, but it might not be displayed on the desktop environment's place for notifications
content/news/notifications.md
Outdated
|
|
||
| This approach has its own advantages: | ||
|
|
||
| 1. We don't rely on presentation. Each notification daemon can present things however it wants on screen, as long as it receives notification through the standard notification specification. |
There was a problem hiding this comment.
either recieves a notification, or recieves notifications
|
@albertotirla please check changes |
because of the current sprint of development, we have a new feature, reading notifications. This article talks about that
the commit was there originally on main, but now I'm doing some hacks to allow this to be reviewed properly before making it available to the public