Modularizing the Dashboard (Page 1 of 4)

Yes, sure @notrinos. We could do it better. Feel free to experiment. What I would like is that we could change the diagrams,  the constants inside the diagrams etc. But remember that we should not convert to Google api. They can not be used for Arabic countries.

So go ahead and be creative ????

Joe

Yes, I like jquery too, but haven't considered it useful for FA. I guess I will discuss it with Janusz.

Joe

Current javascript support in FA is sufficient for most needs, so I have not considered adding big js libraries like jquery to the main code. But if you want to have some functions which would be hard to implement in plain javascript, I'm not entirely against including jquery, providing the new code would be handy to use in other parts of FA interface.

When considering inclusion of javascript libraries one thing have to be guaranteed for sure: all the library code have to be included in FA distribution i.e. no external references to e.g. google apis, or other online js repos is allowed. This is because FA in many cases is installed on LANs with no access to internet for many reasons including security.

Janusz

JQuery can be an extension by itself. Other extensions can then depend on this or install it as a pre-requisite where absent with an alert.

Hello

Here is the modification for a customizable dashboard system

- One current core file to be modified: /admin/dashboard.php
- One folder to be added to the root folder: /dashboards
- In this new folder dashboards the build in widgets would be placed there
- For custom dashboard, developer should create a folder named dashboards in his extension folder then put here a file named custom_dashboards.php. To add new dashboard and widgets would require this file' contents like this:

define('DA_HRM', 'FrontHrm');

$dashboard->addDashboard(_('HRM'), DA_HRM);
$dashboard->addWidget(DA_HRM, 997, _('Widget name 1'), WIDGET_HALF);
$dashboard->addWidget(DA_HRM, 998, _('Widget name 2'), WIDGET_HALF);
$dashboard->addWidget(DA_HRM, 999, _('Widget name 3'), WIDGET_FULL);
...

This is a rough sketch for what I have proposed.
Following this method users can decide which widget, chart would be shown on their dashboard.
I have been doing this by simulating the Report System.
Jquery and any Js, charts libraries could be included later

Thank you

ps: also need few more new css lines

div.widget_title {
    font-weight: bold;
    color: #555;
    font-size: 1.3em;
    width: 100%;
    border-bottom: 1px solid #DDD;
    padding: 5px 0;
    margin-bottom: 5px;
}

div.widget {
    border: 1px solid #DDD;
    background: #FFF;
    padding: 0 10px;
    margin: 10px 0;
    box-sizing: border-box;
    display: inline-block;
    float: left;
    height: 23em;
    overflow: auto;
}

div.widget_full {
    width: calc(100% - 40px);
    margin-left: 20px;
}

div.widget_half {
    width: calc(50% - 30px);
    margin-left: 20px ;
}

@kvvaradha
Just like the Report Extensions, a hook class is not necessary
Can write anything tables, graphs, charts in the custom widgets
You can even add your custom chart library to write a dynamic chart

@boxygen,

Yes, i agree. I am just waiting for @notrinos suggestions about what to change in the core to help modularizing the Dashboard.

@boxygen, @notrinos and @apmuthu.

Thank you for your creative coop in this and other matters.

/Joe

Any update on this @notrinos?

Hello everyone, thank you so much for your responses
Here is the completed code for this modification.
After unzip the attachment we will need to replace one core file: admin/dashboard.php and copy every files in the reporting folder to the coresponding places.
Also need to copy the css contents to every theme we have.

We need new css codes because I used DIV tags to replace the current structure which has been built on tables structure, gradual replacement of tables to DIV tags would create future advantages when building responsive themes.

With this new dashboard system the current file includes/dashboard.inc can be removed.

DOWNLOAD

Thank you all

Great .

@apmuthu. I don't know yet.
You should address this question to @notrinos.
I don't have the complete picture yet.

Joe

@notrinos: You have placed a lot of widgets php files in the reporting folder - should they not be in a separate folder?

If some common css is needed for every theme, should they not be in a separate include file?