>I mentioned "unless there are new magical docs", because I think 99% > of the problems with pyramid right now are the docs. They're hard to > sift through (rather dense) and easy to miss things in. Meanwhile, > docs for projects like Django and Rails are really light and breezy... > and link to the more-in-depth specialized docs and api docs.
I feel more or less same, 'coz I was finding much difficulty in understanding the framwork from the document. Escpecially, the registration, configuration, the Z* things etc... The framework is so powerful, but lack of clean medium to get into it causing people to take U turn. It would be much better if we can re- arrange/modify the documents in a way to take out Z* things, traversal and all complex topics to 'Advance' section seperately. So that, people interested in squeezing full power/flexibility can go through those section while beginners or who come from other framework or technologies can feel better easly and start working on. I'm pretty sure, people would consider/refer advance section once they feel comfortable. But Its almost certain that, without un-cluttered, well organized document, its difficult to attract and get more contribution towards Pyramid. my 2 cents. On Mar 4, 1:34 pm, Jonathan Vanasco <jonat...@findmeon.com> wrote: > I think the criticisms in the post -- and their defense here -- are > really important. I've had the same struggles. > > While many are not technically valid , they appear to be so because of > the documentation and positioning of pyramid. > > Pyramid is really powerful framework, but its also quite low-level. > Most frameworks are high-level. While this can be very powerful, it > can also be frustrating. > > As an example, look at the concept of Auth -- the pyramid auth system > is ( unless there are new magical docs out there ) very much > positioned at doing some fine-grained authentication ( users, groups, > actions) based on each 'view'. Most other frameworks use advanced > plugins for this sort of functionality... and have much simpler > plugins to handle authentication for each handler / controller / etc > as a package. ie: for the majority of web applications, the state of > being "logged in" is the only requirement for access to every method > of a class/package, and having to (re)declare auth policies per method > becomes daunting. > > I mentioned "unless there are new magical docs", because I think 99% > of the problems with pyramid right now are the docs. They're hard to > sift through (rather dense) and easy to miss things in. Meanwhile, > docs for projects like Django and Rails are really light and breezy... > and link to the more-in-depth specialized docs and api docs. -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
