Reviewing merge request #2: Add sorting options and archived/future choice to the component parameters

Add sorting options and archived/future choice to the component parameters

As the data retrieval is done by the model, use the view's parameters in the model to retrieve only the desired events in the desired order (i.e. a menuitem can select to only show archived events in descending order, or so). Also, add an override for archive (i.e. if no task is given, use the archive parameter to check whether archived entries should be used).

This (using component parameters) is much cleaner than using view parameters. Currently, only the eventlist view/model makes use of the component parameters. If you think this is the correct way to handle default sorting options, the other models/views need to be adjusted as well.

Commits that would be merged:

Version 2
  • Version 1
  • Version 2
  • 1fc9b36
  • d128651
  • Add sorting options and archived/future choice to the component parameters

Showing 1fc9b36-d128651

Comments

Add a new comment:

Login or create an account to post a comment

How to apply this merge request to your repository