如何为所有 Cognos 10 报表创建全局样式？

发布于 2024-10-20 20:08:44 字数 724 浏览 4 评论 0原文

我的团队一直致力于创建仪表板和钻取报告。我们已经过了概念验证阶段，现在正在努力构建“生产就绪”报告。在我们的会议中，有人提出应该更改 Cognos 默认设置的报告整体样式。

我们开始了解 Cognos 的皮肤系统。我们看到报表显示和门户中使用的门户和 UI 元素有皮肤。这不一定是我们想要的。我们理想地希望能够更改公司品牌的门户并更改列表和交叉表的外观（以及实际报告的其他元素）。

我能够查看为报告生成的页面源，发现它包含来自以下位置的样式：

cognos\c10_64\webcontent\schemas

在浏览 webcontent 目录时，我还发现了此路径：

cognos\c10_64\webcontent\reportstyles

这两个路径都包含具有相似名称的 css 文件。报告 HTML 包含的样式指向“schemas”目录，但是我的逻辑思维自己愿意相信“reportstyles”目录在 Cognos 报告显示中的某个位置使用，即使我没有看到它包含在任何页面源中我看过。

我已经开始使用包含的 css 文件的系统对“模式”路径中的 css 进行修改，将其中的 css 复制出来并将其放入“xxx_system.css”文件中，然后将该文件包含在原始CSS文件。

这个过程有效，我们能够看到变化，但我们仍然想知道是否有更好或“更正确”的方法来做到这一点。任何人都可以详细说明对实际报告进行皮肤/样式设置的最佳方法吗？

原文

My team has been working with creating dashboards and drill-through reports. We've moved past our proof-of-concept phase and are now working to build the "production ready" reports. In our meetings it has been brought up that the overall styles for the reports should be changed from the Cognos defaults.

We became aware of Cognos's skin system. We saw that there was skinning for the portal and UI elements that are used within the report display and portal. This is not necessarily what we wanted. We ideally wanted to be able to change the portal to company branding AND change the way lists and crosstabs looked (as well as other elements of the actual report).

I was able to look at the page source generated for a report and saw that it is including styles from:

cognos\c10_64\webcontent\schemas

While poking around the webcontent directory I also found this path:

cognos\c10_64\webcontent\reportstyles

Both of these paths contain css files with similar names. The included styles for the report HTML point to the "schemas" directory, however my logical thinking self would like to believe that the "reportstyles" directory is used somewhere within the Cognos report display even though I have not seen it included in any page source I have viewed.

I have begun making my modifications to the css in the "schemas" path using a system of taking the included css file, copying the css out of it and placing it into a "xxx_system.css" file, and then including that file in the original css file.

This process works and we are able to see the changes, but we are still wondering if there is a better or "more correct" way of doing this. Can anyone elaborate on the best way to skin/style the actual reports?

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

把梦留给海 2024-10-27 20:08:44

我定制 UI 的方法明显不同 - 想象一下我进入一家公司，他们已经做了同样的事情 6 年多了，我想开始改变周围的一切。但遇到了一些阻力，所以我希望我的经验可以帮助您入门。

我拥有强大的基于 UI 的背景，并且立即想将我的知识贡献给我们正在设计的报告。这需要机智，因为我想展示精心设计的 UI 的价值，而不会让每个使用它的人感到震惊/害怕（改变逆境等）。我通过在报告中工作来处理这个问题，而不是在 Cognos 文件本身上。

当你开始使用核心文件的那一刻，无论它们是 CSS、Javascript 还是 CGI 本身，都会立即面临明显的风险，即升级时会完全崩溃。我通过在报告中创建 HTML 项目并从那里调用资源来解决这个问题。例如，这个 HTML 项目几乎存在于我的报告的每个标题中：

<link type="text/css" href="cognos8/common/css/ui-lightness/jquery-ui-1.8.5.custom.css" rel="Stylesheet" />
<link type="text/css" href="custom.css" rel="Stylesheet" />
<script type="text/javascript"
 src="https://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>
<script type="text/javascript"
 src="https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.5/jquery-ui.min.js"></script>
<script type="text/javascript">
jQuery.noConflict();
jQuery(document).ready(function() {
}); // End Ready
</script>

所以现在我可以访问 jQuery、UI 框架和其他所有内容。我在 custom.css 中指定覆盖并从那里构建我的外观。这可能看起来很麻烦，但 IBM 有升级主要版本并完全消除命名约定和功能的诀窍，因此如果您的 CSS 选择器关闭，它会“默认”为 IBM 的原始样式。

这就是我必须解决的方法，但我不确定这是否是最好的方法。我一直在使用我所拥有的东西，即无法访问服务器文件或类似的东西。只是认为这是一种超级安全的方法。

My approach to customizing the UI is significantly different - imagine me coming into a company where they've been doing the same thing for 6+ years and I want to start changing everything around. It was met with some resistance, so I hope my experience can help you get started.

I come from a strong UI-based background and immediately wanted to contribute my knowledge to the reports we were designing. That required tact, as I wanted to show the value of a well-designed UI without shocking/scaring everyone that uses it (change adversity and the like). I handled this by working within the reports, not on the Cognos files themselves.

The minute you start working with the core files, whether they be CSS, Javascript, or CGI itself, there's an immediate and glaring risk that it will entirely break on upgrade. I got around this by creating HTML items in my reports and calling resources from there. For example, this HTML item is in virtually every header of my reports:

<link type="text/css" href="cognos8/common/css/ui-lightness/jquery-ui-1.8.5.custom.css" rel="Stylesheet" />
<link type="text/css" href="custom.css" rel="Stylesheet" />
<script type="text/javascript"
 src="https://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>
<script type="text/javascript"
 src="https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.5/jquery-ui.min.js"></script>
<script type="text/javascript">
jQuery.noConflict();
jQuery(document).ready(function() {
}); // End Ready
</script>

So now I've got access to jQuery, the UI Framework, and everything else. I specify overrides in my custom.css and build my look from there. This might seem cumbersome, but IBM has a knack for upgrading major versions and completely wiping out naming conventions and functions, so if your CSS selector is off, it "defaults" to IBM's original style.

This is just how I've had to get around it and I'm not sure entirely that it's the best way. I've been working with what I have, which is no access to the server files or anything like that. Just consider this a super-safe approach.

回复收藏 0 原文