我的任务是为家庭种植的应用程序进行一些规划和研究。我们的主要开发语言是 ColdFusion 和 Flex3，因此我想通过模块化解决方案（使用 MVC 框架）来解决这个问题。
我必须提到，我不是一个巨大的 ColdFusion 开发人员，但将成为这个应用程序背后的架构师之一（哎呀！）。我有几年使用 .NET / PHP / ASP 开发电子商务应用程序的经验，但从未达到过这种规模。
总体目标是构建一个基于模块的应用程序，我们可以推出并“添加”功能模块，以免将自己锁定在某个方向。
该系统需要两个关键的东西：
- 功能必须是“drop and go”类型，这样，如果电子商务应用程序需要诸如 paypal 处理之类的功能，我们就会放入 paypal 模块，然后它就会成为结账时的一个选项，等等；
- 能够处理多个品牌（我们服务的市场有几个，每个市场都有自己的品牌）。
背景知识已经足够了……
我主要关心的是，我应该如何开始？我正在考虑使用 ColdFusion MVC 框架，有什么建议吗？我查看了以下内容（针对 Coldfusion）：
- Model-Glue
- Cairngorm
- Pivot-MVC
- Fusebox
我走在正确的轨道上吗？我希望使用 MVC 将有助于实现插入式模块化功能的目标，同时减少编写重复性内容所花费的时间。我对这些 MVC 框架还不够了解。
我将不胜感激任何有用的建议，以便我可以制定精确的攻击计划。
编辑：
回顾 ColdBox 后，使用它与其他 MVC 有何比较？我读到它不支持“即放即走”类型的功能。
关于 CF 的 MVC 框架还有其他意见吗？
I have been tasked with doing some planning and research for a home grown in house application. Our primary development language is ColdFusion and Flex3, so I wanted to attack this problem with a modular solution, using an MVC framework.
I must mention that I am not a huge ColdFusion developer, but will be one of the architects behind this app (yikes!). I have a few years experience developing ecommerce applications in .NET / PHP / ASP, but never on this type of scale.
The overall goal is to build a module based applciation that we can roll out and 'add' modules for functionality, so as not to lock ourselves in a certain direction.
The system requires two key things:
- Functionality must be a 'drop and go' type, so that if the eCommerce application requires functionality like paypal processing, we drop in the paypal module, and bam it is an option at checkout, etc;
- Ability to handle multiple brands (we have a few markets we serve, and each market has its own brand).
Ok enough background...
My key concerns are, how should I start? I am looking at using a ColdFusion MVC framework, any suggestions at which? I've looked at the following(for Coldfusion):
- Model-Glue
- Cairngorm
- Pivot-MVC
- Fusebox
Am I on the right track? I hope using an MVC will help reach the goal of a drop in and go modular functionality with reduced time spent coding repetitive things. I don't know enough about these MVC frameworks tho.
Would appreciate any helpful suggestions so I can formulate a precise plan of attack.
EDIT:
Having reviewed ColdBox, what would be a comparison to use it over another MVC? I've read that it does not support the 'drop and go' type of functionality.
Any other opinions on an MVC framework for CF?
发布评论
评论（3）
我为其 ColdFusion 的 ColdBox Framework Coldbox/trac.cgi/wiki/cbFeatures" rel="noreferrer">丰富的功能集，能够成为我的 Ajax/Flash/Web 服务开发的控制器，活跃社区和频繁发布。最重要的是，我选择 ColdBox 是为了获得数量惊人的文档——让我能够更快地得到答案，同时让我有更多的时间来编写代码，而不是记录应用程序的工作原理。
我鼓励建立一个框架——任何框架。它将促进更快的开发，帮助指导最佳实践，并使应用程序拥有比您和其他开发人员更长的生命周期。
所以，是的！你走在正确的轨道上。
感兴趣的链接
，
Aaron Greenlee
I selected the ColdBox Framework for ColdFusion for its rich feature set, ability to be a controller for my Ajax/Flash/Web Service development, active community and frequent releases. Most importantly, I selected ColdBox for the amazing amount of documentation--allowing me faster answers while affording me even more time to write code rather than documenting how the application works.
I encourage a framework--any framework. It will foster faster development, help guide best practices and enable the application to have a long life--past you and other developers.
So, YES! You are on the right track.
Links of Interest
Respectfully,
Aaron Greenlee
如果是我，我会规划应用程序的用户视角，有多少个步骤，有多少个不同的页面，每个页面的功能是什么，设计目的。
然后规划出每个页面的逻辑，它需要做什么等等。一步一步没有代码，只有很多注释。
然后也许做一个没有冷融合的线框 html/css 页面，逐步向您展示电子商务应用程序的行为方式..
然后开始逐页制作，并进行大量测试....您的计划越清晰计划越多，功能蔓延的可能性就越小。
If it were me, i'd plan the users viewpoint of the application, how many steps there were, how many different pages, what is the function, design purposes of each page.
Then plan out each page's logic, what it needs to do etc..step by step no code, just lots of comments.
Then maybe do a wireframe html/css pages with no coldfusion to show you step by step how the ecommerce application would act like..
Then start making page by page, and do lots of testing....the clearer your plans are for any plans, the less chance of feature creep.
好吧，我希望我在这里正确理解了你的意思。您列出的所有选项都是很棒的框架。然而，当你建立一个网站时，最多你会得到一个“Hello World”之类的网站，从那里，你可能就得靠自己了。 MVC 框架旨在将编程的不同部分（逻辑、外观、整体数据模型等）分开，以方便重用，但不是达到“哦，添加 PayPal、Authorize.Net 和PayflowPro 是我的购物车应用程序的最后一步。
听起来您正在寻找像 Cartweaver 这样的基于 CF 的电子商务应用程序，然后获取或购买 Cartweaver 插件来扩展它（以提供不同类型的运输、支付处理等）。
Well, I hope I'm understanding you correctly here. All of the options you listed are great frameworks. However, when you set one up, at most, you're going to get a 'Hello World' sort of site out of it, and from there, you're probably on your own. MVC frameworks are designed to sort of split apart different part of programming (the logic, the appearance, the overall data model, etc.) to allow for easy reuse, but not at a level of 'Oh, add PayPal, Authorize.Net and PayflowPro to the last step of my cart' sort of application.
It sounds like you're looking for a CF-based eCommerce application like Cartweaver, and then to acquire or buy Cartweaver plugins to extend it (to offer different types of shipping, payment processing, etc., etc.).