pyramid_registration does pretty much what Apex does - or appears that it will. Apex is just auth + registration on top of pyramid. CSRF and Flash messages were added into it because CSRF should be included in any front-facing webapp and Flash messages just made it easier to communicate events with a user when they signed in, registered or their password was invalid. Supporting i18n should be done for any app developed in the 21st century.
Same with Pyramid_openid - which is just authentication with Pyramid using OAuth2 as a provider. At what point does a toolkit become an application? You can't do anything with Apex except auth and registration. You can't deploy Apex as an application - the app would do nothing but allow someone to register and sign in. This is similar to Akhet which is a layer on Pyramid to give developers a more pylons-like environment. Kotti does have CMS features and by definition appears to be an application or framework that uses Pyramid as a base which would be ineligible. I imagine someone new to Pyramid may not find Kotti, or, may not make the association that it has quite a few CMS components available and ready for a Pyramid app. While you may not want to endorse external apps or show preferences, I think it benefits the communities on either side. I'm not really that concerned about it for Apex, but, having an easy to find set of extensions and apps should raise awareness for pyramid - if that is a goal. -- 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.
