javascript - 我的项目和这些 Javascript 框架哪里错了？

Question

首先，我希望创建的项目的最基本部分是作为单页 Web 应用程序实现的 wiki 引擎。我计划从一开始就提供一组功能，并在未来增加大量功能。

基本特征

• 页面创建(为该文章创建 wiki 文章和讨论论坛)
• 标记和所见即所得ala markitup
• 标记/html/所见即所得之间的即时转换
• 用于快速导航的侧边栏
• 用于选择编辑/查看的顶部工具栏

高级功能

• 可配置的侧边栏以通过不同的方法导航
• 可配置的工具栏(可能添加选择的标记语言)
• 标签
• 可编辑的待办事项
• 拖放文件上传和图片附件

该引擎最初包含最基本的页面创建、标记和所见即所得的编辑和保存。我最终想通过拖放图像支持、文件上传、实时数据图和用于自定义 View 的侧边栏来扩展这个基本引擎。

我已经对一个体面的项目进行了相当广泛的搜索，以此作为我的项目的基础，但除了 TiddlyWiki 之外，似乎没有任何好的基于 javascript 的 wiki 引擎。我还考虑过在现有的 wiki 引擎之上应用 Jquery，但我相信我最终还是会重写它(加上它只是更令人兴奋地添加我想要的功能)。无论哪种方式，我都已经用 javascript 库 + 框架实现了这个野兽。

我知道不能真正将其中一些框架相互比较，因为它们非常不同。我已尝试将任何比较评论/问题与相应框架的可比部分进行比较，但我愿意接受更正。

我们开始吧:

根据我自己的研究和意见，我将列表缩小到以下项目。我有意遗漏了 SproutCore、corMVC、YUI 等内容，因为我以我有限的能力认为以下内容更合适。

我的选择

• jquery + jqueryUI + backbonejs
• knockoutjs
• javascriptMVC
• Dojo
• ExtJS
• Cappuccino

---

jquery/UI + backbonejs

总体

From what I've read this combination is used and beloved by many and is very flexible and extensible. My major concern is that this combination is simply not the best jumping off point for developing the more desktop oriented UI interface.

用户界面

While jQueryUI or jqueryTools might be competitive they certainly do not seem to be on-par with the UI capabilities of other frameworks. Specifically they seem to be heavy on the effects but lacking on decent layout slicing support.

javascriptMVC

总体

JavascriptMVC to me looks like it is essentially jquery + MVC(jqueryMX) extensions, along with a few other apps for documenting(documentJS), functional tests(funcUnit), and code and dependency management(stealJS). Beyond the benefits of the additional module, I think the functional debate really comes down to backbonejs vs. jqueryMX Am I correct on this and has anyone worked with or compared both?

• Features: jupiter's (maker of jMVC) overview of their features
• Link to jqueryMX

用户界面

JavascriptMVC adds the MXUI items on top of whatever is available for Jquery so I think at the very least it is a slight win in that category.

淘汰赛

总体

My thoughts and concerns on this on this are very similar to the jquery + backbone comments. They both seem to offer similar features but just from a different perspective. An oft cited downside is that knockoutjs couples business logic and presentation too tightly with the data-bind's and that this binding method can break down for complex UI interaction but I would love to hear why that is a non-issue.

• Discussion of backbone vs knockoutJS concepts
• Features of knockoutjs

用户界面

暂时空白

Dojo 和 ExtJS

总体

I am going to combine the discussion Dojo and ExtJS because I know the least about them and they seem to play in nearly the same space. Most of the information on stackoverflow about these two seems to be out-of-date. From what I have seen is that they are both large frameworks that are good for desktop caliber app implementation. Dojo had been chided for poor documentation but that seems to be no longer the case. ExtJS of course has the commercial license, but it is really reasonable for what you get and I wouldn't hold that against it too much. The widgets in ExtJS seem to be somewhat more professionally done than Dojo, but I could certainly be corrected there. I would be interested to hear from anyone who has experience in both.

用户界面

Dojo has the dijit UI library ExtJS has UI features but they are not in Ext core. Here's the documentation and here are their demos

卡布奇诺

总体

And then there is Cappuccino. No CSS, no html, but also it could be tough to use existing javascript libraries. Objective-J doesn't seem to scary, especially considering that they tout being able to write plain javascript as well. The demos are impressive and seem to closely approach the UI needs for the wiki engine. The cocoa based API is a lot to take in for someone not familiar with it, but maybe it is worth it. I have heard the layout engine is not always easy to work with but a young and possibly disruptive tech like this will certainly have some shortcomings.

用户界面

Blank at the moment

我很抱歉写了这么多但是嘿，至少它不是一个 x vs y vs z 的问题，希望得到大量廉价的答案。所以你怎么看？我的桌面(如 wiki 引擎)应该以什么为基础，随着时间的推移，它有望变得更加丰富(阅读复杂)？

Answer 1

不确定您的时间表和资源，但当我试图在多个框架/环境之间做出决定时，我只是继续尝试快速构建原型(prototype)。即使它只是一两个主要功能，我发现世界上所有的研究和文档都无法与实际尝试使用这些工具构建某些东西相匹配。我说每个人都花一天时间，看看你能走多远。这会让您很好地了解哪些工具可以胜任这项任务，并且让您感觉最舒服。