I'm starting with Dashboard product. You will see that I have added a bunch of questions in the forums. But now I'm thinking about it and I'm not sure the Dashboard deservers my time anymore.

It looks like it have a bunch of classes extending classes from Koolreport and adding complexity at the same time it remove some functionality from it.

Before to start looking at it, I was planning in use some reports from Dashboard inside another product, to facilitate the report info exchange. If it was pure Koolreport it would be a peace of cake to archive it, But now, I'm seeing that reports inside dashboard are created with its own classes that only exist inside of it, thus removing the reusability of the generated reports outside of Dashboard world.

After my thoughts above, a very simple question follows...

Is it possible to use the Dashboard as a layout only app and use pure Koolreport reports and charts under it?

Ie, instead of a MyTable like:

use \koolreport\dashboard\widgets\Table;

class MyTable extends Table
{
    protected function dataSource()
    {
        ...

do something more like a MyTable.php and MyTable.view.php:

class MyReport extends \koolreport\KoolReport
{
    function settings()
    {
        return array(
            "dataSources"=>array(
                "automaker"=>array(

use \koolreport\widgets\koolphp\Table;

Table::create(array(
        "dataSource"=>$this->dataStore("users"),
        "showFooter"=>true,
        "columns"=>array(
            ...

And still be able to use it inside MyBoard.php layout and do things like connect a chart selection to a table filter, for example?

class MyBoard extends Dashboard
{
    protected function widgets()
    {
        return [ MyTable::create() ]

Effectively having the 3 pure files index.php, MyTable.php and MyTable.view.php and call it inside MyBoard somehow.

As I see, if it is possible without too much of trouble, I could keep using Dashboard cool layout widgets without losing Koolreport DataTable, Export and all the easy and cool of pure Koolreport.

Thank you in advance.

I realise that I may have sounded harsh than I meant to be (language barrier). I just felt the other way around, that Koolreport was easier to get along than Dashboard, but I understand what kind of easy you are talking about.

I guess that what I saw as complexibility was all the abstraction that Dashboard is doing so we can write less code, and what I saw as limitation was, basically, the Table lack of CSV export, I see now.

I guess I gonna try a little with KWidget now. I just hope that KWidget don't bring any negative side effect or limitation to Dashboard as a hole.

Thank you.