是的，完全同意。 我使用 TIBCO GI 开发了一些应用程序，并将其与 TIBCO CIM 集成。 我在 TIBCO 工作，而 GI 是我一直在做的一些复杂的事情。 在做的过程中，我遇到了 GI 的奇怪方面，有时你无法解释的事情，但它们就是这样，使用 JavaScript 和处理多线程问题可能是一场噩梦等等。快速创建一些东西而不是被对应用程序的性感过于挑剔，因此对内部应用程序有利，但对消费者不利，除非你想迷失在疯狂的 CSS 样式丛林中。 XML 映射实用程序是一项出色的功能，可以节省您实施 SOA 应用程序的大量时间。 另一个好处是部署非常简单 - GI 应用程序使用 XML、XSLT、X-Path 和 JavaScript 的组合。 GI 3.8 中还有一些测试工具。 不幸的是，在 GI 编辑器内进行开发既缓慢又痛苦，因此我建议使用像 Notepad++ 这样的外部编辑器。
Yup, couldn't agree more. I have developed a few applications with TIBCO GI and integrated it with TIBCO CIM. I work for TIBCO and GI is something I have been working with quite heavily doing some complicated stuff. Whilst doing it, I came across the odd sides of GI, things you sometimes can't explain but are just the way they are, working with JavaScript and dealing with multithreading issues can be a nightmare etc. It's good to create something quick without being too fussy about the sexiness of the application hence good for internal apps but not for consumers unless you want to get lost in a jungle of crazy CSS styling. The XML Mapping utility is a great feature saving you lots of time to implement SOA applications. The other good part is that deployment is really easy - GI apps use a combination of XML, XSLT, X-Path and JavaScript. In GI 3.8 there are also a couple of testing tools. Unfortunately, development inside GI's editor is slow and painful, so I recommend using an external editor like Notepad++.
您不需要从 Web 浏览器运行 tibco-GI，但需要运行 Programfile GI_Builder.exe，它是一个 ActiveX 应用程序。 只需双击它并运行它。
you dont need to run tibco-GI from a web-browser, but you need to run the Programfile GI_Builder.exe which is an ActiveX application. just double-click on it and run-it.
Kieron 对 GI 的总结做得很好。 它确实适用于企业 Web 应用程序，而不是消费者小部件。 如果您要启动接下来几个小时要使用的呼叫中心或员工供应应用程序，那么加载整个 GI 框架并等待一两秒加载的开销似乎并不多。 但是，如果您正在等待小部件加载到现有网页中，那么这似乎是永远的。 而且，尽管 GI 支持一些不错的功能和性能 QA 工具，但除非您正在处理重要且复杂的事情，否则它们确实有点过分了。 因此，如果您只想在屏幕上显示一个看起来性感的日期选择器，那么一定要使用其他东西。
Kieron does a good job of summarizing GI. It's really for enterprise web applications, not consumer-y widgets. The overhead of loading the entire GI framework and waiting a second or two for it to load doesn;t seem like much if you're firing up a call center or an employee provisioning application you're going to use for the next few hours. But, it seems like forever if you're waiting for a widget to load into an existing web page. And, even though, GI supports some nice functional and performance QA tools, they really are overkill unless you're working on something important and complex. So, if all you want is to toss a sexy looking datepicker on screen, use something else for sure.
浏览器中的 IDE（本身是用 GI 构建的）实际上运行得非常好，尽管它缺少一些您通常期望从编辑器中获得的功能，最值得注意的是（并且令人恼火的是）撤消命令。 尽管您可以在底层 XML 中手动执行这些操作并且 IDE 会尊重它们，但从 IDE 中也不可能执行诸如子文档包含之类的操作（实际上是团队开发所必需的）。
最后我们没有采用它的主要原因是很难使最终的 Web 应用程序看起来像设计师真正想要的那样好。 构建功能相对容易，但组件在外观和感觉上非常有限。 GI 将其自己的文档模型呈现为 HTML 的方式涉及大量 style 属性，这使得 CSS 中的换肤几乎不可能。 它似乎更喜欢制作看起来像应用程序的 Web 应用程序，而不是看起来像网站的 Web 应用程序。
顺便说一句，对于那些不知道的人来说，TIBCO GI 是一个完全独立于 TIBCO 的其他 SOA 业务集成产品的产品 - General Interface 是一家独立的公司，几年前被 TIBCO 收购。
We evaluated GI a few months ago for a project but didn't end up selecting it.
The IDE-in-a-browser (which is itself build with GI) actually works surprisingly well, though there are some features you normally expect from an editor that it lacks, most notably (and irritatingly) an Undo command. It's also impossible to do things like subdocument includes (practically a necessity for team development) from the IDE, though you can do them manually in the underlying XML and the IDE will respect them.
In the end the main reason we didn't go with it was that it was difficult to make the resulting web application look as good as the designers really wanted. It was relatively easy to build functionality, but the components were very restrictive in look and feel. The way GI renders its own document model to HTML involves a lot of style attributes which makes skinning in CSS all but impossible. It seems to prefer making web applications that look like applications, instead of web applications that look like websites.
So it would probably be great for building intranet type applications where look and feel isn't a huge issue, but I probably wouldn't use it to make a public facing site.
By the way for those that don't know, TIBCO GI is a completely separate product from the rest of TIBCO's SOA business integration stuff - General Interface was a separate company that was acquired by TIBCO a couple of years ago.
发布评论
评论（5）
是的，完全同意。 我使用 TIBCO GI 开发了一些应用程序，并将其与 TIBCO CIM 集成。 我在 TIBCO 工作，而 GI 是我一直在做的一些复杂的事情。 在做的过程中，我遇到了 GI 的奇怪方面，有时你无法解释的事情，但它们就是这样，使用 JavaScript 和处理多线程问题可能是一场噩梦等等。快速创建一些东西而不是被对应用程序的性感过于挑剔，因此对内部应用程序有利，但对消费者不利，除非你想迷失在疯狂的 CSS 样式丛林中。 XML 映射实用程序是一项出色的功能，可以节省您实施 SOA 应用程序的大量时间。 另一个好处是部署非常简单 - GI 应用程序使用 XML、XSLT、X-Path 和 JavaScript 的组合。 GI 3.8 中还有一些测试工具。 不幸的是，在 GI 编辑器内进行开发既缓慢又痛苦，因此我建议使用像 Notepad++ 这样的外部编辑器。
Yup, couldn't agree more. I have developed a few applications with TIBCO GI and integrated it with TIBCO CIM. I work for TIBCO and GI is something I have been working with quite heavily doing some complicated stuff. Whilst doing it, I came across the odd sides of GI, things you sometimes can't explain but are just the way they are, working with JavaScript and dealing with multithreading issues can be a nightmare etc. It's good to create something quick without being too fussy about the sexiness of the application hence good for internal apps but not for consumers unless you want to get lost in a jungle of crazy CSS styling. The XML Mapping utility is a great feature saving you lots of time to implement SOA applications. The other good part is that deployment is really easy - GI apps use a combination of XML, XSLT, X-Path and JavaScript. In GI 3.8 there are also a couple of testing tools. Unfortunately, development inside GI's editor is slow and painful, so I recommend using an external editor like Notepad++.
您不需要从 Web 浏览器运行 tibco-GI，但需要运行 Programfile GI_Builder.exe，它是一个 ActiveX 应用程序。 只需双击它并运行它。
you dont need to run tibco-GI from a web-browser, but you need to run the Programfile GI_Builder.exe which is an ActiveX application. just double-click on it and run-it.
来自曾经在 TIBCO 工作的同事：
From a coworker who used to work at TIBCO:
Kieron 对 GI 的总结做得很好。 它确实适用于企业 Web 应用程序，而不是消费者小部件。 如果您要启动接下来几个小时要使用的呼叫中心或员工供应应用程序，那么加载整个 GI 框架并等待一两秒加载的开销似乎并不多。 但是，如果您正在等待小部件加载到现有网页中，那么这似乎是永远的。 而且，尽管 GI 支持一些不错的功能和性能 QA 工具，但除非您正在处理重要且复杂的事情，否则它们确实有点过分了。 因此，如果您只想在屏幕上显示一个看起来性感的日期选择器，那么一定要使用其他东西。
Kieron does a good job of summarizing GI. It's really for enterprise web applications, not consumer-y widgets. The overhead of loading the entire GI framework and waiting a second or two for it to load doesn;t seem like much if you're firing up a call center or an employee provisioning application you're going to use for the next few hours. But, it seems like forever if you're waiting for a widget to load into an existing web page. And, even though, GI supports some nice functional and performance QA tools, they really are overkill unless you're working on something important and complex. So, if all you want is to toss a sexy looking datepicker on screen, use something else for sure.
几个月前，我们评估了一个项目的 GI，但最终没有选择它。
浏览器中的 IDE（本身是用 GI 构建的）实际上运行得非常好，尽管它缺少一些您通常期望从编辑器中获得的功能，最值得注意的是（并且令人恼火的是）撤消命令。 尽管您可以在底层 XML 中手动执行这些操作并且 IDE 会尊重它们，但从 IDE 中也不可能执行诸如子文档包含之类的操作（实际上是团队开发所必需的）。
最后我们没有采用它的主要原因是很难使最终的 Web 应用程序看起来像设计师真正想要的那样好。 构建功能相对容易，但组件在外观和感觉上非常有限。 GI 将其自己的文档模型呈现为 HTML 的方式涉及大量
style属性，这使得 CSS 中的换肤几乎不可能。 它似乎更喜欢制作看起来像应用程序的 Web 应用程序，而不是看起来像网站的 Web 应用程序。因此，它可能非常适合构建内部网类型的应用程序，其中外观和感觉不是一个大问题，但我可能不会使用它来创建面向公众的网站。
顺便说一句，对于那些不知道的人来说，TIBCO GI 是一个完全独立于 TIBCO 的其他 SOA 业务集成产品的产品 - General Interface 是一家独立的公司，几年前被 TIBCO 收购。
We evaluated GI a few months ago for a project but didn't end up selecting it.
The IDE-in-a-browser (which is itself build with GI) actually works surprisingly well, though there are some features you normally expect from an editor that it lacks, most notably (and irritatingly) an Undo command. It's also impossible to do things like subdocument includes (practically a necessity for team development) from the IDE, though you can do them manually in the underlying XML and the IDE will respect them.
In the end the main reason we didn't go with it was that it was difficult to make the resulting web application look as good as the designers really wanted. It was relatively easy to build functionality, but the components were very restrictive in look and feel. The way GI renders its own document model to HTML involves a lot of
styleattributes which makes skinning in CSS all but impossible. It seems to prefer making web applications that look like applications, instead of web applications that look like websites.So it would probably be great for building intranet type applications where look and feel isn't a huge issue, but I probably wouldn't use it to make a public facing site.
By the way for those that don't know, TIBCO GI is a completely separate product from the rest of TIBCO's SOA business integration stuff - General Interface was a separate company that was acquired by TIBCO a couple of years ago.