寻求对 JIDE 的反馈 [英] Looking for a feedback on JIDE

查看:25
本文介绍了寻求对 JIDE 的反馈的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我即将开始开发相当大的基于 Java 的桌面应用程序.看了JIDE组件和框架,乍一看似乎是个不错的解决方案.我想听听使用这些产品的人的意见.他们有多可靠?学习曲线如何?利弊?

I'm about to start development of fairly large java based desktop application. After looking at JIDE components and frameworks, it seems to be a good solution at a glance. I'd like to hear from those who used those products. How reliable are they? What's the learning curve? Pros and cons?

推荐答案

我已经使用 JIDE 2.5 年了.就我而言,它是最好的 Swing 组件库(因为数量不多).如果您想从这里获取一个组件并从那里获取另一个组件,则某些功能可以被其他替代方案替换,但有些功能似乎是独一无二的.当然,采用一个完整的解决方案而不是单独的组件和框架更容易.尽管我应该指出,我主要使用了库中的单独组件以及 Docking 框架,但没有使用 JDAF,因此我无法对此发表评论.
大多数部分的质量都很好,尽管在某些时候感觉每个版本都引入了一个新错误.但是每个 Swing 版本也是如此,所以不能真正责怪他们.总体而言,响应时间和客户服务都很好,因此您的问题并不孤单.他们似乎也愿意根据客户的需求调整产品.
然而,在某些方面,他们的操作似乎有点业余.比如我上次查的时候,他们的论坛还是被当成bug库了.他们还发布了大量新产品,其中一些似乎永远停留在测试阶段.
我建议您就部署费用与他们联系,以了解总成本,评估产品,然后与其他替代方案的风险和成本相比,考虑采用 JIDE 的风险和成本.开源也不是没有风险的.被困在一个死的商业产品上可能比被困在一个死的开源产品上更糟糕,但我也不会喜欢.

I've been using JIDE for 2,5 years now. As far as I'm concerned, it's the best Swing component library there is (as there aren't many). Some of the functionality can be replaced by other alternatives if you want to take a component from here and another from there but some seem to be unique. And of course it is easier to adopt one complete solution instead of separate components and frameworks. Though I should point out, that I've mainly used separate components from the library as well as the Docking framework, but not JDAF so I can't comment on that.
Quality has been good for the most parts although at some point it felt as every release introduced a new bug. But so does every Swing release, so can't really blame them. Response times and customer service in general has been good so you're not alone with your problems. They also seem willing to adapt their products for customers needs.
However, on some parts their operation seems a bit amateurish. For example, the last time I checked, their forum was still used as a bug database. They also have released a large number of new products, some of which seem to be stuck in the beta stage forever.
I'd recommend that you contact them about the deployment fee to get an idea of the total costs, evaluate the product and then consider the risks and costs of adopting JIDE compared to the risks and costs of other alternatives. Open source is not risk free either. Being stuck on a dead commercial product may be worse than being stuck on a dead open source product, but I wouldn't enjoy either.

这篇关于寻求对 JIDE 的反馈的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆