Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 10 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(10)
看到您是 ColdFusion 的新手,我会做的就是选择一个框架并坚持使用它。起初,你会遇到问题,你会很想放弃你选择的框架,但不要这样做。当你掌握了一个框架之后,你就可以学习其他的了。
其中大部分您可以添加
Adobe.com 上的 ColdFusion 框架简介
最重要的是要记住我们都有自己的观点,但没有真正的证据证明什么是最好的。您甚至可以不使用实际的框架,而只需在 MVC 中仔细编码。
你目前维护的东西
我会选择 ColdBox、ModelGlue 或 Framework/1。
ColdBox 提供了一些代码生成,而 Framework/1 非常轻,因此需要学习的内容较少。
Seeing you are NEW to ColdFusion what I would do is pick ONE FRAMEWORK and stick to it. At first it will be hard you will have problems and you will be tempted to drop the Framework you have chosen but don't do it. After you have mastered one framework then you can learn the others.
Most of these you can add
An introduction to ColdFusion frameworks at Adobe.com
Most important is to remember we all have our opinions but there is NO real proof what is best. You can even NOT use a actual framework and just code carefully in MVC.
The stuff you are currently maintaining
I would pick ColdBox, ModelGlue or Framework/1.
ColdBox provides a little Code Generation and Framework/1 is very light so less to learn.
我已经使用 CFWheels 几年了,但没有找到更好的框架。它的灵感来自 Ruby on Rails,并且通过优秀的文档和非常活跃的社区非常容易学习。
www.cfwheels.org
I've been using CFWheels for a couple of years and I've not found a better framework. It's inspired by Ruby on Rails and is very easy to learn with great docs and a very active community.
www.cfwheels.org
我用 ColdFusion 教授一门课程,并在课堂上使用 Sean Corfield 的 Framework/1。它是轻量级的并且具有非常温和的学习曲线,这使得它特别适合转换现有代码库。但与此同时,开发人员团队可以轻松合作并扩展到大型应用程序。无论如何,对我来说,这个框架感觉最不像框架,而最像自然代码。
http://github.com/seancorfield/fw1/
I teach a course in ColdFusion and use Sean Corfield's Framework/1 in the classroom. It's lightweight and has a very gentle learning curve, which makes it especially good for transitioning existing codebases. But at the same time, it's easy for a team of developers to work with and can scale to large apps. It's the framework that feels least like a framework and most like natural code, to me anyway.
http://github.com/seancorfield/fw1/
我想为 cfwheels 提供 +1。
自 2003 年以来,我在各种项目中使用了 Mach II、ColdBox、Fusebox 和 Model-Glue。所有这些都有其优点和缺点(Fusebox 是我现在唯一要避免的),但是,在最近的一个项目中,我决定尝试 CFWheels。
使用轮子真是太棒了。我为小镇上的一些朋友开发了一个网站,他们拥有并经营着一个攀冰和指导网站 ([www.ourayclimbing.com]),我度过了一段愉快的时光。不错的 SES URL,在 Adobe CF 和 Railo 上运行良好,管理员非常容易使用脚手架插件、约定优于配置(我喜欢:))等。
无论如何,如果您坚持使用主要参与者( ColdBox、CFWheels、Mach II 或 Model-Glue),我想您会对 CF 所能提供的功能感到惊喜。
I wanted to give a +1 for cfwheels.
Since 2003, I've used Mach II, ColdBox, Fusebox, and Model-Glue for various projects. All had their pros and cons (Fusebox is the only one I'd avoid now) but, with a recent project, I decided to try CFWheels.
Using Wheels has been a blast. I've had a great time developing a site for some friends in my small town who own and operate an Ice Climbing and Guiding site ([www.ourayclimbing.com]). Nice SES URLs, runs great on Adobe CF and Railo, the admin was insanely easy to get going with the Scaffolding plugin, convention over configuration (which I love :)), etc.
In any case, if you stick with the major players (ColdBox, CFWheels, Mach II or Model-Glue), I think you'll be pleasantly surprised at what CF can offer you.
它确实必须是 coldbox 。
它在网站上有出色的文档,并且还有一本非常出色的书编写内容涵盖了面向对象编程的许多方面以及其他主题。说实话,这本书给我留下了深刻的印象,超出了我的预期。
我喜欢这个框架的地方在于它在处理程序中使用了 Coldfusion 代码,当我拿起它时,我认为其他框架使用了 xml...不确定这是否已经改变。
如果您熟悉 CFC,那么该框架很容易上手,并且具有一些用于构建站点的有用功能。 PLugins、调试工具栏、“漂亮 URL”的 URL 根......
我对这个框架的评价再高也不为过。
还有一个非常有用的社区 这里 他们非常及时地回答了我的所有问题。
It has to be coldbox really.
It has excellent documentation on the site, and also has a book which has been brilliantly written to cover many aspects about object orientated programming, amongst other topics. Honestly, really impressed by the book, more than I was expecting.
What I like about the framework is that it uses coldfusion code in its handlers, when I picked it up I think the other frameworks where using xml...not sure if this has changed.
The framework is easy to pick up if you are knowledgeable on CFCs, and has several useful features for building sites. PLugins, Debug toolbar, URL rooting for "pretty URLS"..
I cant speak highly enough of the framework..
Theres also a really helpful community here who respond to all my questions really promptly.
我建议查看 Mach-II。它已在众多知名度极高、流量大的网站上使用,并且已经使用多年。 这篇博文 在这一点上有点旧,但仍然有一些关于 Mach-II 的一般信息以及谁使用 Mach-II 的重要信息。
它正在非常活跃的开发中(不要让与其他框架相比较低的版本号欺骗了您),1.9 版本即将发布,并且还有 2.0 的宏伟计划。
Mach-II 的重要功能包括复杂的缓存和日志记录功能、用于帮助开发和监控应用程序的非常漂亮的仪表板、带有数据绑定的丰富表单标签库等等。
I'd suggest checking out Mach-II. It's used on numerous extremely high-profile, high-traffic sites and has been for years. This blog post is a bit old at this point but still has some great info in it in terms of Mach-II in general as well as who uses Mach-II.
It's under very active development (don't let the lower version numbers compared with other frameworks fool you) with version 1.9 just around the corner and big plans for 2.0.
Big features of Mach-II include sophisticated caching and logging functionality, a very nice dashboard for helping with development and monitoring of your applications, a rich form tag library complete with data binding, and tons more.
我会选择 CFWheels 或 FW/1。对于那些刚接触 CF 框架的人来说,两者都非常容易使用(我仍然将自己算在该组中),并且学习曲线不像其他框架那么陡峭。 Coldbox 看起来非常强大,但我很难理解它。
I'd go with either CFWheels or FW/1. Both are very easy to use for those new to CF frameworks (I still count myself in that group) and don't have nearly as steep a learning curve as some others. Coldbox looks amazingly powerful, but I had a hard time getting my head around it.
您可能还喜欢我的 SOS 和 COOP 框架。我们正在创建更好的公共文档。与其他选项相比,它可能更像您习惯的代码。
You might also like my SOS and COOP frameworks. We are in the process of creating better public docs. It will likely be more like the code you are used to than other options.
您还可以查看 ColdBox。 http://www.coldbox.org/
大量的文档和大量的功能。
还有 Farcry 核心框架 http://www.farcrycore.org/
不得不说,你'您需要自己决定最喜欢哪种框架,或者是否构建自己的框架。这实际上取决于您想要从框架中得到什么。
就 ColdFusion 8 的 ORM 而言,您拥有 Transfer ORM (http://www.transfer-orm.com) 和 Reactor (http://www.reactorframework.org/)
不过,考虑到 ColdFusion 是 java如果您的应用程序位于 Java 服务器之上,那么您没有理由不能继续使用 Hibernate (http:// www.hibernate.org/)ColdFusion 9 确实使使用 hibernate 变得更加容易,但您暂时只能使用 8。
You could also look at ColdBox. http://www.coldbox.org/
Loads of documentation and loads of features.
There's also Farcry Core Framework http://www.farcrycore.org/
It has to be said that you'll need to make your own mind up which framework you like best or whether to build one of your own. It really depends on what you want out of the framework.
In terms of ORM for ColdFusion 8 you have Transfer ORM (http://www.transfer-orm.com) and Reactor (http://www.reactorframework.org/)
Though, given that ColdFusion is java application on top of a java server, there is no reason why you couldn't go ahead and use Hibernate (http://www.hibernate.org/) ColdFusion 9 does make using hibernate much easier, but you're stuck on 8 for the moment.
一切都是可以商量的。在 Rails 3 中重写 CF 应用程序将是最有力的方法。
基于原则构建的语言和框架 - Ruby/Rails 3(和其他 Ruby 框架)、Python/Django 1.2(和其他 Python 框架)、ASP.NET MVC 2 - 一般来说是最好使用的。
ColdFusion 和 ColdFusion 框架无法进行比较,因为 ColdFusion 作为一种语言和库是随机组合在一起的,而 ColdFusion 框架(ColdBox、FW/1、Model-Glue、CFWheels、Mach II)只能做很多事情来平滑这一点。例如:CF 范围、缺少闭包、缺少可加载类/组件(您可以实例化组件,但不能加载组件本身)、笨拙的参数处理、映射、缺少实际应用程序、缺少委托和闭包,以及对于语言和库的大多数方面来说,都是方便但不严格的方法。相比之下,列出的其他语言提供了严格性和在严格性之上的糖分。
Everything is negotiable. Rewriting the CF apps in Rails 3 would be the strongest approach.
Languages and frameworks built on principles - Ruby/Rails 3 (and other Ruby frameworks), Python/Django 1.2 (and other Python frameworks), ASP.NET MVC 2 - are generally speaking the best thing to use.
ColdFusion and ColdFusion frameworks do not compare because ColdFusion as a language and as a library is hacked together at random and the ColdFusion frameworks (ColdBox, FW/1, Model-Glue, CFWheels, Mach II) can only do so much to smooth that over. For example: CF scopes, lack of closures, lack of loadable classes/components (you can instantiate a component, but not load the component as such), awkward arguments handling, mappings, lack of real applications, lack of delegates and closures, and convenient but non-rigorous approaches to most aspects of the language and library. In comparison, the other languages listed offer rigor plus sugar atop the rigor.