You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
Created by mfriedrich on 2013-03-03 16:41:10 +00:00
Assignee: (none)
Status: Rejected (closed on 2015-05-01 12:51:50 +00:00)
Target Version: (none)
Last Update: 2015-05-01 12:51:50 +00:00 (in Redmine)
inGraph adds serverside rendering with nodejs, so those images may be included with the jasperreport templates as well.
though, it should be made fully optional, as we cannot expect that everyone has inGraph installed.
depending on #3742 those reports should be added within "ingraph" or similar below "reports" in the directory tree.
since is something which may depend on a.) inGraph 1.2 with better nodejs integration and b.) re-organisation of files and templates, this is targetted for the 1.10 release.
This issue has been migrated from Redmine: https://dev.icinga.com/issues/3743
Created by mfriedrich on 2013-03-03 16:41:10 +00:00
Assignee: (none)
Status: Rejected (closed on 2015-05-01 12:51:50 +00:00)
Target Version: (none)
Last Update: 2015-05-01 12:51:50 +00:00 (in Redmine)
inGraph adds serverside rendering with nodejs, so those images may be included with the jasperreport templates as well.
though, it should be made fully optional, as we cannot expect that everyone has inGraph installed.
depending on #3742 those reports should be added within "ingraph" or similar below "reports" in the directory tree.
since is something which may depend on a.) inGraph 1.2 with better nodejs integration and b.) re-organisation of files and templates, this is targetted for the 1.10 release.
Relations:
The text was updated successfully, but these errors were encountered: