Skip to content

Compare segments and periods (in API and UI) #14365

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 182 commits into from
Sep 30, 2019
Merged

Compare segments and periods (in API and UI) #14365

merged 182 commits into from
Sep 30, 2019

Conversation

diosmosis
Copy link
Member

@diosmosis diosmosis commented Apr 23, 2019

Fixes #5711
Fixes #7716

Related sparkline PR is here: davaxi/Sparkline@master...matomo-org:multiple-series

@diosmosis diosmosis added Pull Request WIP Indicates the current pull request is still work in progress and not ready yet for a review. not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org. labels Apr 23, 2019
@diosmosis diosmosis added this to the 3.10.0 milestone Apr 23, 2019
…ults in 100% cpu usage (when reading dataTable param w/ many rows & comparison tables), get overlay/transitions icons to appear, overlay should work properly.
…isons in subtables by forcing idSubtables of comparisons to be sent in request (makes UI work, but not pracitcal for API).
@diosmosis
Copy link
Member Author

diosmosis commented Apr 27, 2019

FYI @mattab / @tsteur ready for an initial UX review. Comparisons should be integrated in the following ways:

-> html table (including actions table + support for subtables)
-> evolution graphs
-> bar graphs
(not pie graphs, since it's not possible to show multiple serieses)
(not sparklines since we'd have to color code different comparisons, which would be confusing w/ evolution graphs since they have their own colors)
-> row evolution/overlay/transitions/segmented visitor log (they display on comparison rows and parameters should change appropriate for the specific compared period/segment)
NOTE: there is one issue here when the table is too big. When there are too many rows, maxNumRowsToHandleEvents blocks row actions from displaying. Since comparing multiplies the amount of rows, it can happen often.

Remaining todo:

  • see if we can eliminate need for maxNumRowsToHandleEvents
  • fix random UI issues (eg, normal subtables have a huge label column)
  • UI tests
  • other in source todo

@diosmosis
Copy link
Member Author

@tsteur Applied the review feedback, will fix the tests now.

@diosmosis
Copy link
Member Author

@tsteur tests are passing, can give it another review now.

}

console.log(this.multiEvolutionRows, this.multiEvolutionRowsSeries);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the console.log should be removed?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

}

function checkEnabledForCurrentPage() {
var category = piwikUrl.getSearchParam('category') || piwikUrl.getSearchParam('module');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you leave a comment when the module/action applies? I suppose it applies when it is widgetized?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's for MultiSites, since it uses a module/action. I guess anything that links through the top bar.

@@ -21,6 +21,7 @@
{% else %}
{% set rowIndex = properties.filter_offset|default(0) + 1 %}
{%- for rowId, row in dataTable.getRows() -%}
{% if rowId != constant('Piwik\\DataTable::ID_TOTALS_ROW') %}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@diosmosis just double checking... in my Datatable class in your branch I'm not seeing that constant.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you're looking at old code, it's not there if I look at "files changed".

@diosmosis diosmosis merged commit 3f26e78 into 3.x-dev Sep 30, 2019
@diosmosis diosmosis deleted the 5711_4 branch September 30, 2019 17:19
sgiehl added a commit that referenced this pull request Oct 28, 2019
sgiehl added a commit that referenced this pull request Oct 28, 2019
sgiehl added a commit that referenced this pull request Oct 28, 2019
mattab pushed a commit that referenced this pull request Oct 29, 2019
* Fix label truncation calculation

regrssion of #14365

* updates expected screenshots
diosmosis pushed a commit that referenced this pull request Nov 6, 2019
* Fix label truncation calculation

regrssion of #14365

* updates expected screenshots
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Review PRs that need a code review not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org.
Development

Successfully merging this pull request may close these issues.

Compare segments Compare data for two different dates in tables, charts and reports
3 participants