Ferris 2.2 has been released.

Ferris Framework

unread,

Jun 30, 2014, 4:32:20 PM6/30/14

to ferris-f...@googlegroups.com

Hello everyone,

I'm happy to announce that Ferris 2.2 has been tagged and released.

Ferris 2.2 represents four months of improvements, bugfixes, and new features. Most notably the new Google API helper will make using the Google API client even easier and our new Caching module provides much needed flexibility in keeping data around. There's a more detailed changelog in the documentation.

I'd like to make a special thanks to our open-source contributors for adding features such as the excellent CSRF component (thanks, Robert Dodd!) and various bug reports, pull requests (thanks, Dustin Smith!), and documentation updates. The framework could not exist without you.

A few notes about version 3

Ferris was created while the Google Cloud Platform consisted only of Google App Engine. Things have changed quite a bit since then but the core ideas in Ferris haven't.. As ideas have been tossed around for Ferris 3, we're starting to notice that full-stack MVC frameworks like Ferris are beginning to be left in the dust as the landscape shifts in favor of multi-device applications. We're aiming to make a huge shift in the design of Ferris to better suit the needs of modern applications. We're going to aim towards making it as easy as possible to create APIs with Ferris. We're going to be adopting Google Cloud Endpoints as a cornerstone just as we did with webapp2 in the beginning. We want to make it possible to create a back-end with ease so you can kick back, relax, and worry about your front-ends. I'm happy to hear if anyone has any thoughts or ideas that could better improve Ferris going forward.

We're also thinking of ways we can help all App Engine developers, not just those who use Ferris. We have a great test runner that works with any app engine app, a helper library for protorpc, and a package installer. We're planning on splitting more parts of Ferris out of the core (like our search helpers) so that any application can use them. If you're interested in helping with any part of this please let us know.

Thanks,

Jon

David Sheffield

unread,

Jul 3, 2014, 2:40:37 PM7/3/14

to ferris-f...@googlegroups.com, ferris-f...@googlegroups.com

Thanks for the wonderful framework Jon! Moving Ferris to a "backend" framework works perfect for our environment. I've had better luck getting team members to contribute on our projects when we have used the api / jscript method instead of the Python / Jinja method. Just out of curiosity, what front end framework does cloud sherpas like the best for web and mobile web development? (Angular, Ember, etc...)