Hi All,
I'm pleased to announce a new release of mortar_rdb.
This package ties together SQLAlchemy, sqlalchemy-migrate and
the component architecture to make it easy to develop projects
using SQLAlchemy through their complete lifecycle.
Changes in this release were:
- Pass None as the default
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
Hi gang.
I put up a (fork of jayd3e's) repo for deform_mako templates:
https://github.com/mfeif/deform_mako
I converted ALL of the templates, and attempted to stay as true to the
original as possible (not implementing any style/markup changes from the .pt
files).
I'm sure I broke a couple of
It's the main() function in your application's top-level
myapp/__init__.py module.
On Wed, Jun 29, 2011 at 7:11 PM, jerry jerryji1...@gmail.com wrote:
Hi Mike,
I'm curious to know where is this main() for Pyramid you were
referring to?
Thanks.
Jerry
On Jun 30, 5:30 am, Mike Orr
On Thu, 2011-06-30 at 18:10 -0500, Michael Merickel wrote:
A good test may be to fix the deformdemo to use these templates.
https://github.com/Pylons/deform/tree/master/deformdemo
I'd just copy the deformdemo into pyramid_mako and make sure its tests
pass after changing the copy to use Mako.
On Thu, 2011-06-30 at 21:53 -0400, Chris McDonough wrote:
On Thu, 2011-06-30 at 18:10 -0500, Michael Merickel wrote:
A good test may be to fix the deformdemo to use these templates.
https://github.com/Pylons/deform/tree/master/deformdemo
I'd just copy the deformdemo into pyramid_mako and
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
