mediawiki-extensions-Echo/modules/ui/mw.echo.ui.DatedNotificationsWidget.js

165 lines
4.3 KiB
JavaScript
Raw Normal View History

( function ( $, mw ) {
/**
* A notifications list organized and separated by dates
*
* @class
* @extends OO.ui.Widget
* @mixins OO.ui.mixin.PendingElement
*
* @constructor
* @param {mw.echo.Controller} controller Echo controller
* @param {mw.echo.dm.ModelManager} modelManager Model manager
* @param {Object} [config] Configuration object
* @cfg {jQuery} [$overlay] An overlay for the popup menus
*/
mw.echo.ui.DatedNotificationsWidget = function MwEchoUiDatedNotificationsListWidget( controller, modelManager, config ) {
config = config || {};
// Parent constructor
mw.echo.ui.DatedNotificationsWidget.parent.call( this, config );
// Mixin constructors
OO.ui.mixin.PendingElement.call( this, config );
this.manager = modelManager;
this.controller = controller;
this.models = {};
this.$overlay = config.$overlay || this.$element;
this.listWidget = new mw.echo.ui.SortedListWidget(
// Sorting callback
function ( a, b ) {
// Reverse sorting
return Number( b.getTimestamp() ) - Number( a.getTimestamp() );
},
// Config
{
classes: [ 'mw-echo-ui-datedNotificationsWidget-group' ],
$overlay: this.$overlay
}
);
// Events
this.manager.connect( this, {
update: 'populateFromModel',
Relate read-state filter and mark read/unread action When we are viewing a certain read state filter ('read' or 'unread') the visibility of items should correspond to that state even when the user marks a specific item as read/unread. That means that the system should remove these items from view when the action is taken. In this commit: * The controller makes the judgment of whether to remove items when read/unread action is taken, based on whether a filter is set. * We clean up the terminology of discard - no more 'remove' - to make sure we have consistency in the code. * Related: The 'discard' event is now scoped within the hierarchy; meaning, lists emit 'discard' when an item is removed, grouplist emits 'discard' when a group is removed, and the manager emits 'discard' when an entire notification model is removed. This means we can actually have proper hierarchy and organization with a single event, and not worry about clashing between the intentional 'discard' action and the event 'remove' that is also used while resorting happens. * The model manager emits a discard event when a model is removed so that the general list can listen to the manager and remove an entire batch of items if needed. * The pagination model now updates the count for the current page rather than some vague notion of the last page. This is also updated when the controller removes items, so we can get an accurate count in the page for the number of notifications that are displayed. Bug: T136891 Change-Id: I247c618042ef256fadf09922f7b83bd1ad361f64
2016-07-14 00:03:57 +00:00
discard: 'onManagerDiscardModel'
} );
this.$element
.addClass( 'mw-echo-ui-datedNotificationsWidget' )
.append( this.listWidget.$element );
// Initialization
this.populateFromModel();
};
/* Initialization */
OO.inheritClass( mw.echo.ui.DatedNotificationsWidget, OO.ui.Widget );
OO.mixinClass( mw.echo.ui.DatedNotificationsWidget, OO.ui.mixin.PendingElement );
Relate read-state filter and mark read/unread action When we are viewing a certain read state filter ('read' or 'unread') the visibility of items should correspond to that state even when the user marks a specific item as read/unread. That means that the system should remove these items from view when the action is taken. In this commit: * The controller makes the judgment of whether to remove items when read/unread action is taken, based on whether a filter is set. * We clean up the terminology of discard - no more 'remove' - to make sure we have consistency in the code. * Related: The 'discard' event is now scoped within the hierarchy; meaning, lists emit 'discard' when an item is removed, grouplist emits 'discard' when a group is removed, and the manager emits 'discard' when an entire notification model is removed. This means we can actually have proper hierarchy and organization with a single event, and not worry about clashing between the intentional 'discard' action and the event 'remove' that is also used while resorting happens. * The model manager emits a discard event when a model is removed so that the general list can listen to the manager and remove an entire batch of items if needed. * The pagination model now updates the count for the current page rather than some vague notion of the last page. This is also updated when the controller removes items, so we can get an accurate count in the page for the number of notifications that are displayed. Bug: T136891 Change-Id: I247c618042ef256fadf09922f7b83bd1ad361f64
2016-07-14 00:03:57 +00:00
mw.echo.ui.DatedNotificationsWidget.prototype.onManagerDiscardModel = function ( modelId ) {
var group,
model = this.models[ modelId ],
list = this.getList();
if ( model ) {
group = list.getItemFromId( model.getName() );
list.removeItems( [ group ] );
}
};
/**
* Respond to model removing source group
*
* @param {string} source Symbolic name of the source group
*/
mw.echo.ui.DatedNotificationsWidget.prototype.onModelRemoveSource = function ( source ) {
var list = this.getList(),
group = list.getItemFromId( source );
list.removeItems( [ group ] );
};
/**
* Respond to model manager update event.
* This event means we are repopulating the entire list and the
* associated models within it.
*/
mw.echo.ui.DatedNotificationsWidget.prototype.populateFromModel = function ( models ) {
var modelId, model, subgroupWidget,
groupWidgets = [];
// Detach all attached models
for ( modelId in this.models ) {
this.detachModel( modelId );
}
for ( model in models ) {
// Create SubGroup widgets
subgroupWidget = new mw.echo.ui.DatedSubGroupListWidget(
this.controller,
models[ model ],
{
showTitle: true,
showMarkAllRead: true,
$overlay: this.$overlay
}
);
Relate read-state filter and mark read/unread action When we are viewing a certain read state filter ('read' or 'unread') the visibility of items should correspond to that state even when the user marks a specific item as read/unread. That means that the system should remove these items from view when the action is taken. In this commit: * The controller makes the judgment of whether to remove items when read/unread action is taken, based on whether a filter is set. * We clean up the terminology of discard - no more 'remove' - to make sure we have consistency in the code. * Related: The 'discard' event is now scoped within the hierarchy; meaning, lists emit 'discard' when an item is removed, grouplist emits 'discard' when a group is removed, and the manager emits 'discard' when an entire notification model is removed. This means we can actually have proper hierarchy and organization with a single event, and not worry about clashing between the intentional 'discard' action and the event 'remove' that is also used while resorting happens. * The model manager emits a discard event when a model is removed so that the general list can listen to the manager and remove an entire batch of items if needed. * The pagination model now updates the count for the current page rather than some vague notion of the last page. This is also updated when the controller removes items, so we can get an accurate count in the page for the number of notifications that are displayed. Bug: T136891 Change-Id: I247c618042ef256fadf09922f7b83bd1ad361f64
2016-07-14 00:03:57 +00:00
this.attachModel( model, models[ model ] );
subgroupWidget.resetItemsFromModel();
groupWidgets.push( subgroupWidget );
}
// Reset the list and re-add the items
this.getList().clearItems();
this.getList().addItems( groupWidgets );
};
/**
* Attach a model to the widget
*
* @param {string} modelId Symbolic name for the model
* @param {mw.echo.dm.SortedList} model Notifications list model
*/
mw.echo.ui.DatedNotificationsWidget.prototype.attachModel = function ( modelId, model ) {
this.models[ modelId ] = model;
};
/**
* Detach a model from the widget
*
* @param {string} modelId Notifications list model
*/
mw.echo.ui.DatedNotificationsWidget.prototype.detachModel = function ( modelId ) {
this.models[ modelId ].disconnect( this );
delete this.models[ modelId ];
};
/**
* Get the list widget contained in this item
*
* @return {mw.echo.ui.SortedListWidget} List widget
*/
mw.echo.ui.DatedNotificationsWidget.prototype.getList = function () {
return this.listWidget;
};
/**
* Get the number of all notifications in all sections of the widget
*
* @return {number} The number of all notifications
*/
mw.echo.ui.DatedNotificationsWidget.prototype.getAllNotificationCount = function () {
var i,
count = 0,
groups = this.getList().getItems();
for ( i = 0; i < groups.length; i++ ) {
count += groups[ i ].getListWidget().getItemCount();
}
return count;
};
} )( jQuery, mediaWiki );