Themes



Reportico provides a theme() method to change the overall look and feel. Reportico contains theme files (stylesheets, HTML templates, javascript etc) under the theme in Reportico. To switch theme just provide this folder name to the theme method.

Reportico comes with two themes bootstrap3 and bootstrap4 (the default used in standalone Reportico and when embedding in frameworks such as Laravel) but it is possible to copy these to a new theme and change the look and feel. Since Reportico can be embedded in existing web applications and work with existing visual frameworks such as Boostrap, the theme folder defines the framework specific logic for embedding reports.

For more details on themes and creating your own visit the Reportico documentation on themes



<?php
      \Reportico\Engine\Builder::build()
          ...
          ->theme("theme_folder")
          ...
          ->execute();
?>
 1


This example shows a report running in the bootstrap3 theme.

Run Demo


<?php

     require_once(__DIR__ .'/../vendor/autoload.php');
     

     \Reportico\Engine\Builder::build()
          ->datasource()->database("mysql:host=localhost; dbname=DATABASE NAME")->user("USER")->password("PASSWORD")
          ->title     ("Employee List")
          ->description     ("Produces a list of our employees")

          // The sql for the main report makes reference to 4 criteria items specified further below.
          // The value between the {curly braces} links in the criteria item by name and is replaced at report time
          // by the users selected values. Where a criteria selections are generated from a lookup, the values come from the criteria
          // return() column.
          //
          // For criteria items that are ranges e.g. date or time ranges, specifiying {criteriarange} expands to a BETWEEN/AND clause and to
          // access the lower and upper range selections use {criteriarange,from} and {criteria,to}
          //
          // For multiselects, it is often appropriate to use the SQL IN () syntax so that IN ({criteria}) is replaced by 
          // IN ( \'selection1\', \'selection2\', ... )
          //
          // By default the values plugged into the SQL are surrounded by quotes and smetimes you need to plug into the SQL selections
          // which have no quotes, for example with the match string example below where you want to surround the selection with % signs to
          // perform and SQL LIKE operation. In this case use false as the final parameter for example {criteria,false} or with a range 
          // {daterange,from,false}
          ->sql       ("
                SELECT EmployeeID employee_id, LastName last_name, FirstName first_name, date(BirthDate) birth_date, Country, BirthDate
                FROM northwind_employees
                WHERE 1 = 1
                [ AND Country IN ( {country} ) ]
                [ AND DATE(BirthDate) BETWEEN {born,from} AND {born,to} ]
                [ AND ( LastName like '%{namematch,false}%' OR FirstName like '%{namematch,false}%' ) ]
                [ AND ( EmployeeID in ( {namemulti} ) ) ]
                ORDER BY Country, LastName
                ")

          // This criteria generates a multiselect list box from an SQL statement
          // giving a list of countries. The "country" column is displayed in the box and 
          // also returned in the return() method which matches the {country} reference in the main SQL. 
          // The {country} specifier in the main query will be replaced by the selected countries
          ->criteria("country")
            ->title("Country")
            ->type("lookup")
            ->sql("SELECT DISTINCT Country country FROM northwind_employees")
            ->widget("multi")
            ->return("country")
            ->display("country", "country")
            ->match("country")

          ->theme("bootstrap3")
          ->prepare();
?>