丰富的互联网应用解决方案

发布于 2024-07-19 07:17:53 字数 286 浏览 8 评论 0原文

我正在评估在下一个项目中使用的富互联网应用程序解决方案。 我听说过以下解决方案 -

  1. Adob​​e Flex
  2. extJS
  3. Jboss Richfaces
  4. IceFaces
  5. Oracle ADF
  6. JavaFX
  7. Silverlight
  8. GWT

我想知道是否有更多可用的解决方案。

如果您能对上述解决方案提供任何有价值的反馈,我将不胜感激。

I am evaluating Rich Internet application solutions to use in next project. I have heard of following solutions -

  1. Adobe Flex
  2. extJS
  3. Jboss Richfaces
  4. IceFaces
  5. Oracle ADF
  6. JavaFX
  7. Silverlight
  8. GWT

I want to know if there are more solutions available.

I would appreciate if you can provide any valuable feedback on the above solutions.

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

扫码二维码加入Web技术交流群

发布评论

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

评论(3

风和你 2024-07-26 07:17:53

IT Mill Toolkit 是一个构建在 GWT 之上的“服务器驱动”框架。

评论:由于我对 PHP 和 Java 怀有很大的敌意,我发现 Toolkit 使用起来非常愉快且快速。 考虑到您在代码中所做的更改会立即反映在您在浏览器中看到的内容这一事实,能够只编写(强类型的、面向对象的)Java 是很好的。

设置起来有点棘手,但 IT Mill 有一个 Eclipse 插件,据说可以帮助解决这个问题。 唯一的问题是插件本身使用起来有点不直观:)

0.02€

回复评论: GWT 和 IMT 之间最大的区别是 GWT 完全在浏览器内部运行(一个敌对/可利用的环境)例如 FireBug),而 IMT 仅使用 GWT 来呈现服务器端状态。 因此,虽然您可以使用 GWT 和 IMT 在浏览器中编辑所需的任何值,但 GWT 会很乐意接受用户编辑的变量值,IMT 会在服务器端跟踪这些值,并且不允许客户端之间存在任何差异和服务器。

另一个很大的区别是,每次对 GWT 小部件进行任何更改时,都需要使用相对耗时的 GWT 交叉编译器(将 Java 编译为 JavaScript)进行编译。 另一方面,IMT 只需要重新部署到 servlet 容器,并且更改就在那里,因为 IMT 内的 GWT 小部件不需要重新编译。 对于 Tomcat,它几乎是瞬时的(即,一旦 Tomcat 注意到 Eclipse 已即时重新编译了类)。

@the_drow:不熟悉 Dijit,这里有一个答案:Dojo 仅是 javascript,这意味着它仅是客户端。 Vaadin(原名 IT Mill Toolkit)也部​​分位于服务器端(称为“服务器驱动”),因此您无法仅通过更改 JavaScript 变量值来破解客户端。 有图表将 Vaadin 与其他同类产品进行比较。 不包括 Dojo,但包括 JQuery,这与 Dojo 有点相似

IT Mill Toolkit is a "server-driven" framework built on top of GWT.

Comment: coming from a heavy PHP and Java-hostile background, I found Toolkit to be very pleasing to use pretty quickly. Being able to write nothing but (the strongly typed, nicely OO-oriented) Java is nice, considering the fact that what you change in the code is pretty instantially reflected on what you see in the browser.

It's a bit tricky to set up, but IT Mill has an Eclipse plugin that supposedly helps with that. The only thing is that the plugin itself is a tad unintuitive to use :)

0.02€

Reply to comment: The biggest difference between GWT and IMT is that GWT operates entirely inside the browser (a hostile/exploitable environment with e.g. FireBug), while IMT uses GWT only to render the server-side state. So, while you can edit any values you want in the browser with both GWT and IMT, GWT will happily accept the user-edited variable values, IMT keeps track on the values server-side, and doesn't allow any discrepancies between the client and server.

Another big difference is that GWT widgets need to be compiled every time you do any changes to them with the relatively time consuming GWT cross-compiler (compiles Java to JavaScript). IMT, on the other hand, needs only to be redeployed to the servlet container, and the changes are there, because the GWT widgets inside IMT don't need to be recompiled. With Tomcat, it's virtually instantaneous (i.e. as soon as Tomcat notices that Eclipse has recompiled the classes on the fly).

@the_drow: Not being familiar with Dijit, here's an answer: Dojo is javascript only, meaning it's client side only. Vaadin (née IT Mill Toolkit) lives partly in the server side too (calls itself "server driven"), so you can't hack the client side just by changing JavaScript variable values. There's a chart that compares Vaadin with other comparable products. Dojo isn't included, but JQuery is, which is vaguely similar to Dojo

妄想挽回 2024-07-26 07:17:53

我有过使用 Spring Webflow + Rich Faces 的经历,结果好坏参半——在屏幕上显示结果的时间确实很短,但微调演示部分很痛苦。

即如果您正在构建一些面向技术的/后端
/standard GUIs - 没关系,如果你要构建一个供数百万 web2.0-ers 使用的前端,你最终会弄乱演示部分 css/javascript 。

i had an experience with Spring Webflow + Rich Faces with mixed results - time to get the results on screen is really short, but it's pain to fine tune the presentation part.

ie if you are building some tech oriented/backend
/standard GUIs - it's ok, if you are going to build a frontend used by millions web2.0-ers you end up messing with presentation part css/javascript big time.

江南月 2024-07-26 07:17:53

在评估和阅读各种RIA解决方案后,我最终选择了GWT和GWT-Ext。 我看到了这些对我和我的团队的好处 -

  1. 我们已经习惯了 Eclipse,所以这是一个优势。
  2. 在 Eclipse 中使用 Java 调试器的能力非常有帮助。
  3. Eclipse 中的 GWT 托管模式,因此每次更改都不需要编译和部署。
  4. 大型开发人员社区
  5. 许多现成可用的组件
  6. 先前的 Java 知识很有帮助
  7. 与 swing 类似,团队在早期项目中也曾研究过 Swing。
  8. 外观也不错,
  9. 还提供 Maven 支持。
  10. 可以编写Junit测试用例。
  11. 除了 Java 之外,不需要其他语言知识。
  12. 基于注释的简单 RPC 配置。

After evaluating and reading various RIA solutions, I have finally selected GWT and GWT-Ext. I see these benefits for me and my team -

  1. We are used to Eclipse so this is an advantage.
  2. Ability to use Java Debugger in Eclipse is extremely helpful.
  3. GWT Hosted mode in eclipse, so no compile and deploy required on every change.
  4. Big developer community
  5. Lots of ready to use components
  6. Prior Java knowledge helpful
  7. Similar to swing and the team have worked on Swing in earlier project.
  8. Look and feel is also good
  9. Maven support is also available.
  10. Can write Junit test cases.
  11. No other language knowledge required apart from Java.
  12. Easy RPC configuration based on annotations.
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文