> On 4 Oct 2017, at 12:34, Ecaterina Moraru (Valica) <[email protected]> wrote: > > On Wed, Oct 4, 2017 at 1:00 PM, Guillaume Delhumeau < > [email protected]> wrote: > >> 2017-10-03 17:32 GMT+02:00 Ecaterina Moraru (Valica) <[email protected]>: >> >>> On Tue, Oct 3, 2017 at 10:50 AM, Guillaume Delhumeau < >>> [email protected]> wrote: >>> >>>> 2017-10-02 18:09 GMT+02:00 Vincent Massol <[email protected]>: >>>> >>>>> >>>>>> On 2 Oct 2017, at 18:08, Vincent Massol <[email protected]> >> wrote: >>>>>> >>>>>> >>>>>>> On 2 Oct 2017, at 18:05, Vincent Massol <[email protected]> >> wrote: >>>>>>> >>>>>>> Another feedback/questions: >>>>>>> >>>>>>> * Is the avatar icon clickable and leading to the user profile? >>>>>>> * We need a way to link directly to the diff, at least for page >>> events >>>>> so that the user can see what was modified (as we have currently in >> the >>>> AS) >>>>>> >>>>>> * Maybe “2 hours ago” is not precise enough. In your example I see >> I >>>>> created and modified the Roadmap page but they both say “2 hours >> ago”. >>>>> Shouldn’t I be able to see how far away both events were done? >>>>> >>>>> My understanding is that events are grouped by app+type but not by >>> entity >>>>> anymore (for page events) and thus you can have 3 events displayed >> for >>>> the >>>>> same page, f.ex: Creation, Modification, Deletion. >>>>> >>>> >>>> And you could also have different users grouped in the same composite >>>> event. So when you display the details, it would be nice to show which >>> user >>>> made each event, and I see you have removed this info. >>>> >>> >>> The focus of this proposal is on user, compared to the old one, when it >> was >>> on the app/doc. >>> Close to what we have on Facebool. So it didn't made sense that we say >> that >>> a page has been edited by vmassol, and that the details showcase that >>> multiple user actually did the edit. >>> >> >> But it's the way it is implemented right now. If we change that, it's not >> only an UI change, it's also on the API-side too. Or maybe we could display >> more than one avatar ? >> > > The proposal is done as a prototype and I had no problems in displaying the > events. Maybe there is something I'm missing? > In theory, if another person changed something too, it should be displayed > as a separate entry. > > >> >> Other problem: the emails that the notifications module send are supposed >> to replace the watchlist at some point. Vincent already complained about >> the fact the events concerning documents are not displayed as a tree, >> corresponding to the hierarchy of the pages. I could think of a way to >> display the events as a tree, but if we decide to focus more on the users, >> we are going in two opposite directions. >> >> Do you plan to cover the email case in your proposals? >> > > I don't plan to cover that case.
Actually, could you cover it too please in your designs? It’s important that we cover it because we’re planning to replace the watchlist email with the notifications email so we need to have something at least as good from user/usability POV. > I am not sure what exactly it's the > problem with the watchlist and why it should be displayed as a tree. If you check the watchlist emails we receive from xwiki.org you’ll see the TOC at the top right of the mail. This is very useful to navigate the email, when there are several page changes. Since 99% of the events we send and that will arrive in the watchlist are document-related events, I would find it a pity that we drop the concept of having a watchlist email TOC that helps you navigate in the mail. We don’t necessarily need the same TOC but I think we need some kind of TOC to navigate the mail (which can be large pretty fast). When users upgrade to XWiki 9.10+ and start receiving the new notification emails they need to find it better than what they had previously. If we remove the TOC, will they still be able to think that? That’s the question we need to answer. They won’t care that our system is more generic if it’s less usable. Thanks -Vincent > If we > like to propose an alternative view we could do it in a separate page, but > the "Notifications menu" should be what users expect from a notification > system and what they are used to see in other applications. If we want to > propose something extra, more powerful, it should be additional and not the > main design. > > Thanks, > Caty > > >> >> Thanks, >> >> >>> >>>> >>>> >>>> >>>>> >>>>> Thanks >>>>> -Vincent >>>>> >>>>>> >>>>>> Thanks >>>>>> -Vincent >>>>>> >>>>>>> >>>>>>> Thanks >>>>>>> -Vincent >>>>>>> >>>>>>>> On 2 Oct 2017, at 18:01, Vincent Massol <[email protected]> >>> wrote: >>>>>>>> >>>>>>>> >>>>>>>>> On 2 Oct 2017, at 17:54, Ecaterina Moraru (Valica) < >>>> [email protected]> >>>>> wrote: >>>>>>>>> >>>>>>>>> Event Type: BlogPostPublishedEvent >>>>>>>>> from >>>>>>>>> http://design.xwiki.org/xwiki/bin/view/Proposal/ >>>>> NotificationsImprovements9x#HEventTypes >>>>>>>> >>>>>>>> ok thanks, had missed this since I was reading from top to bottom >>> and >>>>> stopped at the overview :) >>>>>>>> >>>>>>>> However I don’t think it scales since it means one unique icon >> per >>>>> combination of app type + event type. >>>>>>>> >>>>>>>> What would scale better is two icons: one for the app type and >> one >>>> for >>>>> the event type. >>>>>>>> >>>>>>>> For example imagine that the Blog app had the following events: >>>>>>>> * When a blog post is published >>>>>>>> * When a blog post is created >>>>>>>> * When a blog post is removed >>>>>>>> >>>>>>>> You wouldn’t be able to use the RSS icon to represent the 3 >> events. >>>>>>>> >>>>>>>> BTW the RSS icon isn’t necessarily representative of the Blog >> app. >>> A >>>>> lot of apps can have a RSS feed. >>>>>>>> >>>>>>>> That’s the main remark I have: it’s going to be harder and harder >>> to >>>>> find unique icons as we had more events to apps, especially if >> there’s >>>> only >>>>> 1 icon that is supposed to combine both app type + event type. >>>>>>>> >>>>>>>> WDYT? >>>>>>>> >>>>>>>> Thanks >>>>>>>> -Vincent >>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Caty >>>>>>>>> >>>>>>>>> On Mon, Oct 2, 2017 at 6:52 PM, Vincent Massol < >>> [email protected]> >>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi Caty, >>>>>>>>>> >>>>>>>>>>> On 2 Oct 2017, at 17:21, Ecaterina Moraru (Valica) < >>>>> [email protected]> >>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> I've created some improvements suggestions for our >> Notifications >>>>> UI, see >>>>>>>>>>> http://design.xwiki.org/xwiki/bin/view/Proposal/ >>>>>>>>>> NotificationsImprovements9x >>>>>>>>>>> >>>>>>>>>>> Let me know what you think. >>>>>>>>>> >>>>>>>>>> Re the overview, I don’t see where you mention the app? >>>>>>>>>> >>>>>>>>>> For example, could you show how a new Blog post would be >>> displayed >>>>> and you >>>>>>>>>> differentiate that for example from a Page creation or >>>> modification? >>>>>>>>>> >>>>>>>>>> Thanks >>>>>>>>>> -Vincent >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>>> Caty >>>>>>>>>> >>>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Guillaume Delhumeau ([email protected]) >>>> Research & Development Engineer at XWiki SAS >>>> Committer on the XWiki.org project >>>> >>> >> >> >> >> -- >> Guillaume Delhumeau ([email protected]) >> Research & Development Engineer at XWiki SAS >> Committer on the XWiki.org project
