2017-07-17 12:50 GMT+02:00 Marius Dumitru Florea <
[email protected]>:

> On Mon, Jul 17, 2017 at 1:06 PM, Clément Aubin <[email protected]>
> wrote:
>
> > Hi,
> >
> > On 07/13/2017 02:28 PM, Ecaterina Moraru (Valica) wrote:
> > > We could have a setting: "watch all locations" or "watch just
> particular
> > > pages". Further more you have the ability to "watch all events" or play
> > > with the on/off switches.
> >
> >
>
> > If the proposal of Marius is implemented (adding exclusion filters to
> > notifications),
>
>
> Or inclusion list. It depends what you think is best: start with no
> notification or start with all notifications.
>

Well, we currently start with all notifications. Changing that would break
compatibility so that's why we need to implement an exclusion list to go on.


>
>
> > then this should be easily doable, but we have to think
> > about how to include this feature in the notification center UI (which
> > is already a bit crowded).
> >
> > > If the user sets to "just particular pages", than the "watch" icon
> > appears
> > > and we use the include list. Also when setting watch for particular
> > pages,
> > > the user might want to configure the "auto-watch" for the pages he
> > created,
> > > or commented, or edited. Those pages will be automatically added in the
> > > include list, with the possibility to manually remove them from the
> page
> > > (on the bell icon) or from the watched filters list.
> > >
> > > Thanks,
> > > Caty
> > >
> > > On Wed, Jul 12, 2017 at 2:26 PM, Guillaume Delhumeau <
> > > [email protected]> wrote:
> > >
> > >> It makes sense. Creating an exclude filter is much more natural than
> the
> > >> complicated filter I was proposing...
> >
> > I do agree on that. Apart from the use case that we are currently
> > talking about, this could be useful in further notification center
> > improvements.
> >
> > >> But in the case of the auto-watch, it could be good to store somewhere
> > the
> > >> list of pages where the user has contributed, in order to still
> include
> > >> them even if the user disable the notifications on a larger scope.
> >
> > So I guess that it would take too much time to get a list of
> > contributions directly from a query on the database (particularly for
> > large wikis with a lot of pages). We could add references to the
> > contributed pages of a user directly in XObjects linked to its profile.
> >
> > >> 2017-07-12 10:57 GMT+02:00 Marius Dumitru Florea <
> > >> [email protected]>:
> > >>
> > >>> On Tue, Jul 11, 2017 at 7:26 PM, Guillaume Delhumeau <
> > >>> [email protected]> wrote:
> > >>>
> > >>>> *TL;DR*
> > >>>>
> > >>>>    - Add a button in each page that will allow you to subscribe to
> all
> > >>>>    events that happens to that page.
> > >>>>    - When you subscribe to a page with this "in-context" bell, it
> must
> > >>> not
> > >>>>    affect your other preferences regarding notifications.
> > >>>>
> > >>>> *Full Post*
> > >>>>
> > >>>> Hello developers,
> > >>>>
> > >>>> With Clément Aubin, we are implementing new features in the
> > >> Notifications
> > >>>> Application in order to be able to remove the Watchlist Application.
> > >>>>
> > >>>> *Status*
> > >>>>
> > >>>> Currently, a user can subscribe to different kinds of events (ex:
> > >>> "update",
> > >>>> "comment", "blog published", etc...). Recently, we have also added
> the
> > >>>> ability to restrict on which locations we are interested in, for
> each
> > >>> kind
> > >>>> of events. For example, we are now able to say, "for the *update*
> > >> event,
> > >>>> show me notifications only about the wiki ABC and for the *blog
> post*
> > >>>> event, show me notifications only about the space XYZ".
> > >>>>
> > >>>> If you have no restriction (a.k.a "filters") on an event type, then
> > you
> > >>>> receive notifications for every event matching the event type in the
> > >>> wiki,
> > >>>> no matter the location of the entity it concerns.
> > >>>>
> > >>>> *Objectives*
> > >>>>
> > >>>> In the Watchlist Application, we had 3 switches on the top menu that
> > >> was
> > >>>> displayed on every page, and these switches were "watch this wiki /
> > >> watch
> > >>>> this space / watch this page". That would be great if we could have
> > the
> > >>>> same for the notifications.
> > >>>>
> > >>>> *Proposal*
> > >>>>
> > >>>>    - Add the ability to subscribe to all events that happen in a
> given
> > >>>>    location, no matter their type (≈ what the watchlist does).
> > >>>>    - In each page, add a button to subscribe to the current
> location:
> > >>>>    https://pasteboard.co/GAqEi6M.png (thanks Caty for the mockup)
> > >>>>
> > >>>
> > >>>
> > >>>>    - Problem: if you previously had no restriction, you suddenly
> add a
> > >>> new
> > >>>>       one that will prevent you to receive any notifications
> > >>>> concerning the other
> > >>>>
> > >>>
> > >>> Maybe I didn't understood correctly, but if you have no restrictions
> > and
> > >>> you go to a page A then that page should appear as "watched" because
> > you
> > >>> are receiving notifications for that page (because you don't have
> > >>> restrictions). So if the icon is "watched" then clicking on it will
> > >> toggle
> > >>> "don't watch". So you are actually removing that page from the list
> of
> > >>> watched pages (i.e. you add an exclude).
> > >>>
> > >>> It all depends on what's the initial state:
> > >>>
> > >>> (1) receive notifications from everywhere => then when you go to a
> page
> > >> you
> > >>> can exclude it
> > >>> (2) no notifications => then when you go to a page you can include it
> > >>>
> > >>> So it depends what you understand by "no restrictions". Either all
> > >>> notifications or no notifications.
> > >>>
> > >>> Hope this helps,
> > >>> Marius
> > >>>
> > >>>
> > >>>>       locations. A bit like the rights module: adding a right to
> > >>>> someone at some
> > >>>>       level will dismiss rights for all other people. I guess we all
> > >>>> agree it's a
> > >>>>       problem on the User Experience point of view.
> > >>>>       - Proposition: the restriction added by the "in-context"
> button
> > >>>>       should be *inactive if there is no other restriction enabled
> > >>> manually
> > >>>>       via the notification preferences UI*.
> > >>>>       - Rational:
> > >>>>          - When you are on the notifications preferences, you can
> > >>> actually
> > >>>>             see all restrictions, so you can understand that
> creating
> > >>>> one will make you
> > >>>>             lose all notifications that do not honor the
> restrictions.
> > >>>>             - However, when you are on a page, you don't see all the
> > >>>>             restrictions. If you click on the "subscribe" bell
> > >>>> naively, you might not
> > >>>>             expect it will impact all other notifications. It would
> > >>>> actually be very
> > >>>>             confusing.
> > >>>>             - In addition: if we add an "auto-watch" option, that
> add
> > >> the
> > >>>>    page you just saved to the list of locations you are interested
> in,
> > >> we
> > >>>> need
> > >>>>    to have this feature too. Otherwise saving a document will make
> all
> > >>>> other
> > >>>>    notifications silent.
> > >>>>
> > >>>> That is our plan. Cast you ideas!
> > >>>>
> > >>>> Thanks,
> > >>>>
> > >>>> Guillaume
> > >>>>
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> Guillaume Delhumeau ([email protected])
> > >> Research & Development Engineer at XWiki SAS
> > >> Committer on the XWiki.org project
> > >>
> >
> > Thanks,
> >
> > --
> > Clément Aubin
> > Web Developer Intern @XWiki SAS
> > [email protected]
> > More about us at http://www.xwiki.com
> >
>



-- 
Guillaume Delhumeau ([email protected])
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project

Reply via email to