I'd be very interested in seeing that. As a Pyramid first-timer, I find the documentation itself to be very solid. What I miss are the cookbook-style blog posts which spring up when projects have been around for a long time (How to do X with Pyramid). So, any such tutorials would be very much appreciated!
On 1 July 2011 05:02, Eric Rasmussen <[email protected]> wrote: > Hi Kristian, > > For UI-intensive applications I like to go the ajax route. It works well > because Pyramid can focus on tasks like security, validation and processing > of data, and updating the database, while only returning the minimal amount > of information the client-side application needs to function. This could > mean returning a json reply that everything was ok, flashing back a message > that it isn't, or sending only the snippet of html needed for a form or > other feature. The javascript then makes decisions about where and how those > responses interact with the client. > > I've found that during the development phase this often keeps things much > simpler (provided you're willing to learn a javascript framework and/or a > lot of javascript), and makes it easy to separate out the ideas of what the > client sees vs how you handle data on the server. > > I've been stalling for months on writing a tutorial to demonstrate how you > can structure a UI-rich application with Pyramid, partly because it'd rely > heavily on YUI for the client-side features, and that's not something > everyone wants to learn or use. It comes down to me being most comfortable > with YUI and too stubborn to use another framework, though I believe the > Pyramid techniques would work well with any javascript framework. If there > is a real interest in this I can try to put together a shortish demo. > > Take care, > Eric > > > > On Thu, Jun 30, 2011 at 2:43 PM, Kristian Benoit < > [email protected]> wrote: > >> I'm not so familiar with web development and am currently writting a >> social network like app using pyramid. >> >> It seems to me that setting a renderer (inheriting a global layout) to a >> view and passing a few variables to modify the content of that renderer, is >> a little limited. I was inspired by the way deform works and thought about >> creating widgets (rendered html code) in the views, and pass those to the >> view renderer. >> >> That's not so much the design style that tutorials showed me, but seems >> much more object oriented. I'd like to know a little more about the >> techniques and patterns you are using to have good designs. >> >> Thanks, >> Kristian >> >> -- >> 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. >> > > -- > 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. > -- 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.
