It looks interesting and I've played around with it some --- but the development IDE in a web browser seems to be nightmare eventually.
它看起来很有趣,我已经玩了一些 - 但是网络浏览器中的开发IDE最终似乎是噩梦。
Does anyone have experience using it and what are your thoughts?
有没有人有使用它的经验,你有什么想法?
5 个解决方案
#1
10
We evaluated GI a few months ago for a project but didn't end up selecting it.
几个月前我们对一个项目进行了GI评估,但最终没有选择它。
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.
浏览器中的IDE(它本身是使用GI构建的)实际上运行得非常好,尽管您通常期望编辑器缺少某些功能,尤其是(并且令人恼火)撤销命令。虽然你可以在底层的XML中手动完成子文档包括(实际上是团队开发的必要性),但是也不可能做到这一点,IDE会尊重它们。
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.
最后,我们没有采用它的主要原因是很难使得最终的Web应用程序看起来像设计师真正想要的那样好。构建功能相对容易,但组件的外观和感觉都非常严格。 GI将自己的文档模型呈现为HTML的方式涉及许多样式属性,这使得CSS中的蒙皮几乎不可能。它似乎更喜欢使Web应用程序看起来像应用程序,而不是看起来像网站的Web应用程序。
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.
对于那些不知道的人来说,TIBCO GI是与TIBCO其他SOA业务集成的完全独立的产品 - General Interface是一家独立的公司,几年前被TIBCO收购。
#2
2
From a coworker who used to work at TIBCO:
来自曾经在TIBCO工作的同事:
TIBCO is a complicated, hard to use system because it's used for complicated, hard to solve problems.
TIBCO是一个复杂,难以使用的系统,因为它用于复杂,难以解决的问题。
#3
1
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.
Kieron在总结GI方面做得很好。它实际上适用于企业Web应用程序,而不是消费者小部件。加载整个GI框架并等待一两秒钟进行加载的开销并不大,如果您要启动呼叫中心或将在接下来的几个小时内使用的员工配置应用程序。但是,如果你正在等待一个小部件加载到现有的网页中,它似乎是永远的。而且,即使GI支持一些不错的功能和性能QA工具,除非你正在处理一些重要且复杂的事情,否则它们实在是太过分了。所以,如果你想要的只是在屏幕上抛出性感的日期选择器,那么请确保使用别的东西。
#4
1
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++.
是的,不能同意。我开发了一些使用TIBCO GI的应用程序并将其与TIBCO CIM集成。我为TIBCO和GI工作是我一直在努力做一些复杂的事情。虽然这样做,我遇到了GI的奇怪方面,你有时无法解释的事情,但只是他们的方式,使用JavaScript和处理多线程问题可能是一场噩梦等。快速创建一些东西是好的对于应用程序的性感太过挑剔,因此对内部应用程序有好处,但对消费者却没有,除非你想迷失在疯狂的CSS样式的丛林中。 XML Mapping实用程序是一个很好的功能,可以节省大量时间来实现SOA应用程序。另一个好处是部署非常简单 - GI应用程序结合使用XML,XSLT,X-Path和JavaScript。在GI 3.8中,还有一些测试工具。不幸的是,GI编辑器内部的开发很慢且很痛苦,所以我建议使用像Notepad ++这样的外部编辑器。
#5
1
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-GI,但你需要运行Programfile GI_Builder.exe这是一个ActiveX应用程序。只需双击它并运行它。
#1
10
We evaluated GI a few months ago for a project but didn't end up selecting it.
几个月前我们对一个项目进行了GI评估,但最终没有选择它。
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.
浏览器中的IDE(它本身是使用GI构建的)实际上运行得非常好,尽管您通常期望编辑器缺少某些功能,尤其是(并且令人恼火)撤销命令。虽然你可以在底层的XML中手动完成子文档包括(实际上是团队开发的必要性),但是也不可能做到这一点,IDE会尊重它们。
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.
最后,我们没有采用它的主要原因是很难使得最终的Web应用程序看起来像设计师真正想要的那样好。构建功能相对容易,但组件的外观和感觉都非常严格。 GI将自己的文档模型呈现为HTML的方式涉及许多样式属性,这使得CSS中的蒙皮几乎不可能。它似乎更喜欢使Web应用程序看起来像应用程序,而不是看起来像网站的Web应用程序。
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.
对于那些不知道的人来说,TIBCO GI是与TIBCO其他SOA业务集成的完全独立的产品 - General Interface是一家独立的公司,几年前被TIBCO收购。
#2
2
From a coworker who used to work at TIBCO:
来自曾经在TIBCO工作的同事:
TIBCO is a complicated, hard to use system because it's used for complicated, hard to solve problems.
TIBCO是一个复杂,难以使用的系统,因为它用于复杂,难以解决的问题。
#3
1
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.
Kieron在总结GI方面做得很好。它实际上适用于企业Web应用程序,而不是消费者小部件。加载整个GI框架并等待一两秒钟进行加载的开销并不大,如果您要启动呼叫中心或将在接下来的几个小时内使用的员工配置应用程序。但是,如果你正在等待一个小部件加载到现有的网页中,它似乎是永远的。而且,即使GI支持一些不错的功能和性能QA工具,除非你正在处理一些重要且复杂的事情,否则它们实在是太过分了。所以,如果你想要的只是在屏幕上抛出性感的日期选择器,那么请确保使用别的东西。
#4
1
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++.
是的,不能同意。我开发了一些使用TIBCO GI的应用程序并将其与TIBCO CIM集成。我为TIBCO和GI工作是我一直在努力做一些复杂的事情。虽然这样做,我遇到了GI的奇怪方面,你有时无法解释的事情,但只是他们的方式,使用JavaScript和处理多线程问题可能是一场噩梦等。快速创建一些东西是好的对于应用程序的性感太过挑剔,因此对内部应用程序有好处,但对消费者却没有,除非你想迷失在疯狂的CSS样式的丛林中。 XML Mapping实用程序是一个很好的功能,可以节省大量时间来实现SOA应用程序。另一个好处是部署非常简单 - GI应用程序结合使用XML,XSLT,X-Path和JavaScript。在GI 3.8中,还有一些测试工具。不幸的是,GI编辑器内部的开发很慢且很痛苦,所以我建议使用像Notepad ++这样的外部编辑器。
#5
1
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-GI,但你需要运行Programfile GI_Builder.exe这是一个ActiveX应用程序。只需双击它并运行它。