Skip to content
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

Allow ViewDataTables to be rendered via metadata alone #4040

Closed
diosmosis opened this issue Jul 8, 2013 · 32 comments
Closed

Allow ViewDataTables to be rendered via metadata alone #4040

diosmosis opened this issue Jul 8, 2013 · 32 comments
Labels
Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Milestone

Comments

@diosmosis
Copy link
Member

Related to #1491.

Should be possible to define a set of display properties for a report and have ViewDataTable automatically render based on those properties. This would replace the current method of manually creating a ViewDataTable instance and calling setXXX and disableYYY functions on it before rendering.

@anonymous-matomo-user
Copy link

In 0105777: Refs #4040, #4041, move all ViewDataTable properties to the viewProperties array and allow these properties to be specified through new display metadata. Converted the Actions, Goals, UserSettings and VisitTime controllers.

Notes:

  • Includes refactoring of ExcludeLowPopulation filter.

@anonymous-matomo-user
Copy link

In d99e37e: Refs #4040, Modify getReportDisplayProperties to add display properties for all of a plugin's reports to a list rather than to pick out the display properties for a single report.

@anonymous-matomo-user
Copy link

In 80c4b46: Refs #4040, converted CustomVariables plugin to use display properties instead of manually calling ViewDataTable functions.

@anonymous-matomo-user
Copy link

In d056230: Refs #4040, converted DBStats plugin to use display properties instead of ViewDataTable methods.

@anonymous-matomo-user
Copy link

In a5bbfbf: Refs #4040, convert DevicesDetection plugin to use display properties instead of ViewDataTable methods.

@anonymous-matomo-user
Copy link

In 9b02615: Refs #4040, move Piwik_ViewDataTable::getRawSegmentFromRequest to Piwik_API_Request.

@anonymous-matomo-user
Copy link

In f1dcb45: Refs #4040, converted Live plugin to use display properties instead of ViewDataTable methods.

@anonymous-matomo-user
Copy link

In b298983: Refs #4040, convert Provider plugin to use display properties instead of ViewDataTable methods.

@anonymous-matomo-user
Copy link

In 02e0be4: Refs #4040, converted Referrers plugin to use display properties instead of ViewDataTable methods.

@anonymous-matomo-user
Copy link

In 4e3a67a: Refs #4040, converted UserCountry plugin to use display properties instead of ViewDataTable methods.

@anonymous-matomo-user
Copy link

In 228a6aa: Refs #4040, converted VisitorInterest plugin to use display properties instead of ViewDataTable methods.

@anonymous-matomo-user
Copy link

In edf2c04: Refs #4040, #4041, added ability to access view properties directly, started documenting view properties and modified ExampleUI plugin to set view properties directly.

@anonymous-matomo-user
Copy link

In 0ea1a94: Refs #4040, #4041 convert RowEvolution popup rendering code to set view properties directly.

@anonymous-matomo-user
Copy link

In 13f657c: Refs #4040, #4041, fix sparklines regression caused by datatable css refactoring and clean up the getLastUnitGraphAcrossPlugins function (modified to set properties directly).

@anonymous-matomo-user
Copy link

In 0f61caa: Refs #4040, #4041 removed rest of viewdatatable set/get/enable/disable property functions, did the same for all other ViewDataTable classes, moved most of ViewDataTable/HtmlTable logic to visualization instead of main class and re-add links for UI integration tests.

@anonymous-matomo-user
Copy link

In 883c322: Refs #4040, #4041, move more logic out of HtmlTable ViewDataTable class.

@anonymous-matomo-user
Copy link

In 1a9898b: Refs #4040, #4041, fix regression in default sort column of goals table.

@anonymous-matomo-user
Copy link

In 7519e67: Refs #4040, #4041, move AllColumns ViewDataTable & Goals ViewDataTable logic to HtmlTable visualization class & remove those classes. Revised the way visualizations default/override view properties. Cleaned up the ViewDataTable class a bit. Added base type for datatable visualizations.

@anonymous-matomo-user
Copy link

In b808489: Refs #4040, #4041, remove is_multi_evolution javascript parameter as it is no longer necessary due to earlier row evolution refactoring.

@anonymous-matomo-user
Copy link

In cc92fac: Refs #4040, #4041, remove GenerateGraphHtml & descended ViewDataTables and replace w/ new visualizations for jqplot.

@anonymous-matomo-user
Copy link

In ac3a25c: Refs #4040, #4041, forgot to remove GenerateGraphHTML file.

@anonymous-matomo-user
Copy link

In cf8d0a5: Refs #4041, #4040, moved viewdatatable cloud logic to cloud visualization. Removed cloud viewdatatable.

@anonymous-matomo-user
Copy link

In 2615404: Refs #4040, #4041, move visualization only view properties to separate visualizations, changed JavaScript properties to 'client side parameters' and 'overridable properties' to 'client side properties', changed keep_summary_row from a JavaScript property to a client side property, allowed visualization properties to be inherited, fixed system that allowed visualizations to set custom defaults for property values, modified behavior of datatable_css_class viewdatatable property, allow view properties to be customized in metadata based on the visualization used, and tweaks to UI Integration tests.

@anonymous-matomo-user
Copy link

In 9b5a42a: Refs #4040, #4041, change the way jqplot.js checks for viewdatatble types, changed relatedReports view property name to related_reports and fixed spelling of row_picker_mach_rows_by.

@anonymous-matomo-user
Copy link

In e898bc2: Refs #4040, #4041 add initial code for making datatable visualizations an extensibility point.

@anonymous-matomo-user
Copy link

In 9e19f24: Refs #4041, #4040 add new CoreVisualizations plugin and move HtmlTable, Cloud & JqplotGraph visualizations to it and improve UIIntegration test debug output.

@anonymous-matomo-user
Copy link

In be35dc4: Refs #4040, #4041, removed ViewDataTable::init & moved default property values for core properties to Properties class.

@anonymous-matomo-user
Copy link

In 7daadd4: Refs #4040, #4041 added new plugin ExtraVisualizations with dummy visualization and made it possible for non-core visualizations to appear in DataTable UI footer.

@anonymous-matomo-user
Copy link

In 6f8b40d: Refs #4040, #4041, added documentation to DataTableVisualization class.

@anonymous-matomo-user
Copy link

In 27dcd70: Refs #4040, #4041, removed two-phase rendering for ViewDataTable.

sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…ies to the viewProperties array and allow these properties to be specified through new display metadata. Converted the Actions, Goals, UserSettings and VisitTime controllers.

Notes:
  - Includes refactoring of ExcludeLowPopulation filter.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…y properties for all of a plugin's reports to a list rather than to pick out the display properties for a single report.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
… properties instead of manually calling ViewDataTable functions.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…properties instead of ViewDataTable methods.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…perties instead of ViewDataTable methods.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
… properties instead of ViewDataTable methods.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…roperties directly, started documenting view properties and modified ExampleUI plugin to set view properties directly.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…ering code to set view properties directly.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…ed by datatable css refactoring and clean up the getLastUnitGraphAcrossPlugins function (modified to set properties directly).
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…et/get/enable/disable property functions, did the same for all other ViewDataTable classes, moved most of ViewDataTable/HtmlTable logic to visualization instead of main class and re-add links for UI integration tests.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…& Goals ViewDataTable logic to HtmlTable visualization class & remove those classes. Revised the way visualizations default/override view properties. Cleaned up the ViewDataTable class a bit. Added base type for datatable visualizations.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…script parameter as it is no longer necessary due to earlier row evolution refactoring.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…cended ViewDataTables and replace w/ new visualizations for jqplot.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…c to cloud visualization. Removed cloud viewdatatable.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…roperties to separate visualizations, changed JavaScript properties to 'client side parameters' and 'overridable properties' to 'client side properties', changed keep_summary_row from a JavaScript property to a client side property, allowed visualization properties to be inherited, fixed system that allowed visualizations to set custom defaults for property values, modified behavior of datatable_css_class viewdatatable property, allow view properties to be customized in metadata based on the visualization used, and tweaks to UI Integration tests.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…s for viewdatatble types, changed relatedReports view property name to related_reports and fixed spelling of row_picker_mach_rows_by.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…atable visualizations an extensibility point.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…in and move HtmlTable, Cloud & JqplotGraph visualizations to it and improve UIIntegration test debug output.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…moved default property values for core properties to Properties class.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…tions with dummy visualization and made it possible for non-core visualizations to appear in DataTable UI footer.
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Projects
None yet
Development

No branches or pull requests

3 participants