如何使用plone作为框架

时间:2021-11-18 07:23:29

I am creating a web app that allows people to debate topics. I started prototyping with Django and have a functional app. I have not yet decided on what framework to use.

我正在创建一个允许人们讨论主题的网络应用程序。我开始使用Django进行原型设计并拥有一个功能性应用程序。我还没决定使用什么框架。

I've read about Plone the app and Plone the framework. I just can't seem to find any online documentation on using Plone as a framework. I'm looking for a tutorial or something that will show me how to build a web app starting with Plone. I just want to evaluate Plone before I choose my framework.

我已经阅读了Plone应用程序和Plone框架。我似乎无法找到任何关于使用Plone作为框架的在线文档。我正在寻找一个教程或其他东西,向我展示如何构建一个以Plone开头的Web应用程序。我只想在选择框架之前评估Plone。

Anyone have any refs or recommendations on learning how to use Plone as a framework?

任何人都有关于学习如何使用Plone作为框架的任何参考或建议?

3 个解决方案

#1


You should start here:

你应该从这里开始:

http://plone.org/documentation

A really good book is: http://www.packtpub.com/Professional-Plone-web-applications-CMS/book

一本非常好的书是:http://www.packtpub.com/Professional-Plone-web-applications-CMS/book

Plone is build on Zope Application Server (zope.org). You should read into the zope book too. Its free.

Plone构建于Zope Application Server(zope.org)之上。你也应该阅读zope书。免费。

The IRC Channel (#plone) on freenode is full of experts that are willing to help. They like to discuss with :)

freenode上的IRC频道(#plone)充满了愿意提供帮助的专家。他们喜欢和:)讨论

#2


I think that the most important factor in choosing a framework is the existence of good documentation. If you can't find good docs for using plone in the way that you want without having to ask here first, that's all the "evaluation" you need.

我认为选择框架最重要的因素是存在良好的文档。如果你找不到以你想要的方式使用plone的好文档而不必先问这里,那就是你需要的所有“评估”。

I'd stick with Django.

我坚持使用Django。

#3


Don't use Plone as Framework.

不要将Plone用作框架。

Plone is an CMS. You can use it as framework,You can use Zope2 application server + Zope3 component architecture but I don't recomended to do this. Plone was designed to be a CMS so why You want use it as framework?

Plone是一个CMS。你可以使用它作为框架,你可以使用Zope2应用服务器+ Zope3组件架构,但我不建议这样做。 Plone被设计成一个CMS,为什么你想用它作为框架?

Why you shouldn't use Plone as framework?:

为什么你不应该使用Plone作为框架?:

  1. Plone is Slow!!! 30 sec. on every restart is too much. When You change something, you need restart. Autorestart(http://plone.org/products/collective.autorestart) doesn't help, you still need to restart Plone any time You change a zcml, portlet's code and sometime with python code.
  2. Plone很慢!!! 30秒每次重启都太多了。当你改变某些东西时,你需要重新启动。 Autorestart(http://plone.org/products/collective.autorestart)没有帮助,你仍然需要在任何时候使用python代码更改zcml,portlet的代码时重启Plone。

  3. Plone is too complex. So big code base. Different coding styles (old Zope2, new component base Zope3, some parts are written with Grok).
  4. Plone太复杂了。如此庞大的代码库。不同的编码风格(旧的Zope2,新的组件基础Zope3,一些部分是用Grok编写的)。

  5. You will need write xml (Generic Setup).
  6. 您将需要编写xml(通用设置)。

  7. Nobody can say what you must use Archetypes, Formlib, z3c.form or Dexterity?
  8. 没有人可以说你必须使用Archetypes,Formlib,z3c.form或Dexterity?

  9. Plone doesn't have good documentation. Too much old documentation (plone.org/documentation) and there is no place where you can read what is the right way to do. The only good documentation is in Martin Aspeli's book (martinaspeli.net/plone-book) but you will need more and this book isn't open, so You will need buy it.
  10. Plone没有很好的文档。太旧的文档(plone.org/documentation),没有地方可以阅读正确的方法。唯一的好文档是在Martin Aspeli的书(martinaspeli.net/plone-book)中,但是你需要更多,而且这本书没有开放,所以你需要买它。

  11. Plone has so many products but if you need really stable and quality stuff you will need write your own.
  12. Plone有很多产品,但如果你需要非常稳定和高质量的东西,你需要自己编写。

  13. Plone is Slow!!! Forget test driven development.
  14. Plone很慢!!!忘记测试驱动的开发。

#1


You should start here:

你应该从这里开始:

http://plone.org/documentation

A really good book is: http://www.packtpub.com/Professional-Plone-web-applications-CMS/book

一本非常好的书是:http://www.packtpub.com/Professional-Plone-web-applications-CMS/book

Plone is build on Zope Application Server (zope.org). You should read into the zope book too. Its free.

Plone构建于Zope Application Server(zope.org)之上。你也应该阅读zope书。免费。

The IRC Channel (#plone) on freenode is full of experts that are willing to help. They like to discuss with :)

freenode上的IRC频道(#plone)充满了愿意提供帮助的专家。他们喜欢和:)讨论

#2


I think that the most important factor in choosing a framework is the existence of good documentation. If you can't find good docs for using plone in the way that you want without having to ask here first, that's all the "evaluation" you need.

我认为选择框架最重要的因素是存在良好的文档。如果你找不到以你想要的方式使用plone的好文档而不必先问这里,那就是你需要的所有“评估”。

I'd stick with Django.

我坚持使用Django。

#3


Don't use Plone as Framework.

不要将Plone用作框架。

Plone is an CMS. You can use it as framework,You can use Zope2 application server + Zope3 component architecture but I don't recomended to do this. Plone was designed to be a CMS so why You want use it as framework?

Plone是一个CMS。你可以使用它作为框架,你可以使用Zope2应用服务器+ Zope3组件架构,但我不建议这样做。 Plone被设计成一个CMS,为什么你想用它作为框架?

Why you shouldn't use Plone as framework?:

为什么你不应该使用Plone作为框架?:

  1. Plone is Slow!!! 30 sec. on every restart is too much. When You change something, you need restart. Autorestart(http://plone.org/products/collective.autorestart) doesn't help, you still need to restart Plone any time You change a zcml, portlet's code and sometime with python code.
  2. Plone很慢!!! 30秒每次重启都太多了。当你改变某些东西时,你需要重新启动。 Autorestart(http://plone.org/products/collective.autorestart)没有帮助,你仍然需要在任何时候使用python代码更改zcml,portlet的代码时重启Plone。

  3. Plone is too complex. So big code base. Different coding styles (old Zope2, new component base Zope3, some parts are written with Grok).
  4. Plone太复杂了。如此庞大的代码库。不同的编码风格(旧的Zope2,新的组件基础Zope3,一些部分是用Grok编写的)。

  5. You will need write xml (Generic Setup).
  6. 您将需要编写xml(通用设置)。

  7. Nobody can say what you must use Archetypes, Formlib, z3c.form or Dexterity?
  8. 没有人可以说你必须使用Archetypes,Formlib,z3c.form或Dexterity?

  9. Plone doesn't have good documentation. Too much old documentation (plone.org/documentation) and there is no place where you can read what is the right way to do. The only good documentation is in Martin Aspeli's book (martinaspeli.net/plone-book) but you will need more and this book isn't open, so You will need buy it.
  10. Plone没有很好的文档。太旧的文档(plone.org/documentation),没有地方可以阅读正确的方法。唯一的好文档是在Martin Aspeli的书(martinaspeli.net/plone-book)中,但是你需要更多,而且这本书没有开放,所以你需要买它。

  11. Plone has so many products but if you need really stable and quality stuff you will need write your own.
  12. Plone有很多产品,但如果你需要非常稳定和高质量的东西,你需要自己编写。

  13. Plone is Slow!!! Forget test driven development.
  14. Plone很慢!!!忘记测试驱动的开发。