Consider while looking at different tools that some might require special server back-ends. qooxdoo as a toolkit is all client-side.
The rest of this post concerns only qooxdoo and I don't think there are any mature ones available for qooxdoo right now. At least, there are none that are on par with the likes of the experience of developing in Visual Studio and with WinForms (as simply a comparison.) There are some early immature tool attempts at doing similar things, but they still will require a good understanding of qooxdoo and form placement. This is not a complete list:
I think there were also some attempts to put a WYSIWYG designer in front of the XML to qooxdoo tool called QxTransformer, http://qxtransformer.org/ but I may be confusing my projects.
Note that the qooxdoo license is dual licensed to LGPL/EPL. If you are working in a commercial environment some corporations are skittish of anything that isn't MIT or BSD licensed. I mention this in regard to your reference to the "free and open source" alternatives. While I firmly believe the intention of the application of LGPL/EPL is to allow us developers to do whatever we want with our creation as long as we contribute back to any enhancements to the qooxdoo libraries, corporate lawyers are afraid of nothing specific in writing. If you are doing this for commercial organization do your homework first. I had wanted to use qooxdoo for a project, but was prevented because of the license and my companies leaning toward MIT/BSD only open source licenses.
As a library goes, I think qooxdoo is the most feature complete and best structured. It is well documented though it does come with a learning curve. However, examples abound and the forum is very responsive. If there is any criticism about qooxdoo it might be that it is a heavier weight (size) library so that the final compiled javascript is often large (500-700k). For complex applications it can be a bit too intensive for smart phones and first generation iPads. However, nowadays this becomes less and less an issue and the mobile side of qooxdoo is evolving rapidly to provide a lighter weight solution. Basically, it keeps getting better and better.
From experience I think manual (text editing) form design is tedious and error prone and a tool to make it easier would be a godsend. qooxdoo's structure and "extends" capability would make it a prime candidate for a IDE implementation like Visual Studio uses with WinForms and .NET.
Before switching to Ext, we used the Yahoo libraries. We were using the old version YUI2, but version 3 is apparently also very good. It has many similar components such as grids (datatables) , menus, calendar widgets, etc.
发布评论
评论（4）
一般来说，你可以看看这篇文章：
HTML/JavaScript UI 小部件 GUI 构建器
在查看某些人可能会使用的不同工具时请考虑需要特殊的服务器后端。 qooxdoo 作为一个工具包，全部是客户端的。
这篇文章的其余部分仅涉及 qooxdoo，我认为现在没有任何成熟的可用于 qooxdoo。至少，没有任何工具可以与 Visual Studio 和 WinForms 中的开发体验相提并论（只是作为比较）。有一些早期不成熟的工具尝试做类似的事情，但它们仍然需要良好的性能。了解 qooxdoo 和表单布局。这不是完整的列表：
我认为也有一些尝试XML 到 qooxdoo 工具 QxTransformer 前面的所见即所得设计器，http://qxtransformer.org/ 但我可能会混淆我的项目。
请注意，qooxdoo 许可证是 LGPL/EPL 的双重许可。如果您在商业环境中工作，一些公司会对任何未经 MIT 或 BSD 许可的东西感到不安。我在提到“免费和开源”替代方案时提到了这一点。虽然我坚信应用 LGPL/EPL 的目的是让我们开发人员可以随心所欲地创作，只要我们对 qooxdoo 库的任何增强做出贡献，但公司律师并不害怕任何书面的具体内容。如果您是为商业组织这样做，请先做好功课。我曾想在一个项目中使用 qooxdoo，但由于许可证的原因而被阻止，而且我的公司只倾向于 MIT/BSD 开源许可证。
作为一个库，我认为 qooxdoo 是功能最齐全、结构最好的。尽管它确实有一个学习曲线，但它有很好的记录。然而，例子比比皆是，论坛的反应也非常灵敏。如果对 qooxdoo 有任何批评的话，可能是它是一个重量（大小）较重的库，因此最终编译的 javascript 通常很大（500-700k）。对于复杂的应用程序，对于智能手机和第一代 iPad 来说可能有点过于密集。然而，如今这已不再是一个问题，qooxdoo 的移动端正在迅速发展，以提供更轻量级的解决方案。基本上，它一直在变得越来越好。
最后，这里是 qooxdoo 开发人员关于创建 IDE 的讨论的链接。
http://qooxdoo.678.n2.nabble.com/qooxdoo-quot-IDE-quot-Request-for-Comments-td3782909.html
根据经验，我认为手动（文本编辑）表单设计是乏味且容易出错，而一个能让事情变得更容易的工具将是天赐之物。 qooxdoo 的结构和“扩展”功能使其成为 IDE 实现的主要候选者，例如 Visual Studio 与 WinForms 和 .NET 一起使用。
In general, you might check out this post:
HTML/JavaScript UI widgets GUI builder
Consider while looking at different tools that some might require special server back-ends. qooxdoo as a toolkit is all client-side.
The rest of this post concerns only qooxdoo and I don't think there are any mature ones available for qooxdoo right now. At least, there are none that are on par with the likes of the experience of developing in Visual Studio and with WinForms (as simply a comparison.) There are some early immature tool attempts at doing similar things, but they still will require a good understanding of qooxdoo and form placement. This is not a complete list:
I think there were also some attempts to put a WYSIWYG designer in front of the XML to qooxdoo tool called QxTransformer, http://qxtransformer.org/ but I may be confusing my projects.
Note that the qooxdoo license is dual licensed to LGPL/EPL. If you are working in a commercial environment some corporations are skittish of anything that isn't MIT or BSD licensed. I mention this in regard to your reference to the "free and open source" alternatives. While I firmly believe the intention of the application of LGPL/EPL is to allow us developers to do whatever we want with our creation as long as we contribute back to any enhancements to the qooxdoo libraries, corporate lawyers are afraid of nothing specific in writing. If you are doing this for commercial organization do your homework first. I had wanted to use qooxdoo for a project, but was prevented because of the license and my companies leaning toward MIT/BSD only open source licenses.
As a library goes, I think qooxdoo is the most feature complete and best structured. It is well documented though it does come with a learning curve. However, examples abound and the forum is very responsive. If there is any criticism about qooxdoo it might be that it is a heavier weight (size) library so that the final compiled javascript is often large (500-700k). For complex applications it can be a bit too intensive for smart phones and first generation iPads. However, nowadays this becomes less and less an issue and the mobile side of qooxdoo is evolving rapidly to provide a lighter weight solution. Basically, it keeps getting better and better.
Finally, here is a link to a discussion amongst qooxdoo developers about creating an IDE.
http://qooxdoo.678.n2.nabble.com/qooxdoo-quot-IDE-quot-Request-for-Comments-td3782909.html
From experience I think manual (text editing) form design is tedious and error prone and a tool to make it easier would be a godsend. qooxdoo's structure and "extends" capability would make it a prime candidate for a IDE implementation like Visual Studio uses with WinForms and .NET.
在切换到 Ext 之前，我们使用了 Yahoo 库。我们使用的是旧版本 YUI2，但版本 3 显然也非常好。它有许多类似的组件，例如网格（数据表）、菜单、日历小部件等。
http://developer .yahoo.com/yui/2/
http://developer.yahoo.com/yui/< /a>
Before switching to Ext, we used the Yahoo libraries. We were using the old version YUI2, but version 3 is apparently also very good. It has many similar components such as grids (datatables) , menus, calendar widgets, etc.
http://developer.yahoo.com/yui/2/
http://developer.yahoo.com/yui/
Sencha Architect是一个非常好的产品。
Sencha Architect is a very nice product.
DHTMLX 库附带一个免费的在线 UI 设计器工具。
该库本身具有双重许可：GPL 和商业许可。商业许可证包括 UI 设计器的桌面版本。
还有使用 dhtmlx 组件构建的文件浏览器演示。
（免责声明：我为 DHTMLX 工作）。
The DHTMLX library comes with a free online UI designer tool.
The library itself is dual licensed: GPL and commercial. The commercial license includes the desktop version of the UI designer.
There is also file explorer demo built with the dhtmlx components.
(Disclaimer: I work for DHTMLX).