First, I would like to say that we have not announced Ptah formally because of two reasons:
1. The documentation is underwhelming. I apologize for that. It can be found here at readthedocs: http://ptahproject.readthedocs.org/en/latest/index.html 2. We wanted to push features down into Pyramid. It seems that with Pyramid 1.3 - we should be synchronized to the point where we are comfortable. Congrats to mcdonc for doing the work on 1.3 the release of Pyramid. > I'd like to elaborate a bit more on the idea before I address the > rather pertinent issue of existing efforts (in particular the content > management systems Ptah and Kotti, both written directly for Pyramid). Ptah is not a content management system. It has changed substantially from its original intent. While it contains libraries to make writing a CMS much easier (ptah.cms.Content, for example) it really is more of a "structure" in which to write pyramid applications. And provides very high level functionality, as you said: forms, management ui. There is quite a bit there and the scaffolds demonstrate a lot of features. ptah101 shows management ui and form library. ptah102 introduces models ptah201 introduces security ptah301 is a fairly sophisticated "cms" example For instance, the Ptah Manage interface is quite generic. And is meant to plug in your own "management" functionality. What does Ptah come with: - You get a "manage" ui - You get CRUD for your models (provided they have __type__ attribute) - You get visibility/reflection into sql table structure - You have forms and quite a bit of view "support" libraries such as libraries. (see the colorpicker widget in ptah101) - Security model - You can use traversal (ptah301) or urldispatch (ptah102) - You can use it like a library. Ptah is not your application. - Like Pyramid, Ptah is fast (measuring Ptah301) Ptah is 99-100% test coverage and is being used in production. Ptah is not an application, it is a library/frameworkish, which you can use to make the application of your dreams. > There's a great potential in bringing the various technologies > together in an application server that we can build upon and expand. Ah men. > What we've got now is a lot of code and little effort to integrate it. > Any content-based application needs: user management, search, content > factories, unique id service, mail service, cache control, transience > (temporary objects), message queues, logging, statistics, support for > software upgrade, database maintainance, alert systems, etc. I agree.You need a framework, at the very least, to show such UI in a centralized manner. Ptah's management UI is quite primitive but extremely useful. And the fact that it does nothing means its easy for people to use it. Ptah has "content factories" inside of its ptah.cms package. So the only thing that is necessary for the above is for people to buy into Pyramid/Ptah's security model. We have a concept of Roles. If people agree then we can start to build things such as search. We do not have a "unique id" service although we do have a concept of a "unique id" called a uri. Which is another thing we would like for people to comment on. > What about Ptah? > https://github.com/ptahproject/ptah Yes, please give it a go. And give us your thoughts. > First, what exactly is Ptah: It's a "fast, fun, open source high-level > Python web development environment". In more concrete terms, it's a > content management system that has been somewhat deconstructed into > "library code". The fact that it's only somewhat deconstructed means > that you can very quickly reconstruct the system. There's even a > tutorial included that does exactly this. Yes. > It's still early days. It's clear that documentation was an > afterthought, but there's some formal documentation in the repository > (as restructured text). It's mostly missing from the actual codebase. Yes. Anyone who wants to contribute can join #ptahproject on freenode or subscribe to mailing list. http://groups.google.com/group/ptahproject > While a substantial effort has gone into the project, it's a hard sell > without any prose to lure you in. I agree. A reason we have not publicly talked about it except among core Pyramid audience. > It also comes as a single package that spans a lot of functionality > including a complete forms library. It has decided to reinvent quite a > few wheels, although some of them have been ported over and simplified > from the Zope Toolkit. > > Note that Ptah also wants to be an "environment" and it has to compete > on those terms: > > - Where's the design defense? > - Why isn't the codebase littered with excellent prose that might > justify its design? > - Where's the call for collaboration? I agree. All of those things are in the pipeline. It is just a matter of paid work, validation of design (which we are still doing), and contributing. Design validation is near impossible - we have been asking people for feedback but rarely get any. > That said, I think there's a lot of good code in there. It might > benefit from being based on the platform I dream about. Well, why not give us some feedback? ptah 0.1 was released in pypi, so you can install it if you have Python 2.7 $ easy_install ptah $ bin/paster create -t ptah101 myapp $ cd myapp $ ../bin/python setup.py develop $ ../bin/paster serve settings.ini Pretty easy. cheers runyaga -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
