On Thu, Oct 8, 2009 at 3:46 PM, Matt Feifarek <[email protected]> wrote: >> What we need is somebody who >> regularly uses Pylons on App Engine to maintain the howto. > > I don't know how long my commitment to use GAE will continue. I'm basically > evaluating it now with a project. If I can help out the general community > now, great. If things don't go well with the over-all experiment, I may fall > out of the loop myself, but for right now, I can commit to keeping this doc > up-to-date with what I discover.
That sounds good. > I like the idea of a paster create -t pylons-appengine... that would be > excellent. Somebody just needs to write it. If you can put together a list of what it should contain, and how it should differ from the regular Pylons template, we can get somebody with more experience to actually create the template. Application templates can also ask yes/no or text questions, and contain if-blocks. So if you think those would be useful, just outline what they should do. Off the top of my head, the model.py should contain commented code for a typical (simple) Datastore model. Not all apps will use Datastore, but those that do will want something to start from. -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
