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
Comments
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. |
…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.
…y properties for all of a plugin's reports to a list rather than to pick out the display properties for a single report.
… properties instead of manually calling ViewDataTable functions.
…ies instead of ViewDataTable methods.
…properties instead of ViewDataTable methods.
…est to Piwik_API_Request.
… instead of ViewDataTable methods.
…es instead of ViewDataTable methods.
…rties instead of ViewDataTable methods.
…perties instead of ViewDataTable methods.
… properties instead of ViewDataTable methods.
…roperties directly, started documenting view properties and modified ExampleUI plugin to set view properties directly.
…ering code to set view properties directly.
…ed by datatable css refactoring and clean up the getLastUnitGraphAcrossPlugins function (modified to set properties directly).
…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.
…le ViewDataTable class.
… column of goals table.
…& 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.
…script parameter as it is no longer necessary due to earlier row evolution refactoring.
…cended ViewDataTables and replace w/ new visualizations for jqplot.
…c to cloud visualization. Removed cloud viewdatatable.
…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.
…s for viewdatatble types, changed relatedReports view property name to related_reports and fixed spelling of row_picker_mach_rows_by.
…atable visualizations an extensibility point.
…in and move HtmlTable, Cloud & JqplotGraph visualizations to it and improve UIIntegration test debug output.
…moved default property values for core properties to Properties class.
…tions with dummy visualization and made it possible for non-core visualizations to appear in DataTable UI footer.
…leVisualization class.
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.
The text was updated successfully, but these errors were encountered: