On Fri, 2011-03-04 at 12:00 -0800, Mike Orr wrote: > On Thu, Mar 3, 2011 at 11:42 PM, Peter Alexis <palexis2...@gmail.com> wrote: > >>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. > > This is where Pyramid's multiple goals come into play. The BFG-ish > users say that Traversal was immediately understandable to them and > they could apply it right away, while they find URL Dispatch > cumbersome. > > ZCML configuration was moved to the back of the manual for exactly the > reason you describe, because it was a stumbling block for the large > number of Pylons users who were about to come, and the BFG users knew > where to find it in the back of the manual. I'd support moving > Traversal to the back except I think there'd be more resistance to > doing that than there was for ZCML. Traversal is central to an > application if you're using it, whereas ZCML is "just zis > configuration format, y'know". [voice of Zaphod Beeblebrox's > psychiatrist]
There is no ZCML in the Pyramid docs anymore. It was all moved to the pyramid_zcml package docs, and in order to use ZCML, you must install that package. - C -- 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.
