Chameleon.* will not work because it needs to generate code objects and
that's forbidden in GAE (no marshal.py, parser.py or direct calls to
new.code() or similar). BFG itself works just fine. Well, at least the
starter app minus chameleon does:
BFG developers who want to use GAE will need some other templating solution.
Carlos de la Guardia
On Sat, May 2, 2009 at 1:11 AM, Chris McDonough <chr...@plope.com> wrote:
> On 5/1/09 11:52 PM, Martin Aspeli wrote:
> > I think there'd be enormous value in a "Getting started on GAE" tutorial
> > on bfg.repoze.org.
> > For that I'd like to see:
> > - a skeleton code project
> > - an understanding of how to use the GAE model storage in a BFG
> > application
> > - some kind of basic CRUD forms for such
> > BFG feels like a good match for GAE, especially for people with a
> > Zopeish inclination. I did a GAE project recently and used Google's own
> > webapp framework, which was OK, but rather bare. I looked into using
> > Pylons, but it seemed to require some rather shaky patches to the GAE
> > environment. So probably, this could be an interesting niche for BFG.
> Tim Hoffman has been trying to get it going on GAE, and I think the trunk
> works except for the chameleon.zpt bits (there are apparently no "ast" or
> "compiler" modules on GAE).
> - C
> Repoze-dev mailing list
Repoze-dev mailing list