野花CMS不是一个CakePHP插件...简单的CMS是一个CakePHP插件...有什么区别？ [英] Wildflower CMS is NOT a CakePHP plugin...Baked Simple CMS IS a CakePHP plugin...what's the difference?
问题描述
我刚刚开始使用CakePHP，我发现了 Wildflower CMS 。我喜欢这个想法，我要开始修饰它。
I just started playing with CakePHP and I found Wildflower CMS . I like the idea and am going to start tinkering with it. I have a question, though.
在README中，我发现了以下内容：Wildflower不是，不会是CakePHP插件。 Wildflower与Baked Simple之间有什么区别，这称为CakePHP插件？
In the README, I found the following: "Wildflower is not and won't be a CakePHP plugin". What's the difference between Wildflower and something like 'Baked Simple', which claims to be a CakePHP plugin?
Wildflower是一个完整的Cake应用程序，而Baked Simple仅仅是一个在另一个Cake应用程序中使用的插件？有人可以说一些光吗？每一个的优点或缺点是什么（想想你想使用其中的一个作为你的应用程序的基础，但扩展它相当多）？
Is Wildflower an entire Cake application, whereas Baked Simple is just a plugin to be used within another Cake application? Could someone shed some light on this? What would be the advantages or disadvantages to each one (thinking that you want to use one of these as the base for you application, but extend it quite a bit)?
推荐答案
Wildflower CMS使用其他类路径（在 wildflower / 子目录中。如果你想覆盖核心Wildflower的功能，我相信你应该能够拖动文件到你的 app / 目录中修改它们，类似于你可以做一些文件在 cake / 目录中。
Wildflower CMS uses additional class paths (configured in bootstrap.php) to load itself into your application. The CMS code itself is stored in a wildflower/ subdirectory alongside your application. If you wish to overwrite core Wildflower functionality, I believe you should be able to drag files into your app/ directory to modify them, similarly to how you can do this for some files in the cake/ directory.
CakePHP插件有其缺点。我的理解是，插件的原则是允许人们轻松地共享自包含的功能，因此使它们与主应用程序或其他插件通信，或包含自己的配置或数据源稍微更复杂。这允许开发人员更轻松地共享在应用程序中使用的功能块，因为他们可以将插件置于版本控制之下，而不是编写多页复制&粘贴面包 。
CakePHP plugins come with their disadvantages. It is my understanding that the principle of plugins is to allow people to easily share self-contained functionality, therefore making it slightly more complicated to have them communicate with the main app or other plugins, or contain their own configurations or datasources. This allows developers to more easily share blocks of functionality for use in your applications, as they can put the plugin under version control instead of writing a multi-page copy&paste Bakery article.
一般来说，CMS是核心，插件是CMS安装的附件。 Wildflower开发人员考虑了沿着插件路线，然后必须意识到，所需要的是一个控制水平不可能与插件，因为它们存在于CakePHP 1.2，所以决定更可行的基础应用程序。
One conventionally imagines a CMS being the core and plugins being the addons you install for the CMS. The Wildflower developer considered going down the plugin route and then must have realized that what was needed was a level of control not possible with plugins as they exist in CakePHP 1.2, so decided it was more feasible to be the base application.
通过使用这个额外的类路径功能，Wildflower文件将在您的应用程序中不存在时使用。它设法走出你的方式，让你一个绝大多数裸的 app / 目录，通过订单CakePHP寻找文件： app / 然后 wildflower / 然后 cake /
By utilising this additional class path functionality, Wildflower files will be used when they don't exist in your application. It manages to step out of your way, leaving you a mostly bare app/ directory, by making the order CakePHP looks for files: app/ then wildflower/ then cake/
这篇关于野花CMS不是一个CakePHP插件...简单的CMS是一个CakePHP插件...有什么区别？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
