Closed mohierf closed 5 years ago
@mohierf since this is Alignak specific I let you merge when this is ready.
Hm, no. Do not merge anything in common css or helpers. Please separate what is alignak specify.
There is nothing specific in the branch for the CSS ... this is because you did not yet merged #670 .
Adding a function in helper.py will not break the Shinken version ... but I will make an alignak_helper.py file.
@maethor : I created an alignak_helper.py file for the alignak specific function. This isolates as much as possible the specific code. Note that it still exists some common part in some files but it is not possible to create separate files for everything ....
I don't understand, why do you say "because you did not yet merged #670"? Pull Requests should be independent from each others. Unless there is stuff you need in #670 for this code to work, you should be able to merge this without #670.
Sure, but I was obliged to include a commit from #670 in this PR to avoid a huge mess ... and to be able to continue working independently on both PR
@maethor : I am closing this one and I will re-open a new Alignak specific PR. This one is now quite complicated to maintain because of the most merge and many commits since its inception...
Alignak logs and statistics - first draft as a PoC Some Alignak specific views: livesynthesis, status, events log
1st commit is same as #659 ... needed for Alignak that raises NW broks 3rd commit is same as #670 ... CSS styling for Alignak specific menu