Dear all, Just thought that I add my two pence worth. I am not a web-hacker, I'm a scientist. I use Pyramid to expose my science as web apps/services.
If I am not a web-hacker then why don't I use something that is "simpler" than Pyramid. Personally, because the science that I want to expose does not fit easily into the more "opinionated" out-of-the-box solutions. So what is the difficulty with using Pyramid? Some people believe that it is all explained in the docs, and I'm sure it is, but Pyramid forces users like me to think harder about some of the underlying concepts of what they are trying to do. Let me explain by some illustrations. Let us start with the "hello world" example. When I look at it my first question is: what on earth is wsgi? It took me a couple of hours of surfing the web and reading to get my head around this. If this had been explained neatly in a book for "beginners" it something that I would have benefited from. After getting my head around wsgi I realised that I really needed to get a better understanding of what http was. Up until this point all I had needed to know about http was that it was something that my URLs started with, oh and then there were get and post. Whilst reading up on http I found it useful to get to grips with the WebOb module. Again, Pyramid makes certain assumptions that the users are familiar with these concepts, so if there was a "beginners" book for Pyramid users I think that it could benefit from some introductory sections on these topics. I did have the idea of putting some of these thoughts into a book and started writing some of it down in a google doc. If anyone is interested I'm happy to share it with them. Not because I think that what I have written is particularly good, but because it may give some inspiration. Let me know. Finally, I would like a Pyramid book to contain lots of small, self-contained example applications. I find it easier to understand what is going on from reading example code rather than looking at API or the "official" documentation. However, the problem with example code is that it does not always fit into what one wants to achieve, I therefore find it most productive to look at many small, self-contained to examples to work out what the similarities and differences are. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
