我应该购买 Obout 控件吗？
我们开始了一个新项目，该项目的本质是交互性很强，需要丰富的 UI。
我们需要一组富 UI 开发所需的控件。我在谷歌搜索时发现了奥布特。除了 Telerik、ComponentOne、NetAdvantage 之外，我从未听说过它们，也从未见过其他成员告诉我这样的名字。这些都是我们听说过的著名名字，但没有这个。
但是，控制给人一种积极的感觉。但当您购买某些服务时，有两件事始终很重要：他们的客户支持有多好？他们的价格有多少可行？
另外，他们发布补丁/更新的速度有多快？例如，如果我们在开发过程中发现错误或错误，会发生什么？他们为此提供快速解决方案吗？
我在这里做出决定有点困惑。我需要您的帮助、经验和反馈。
We started a new project and the nature of the project is very interactive and a Rich UI is required.
We would need a set of controls that would require for Rich UI development. I found Obout while googling. I never heard about them and never seen fellow members telling me such name except Telerik, ComponentOne, NetAdvantage. These are the famous names we heard but no this one.
But, the controls give a positive feeling. But as two things matter always when you are buying some services: How good are their customer support? and How much feasible their price is?
Another, how quickly they release patches/updates? As, what if we find a bug or an error during development what will going to happen? Do they provide a quick solution for this?
I'm bit confused making a decision here. I need your assistance, experience and feedback.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（7）
我以前用过 Obout 控件。他们肯定不如 Telerik 或 ComponentOne 这样的公司出名，但他们已经存在相当长一段时间了，并且确实推出了优质的产品。它们的价格也便宜很多。总的来说，我与他们的合作经历非常积极，并且在支持请求方面从未遇到过任何麻烦。我第一次接触他们是在大约 5 年前，当时他们非常好，而且只会变得更好。
我不知道他们发布版本的具体速度，但我可以告诉你，在过去的几年里他们发布了很多新东西。我相信您可以在购买之前下载所有控件并试用它们，所以我鼓励您这样做。如果它满足您的需求并且您发现它比其他替代品更容易使用，那么就选择它。
另请查看此问题以查看一些其他反馈：Obout control in C# .Net
I've used Obout controls before. They are definitely lesser known than something like Telerik or ComponentOne, but they've been around for quite a while and definitely put out a quality product. They are also a good deal less expensive. Overall I had a very positive experience with them and never had any trouble with support requests at all. My first experience with them was about 5 years ago and they were very good then, and they've only gotten better.
I don't know specifically how quickly they put out releases, but I can tell you that over the past few years they have released a whole lot of new stuff. I believe you can download all the controls and try them out before you buy them, so I would encourage you to do that. If it meets your needs and you find it easier to use than the alternatives then go for it.
Also check out this question to see some additional feedback: Obout controls in C# .Net
不这么认为。我买了他们的套件，每次我尝试使用他们的其中一个控件时，它都很糟糕。
示例 1。
我使用他们的网格并想利用过滤选项。对于 400 条记录，网格仅筛选第一页上的 20 条记录。所以它遗漏了大部分记录。我联系了他们的支持人员，并向他们发送了他们要求的文件。那是五个月前的事了，尽管我多次尝试和发送电子邮件，但我从未得到答复。
示例2：
今天我正在使用他们的日期选择器。不错的尝试，但它在页面上的奇怪位置打开，并且无法更改。
Don't think so. I bought their suite and everytime i tried to use one of their controls, it sucked.
Example 1.
I use their grid and want to take advantage of the filtering options. For 400 records, the grid only filters in the twenty records that are on the first page. So it leaves out the majority of the records. I got in contact with their support and i sent them the files they asked for. That was five month ago and despite repeated tries and emails, i never got an answer.
Example 2:
Today i am using their datepicker. Nice try, but it opens in a weird position on the page and there is no possibility to change that.
我们已经使用他们的工具一年多了，我们对它们非常满意。成本只是竞争对手收费的一小部分。它们工作得很好，看起来也很漂亮，而且它减少了我们的开发工作，因此即使学习了新工具，我们的项目也比预期提前了两个月完成。
学习曲线有点陡峭，但这适用于任何类似的软件包。技术支持很糟糕，仅通过电子邮件。当我们第一次购买它时，他们有一个支持论坛，您可以在论坛中找到大部分答案，但遗憾的是他们没有成功。现在需要几天时间才能得到答复。但是，在执行整个应用程序时，我们在等待响应时需要处理大量页面。大多数时候他们会指出问题或告诉我们如何解决。我给他们发了很多消息，告诉他们不要理会以前的询问，因为我在互联网上找到了答案。
他们的例子很简单，如果您的需求很简单，它们就足够了。如果构建一个成熟的应用程序来替换旧应用程序并运行您的业务（就像我们所做的那样），您需要更好的支持。尽管如此，这笔钱花得值。我们使用网格和过滤器对包含 200,000 条记录的客户数据库进行搜索，通常只需按姓名不到 10 次按键即可找到我们需要的人。我们的内联网上的性能非常好。
我要指出的是，当我认为我发现了软件中的错误时，只有我自己发现了错误。句号应该是逗号，大小写错误，函数误用等等。Javascript对其语法非常敏感，并且对错误消息不友好，所以花了很多时间检查代码来发现不那么明显的错误。
而我们的需求可能超出了大多数人的需求，我们的主屏幕有一个超级表单和7个数据网格的组合，每个网格都会弹出一个用于数据输入的模式表单，所有这些都在同一个网页内。但它做得很好。总而言之，我们有大约 60 个数据输入页面和另外 60 个使用 oBout 工具创建的报告页面。报告页面允许用户设置报告条件（即使用弹出窗口、日历、单选按钮等的日期、客户、产品等）并将这些条件传递给 SSRS 报告（一种临时报告）。因此，我们在不到一年的时间里创建了一个包含超过 125 个网页和 150 多个报告的项目，考虑到劳动力规模较小，这是一项相当大的成就。
We have been using their tools for over a year now, and we are very pleased with them. The cost is a fraction of what the competition is charging. They work great, they look nice and it reduced our development so that our project was completed two months before expected, even with learning the new tools.
The learning curve is a little steep, but that goes for any of the comparable packages. The tech support sucks, by email only. When we first purchased it they had a support forum and you could find most of your answers in the forum, but sadly they did away wit hit. Now it takes a few days to get a response. But when doing an entire application, we had plenty of pages to work on while waiting for responses. Most of the time they pointed out the problems or told us how to resolve them. And I sent them many messages telling them to disregard previous queries, having found the answers on the internet.
Their examples are simple, and if your needs are simple they will suffice. If building a full-blown application to replace a legacy application and run your business, such as we did, you need better support. Still, it was money well spent. We use the grid and filters to perform searches on our client database of 200,000 records, and can usually find the person we need in less than 10 keystrokes by name alone. Performance is very good on our intranet.
I will note that when I thought I had found bugs in the software, it was just me. A comma where a period should be, bad capitalization, misuse of functions, etc. Javascript is very sensitive with it's syntax and not friendly with error messages, so much time was spent going over code to discover the not-so-obvious errors.
And our demands are probably beyond most peoples needs, our main screen has a combination of a superform and 7 data grids, each of which pops up a modal form for data entry, all within the same web page. But it does the job well. All in all, we have about 60 data entry pages and another 60 reporting pages we created with the oBout tools. The reporting pages allow the users to set report criteria (i.e. dates, clients, products, etc. using popups, calendars, radio buttons, etc.) and pass these to SSRS reports, a sort of ad-hoc reporting. So we created a projects with over 125 web pages and over 150 reports in less than one year, quite an achievement considering the small workforce.
如果我是您，我会强烈关注使用 jQuery 和数百个出色的插件，它们几乎可以提供您需要的任何功能。 jQuery 得到了大力支持，最重要的是它是免费的（开源）。
它将提供您需要的所有客户端功能，并且非常易于使用。使用 jQuery 真正需要的事情之一是控制 HTML 控件（DOM 元素）的 id 和名称。当您使用这些第三方控制包（以及 .net 中的大多数内置控制包）时，您通常会失去对它们生成的 HTML 的大量控制。您可以等待 asp.net 4.0 的发布来解决控件 id 问题，也可以依赖转发器控件并完全控制它生成的 id 和其他 HTML。
如果您还没有学习 jQuery 和中继器控件，那么花一点钱学习 jQuery 和中继器控件是非常值得的。
If I were you I'd look strongly at using jQuery and the hundreds of great plug-ins that will provide just about any functionality you need. jQuery is heavily supported and best of all it's free (open source).
It will provide all the client-side functionality you need and it's VERY easy to work with. One of the things you really need to use jQuery is to have control over the id and names of your HTML controls (DOM elements). When you use those third-party control packs (and most of the built-in ones in .net too) you typically lose a good deal of control of the HTML they produce. You can either wait for asp.net 4.0 to come out which will resolve the control id issues or rely on repeater controls and have complete control over the ids and other HTML it produces.
It's well worth the small investment in learning jQuery and the repeater control if you haven't done so already.
几年前我使用过 Obout 控件（凭记忆，他们的 ASP.Net TreeView 和 Slidemenu）。
我想我必须联系他们几次，并且两次都得到了及时的支持，解决了我们遇到的问题。
然而，他们的控件（在 UI、API 方面）是否满足你的期望是很个人的事情——支持很好，但你可能会发现你不喜欢它们的外观，或者 API 不适合与你做事的方式（虽然这对我来说很好）。你真的应该亲自评估一下他们，看看你与他们相处得如何。
I used Obout controls several years ago (from memory, their ASP.Net TreeView and Slidemenu).
I think I had to contact them on a couple of occasions, and received prompt support both times, solving the problem we had.
However, whether their controls (in terms of UI, API) meet your expectations is quite a personal thing- the support is good, but you might find that you don't like the look of them, or the API doesn't fit in with the way you do things (although it was fine for me). You should really evaluate them yourself and see how you get on with them.
如果您不需要将某些东西很好地集成到 ASP.NET 中，那么一定要看看 extjs。它是丰富的用户界面库。
if you don't need something too well integrated into asp.net, definetly have a look at extjs. its THE rich ui library.
我正在使用 Obout 控件。显然，如果可以的话，我会做出另一种选择。这些控件体积庞大，并且当您尝试继承它们时常常会出现错误。对我来说这是一个糟糕的选择。
I am using Obout controls. And clearly I would have done another choice If I could. The controls are bulky and quite often buggy when you try to inherits from them. A poor choice to me.