On Sat, 2010-11-06 at 10:06 -0700, Mike Orr wrote: > A few incompatibilities have been discovered between Pyramid and WebHelpers. > > http://bitbucket.org/bbangert/webhelpers/issue/54/pyramid-incompatibilities-paginate-flash > http://bitbucket.org/bbangert/webhelpers/issue/53/paginate-in-pyramid > > Paginate, Flash, and everything in webhelpers.pylonslib depend on > Pylons' magic globals, which don't exist in Pyramid. For Paginate, > you'll have to write a callback function wrapping > ``pyramid.url.route_url()``; you'll need a separate function for each > route. For Flash and pylonslib, you'll have to modify the helpers to > pass the request/response/session in a Pyramid-friendly way. > > I haven't decided yet how to accommodate these in WebHelpers. I'll > probably modify Paginate and add another fallback. As for pylonslib, > I'm not sure whether to create a pyramidlib directory or make them all > generic. > > * Flash: This is frequently-used enough to go into Pyramid directly.
Sure. Instead of something that uses thread locals, I'd like to make this an API of the session object (e.g. session.flash(...)). If someone can propose a reasonable set of methods on the session object for flashing I can add them. > * Grid: A generic version is in webhelpers.html.grid. > > * Minify: I've never used this. Can it go into Pyramid. > > * Secure_form: I've never used this. Can it go into Pyramid? Pylons > imports it into pylons.decorators.secure . I think maybe the functionality of most of this stuff should be reintroduced as separate libraries (or maybe not at all). - 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-de...@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.
