On 22 May 2010 21:25, Tim Black <[email protected]> wrote: > At least partial examples of 1 & 2 are provided by by TurboGears, though > not as plugins.
As I understand it (I had a looked a *bit* before) TG admin is based on dbsprockets + toscawidgets: <http://turbogears.org/2.0/docs/main/Extensions/Admin/index.html> Is there any way for that tgext.admin to be re-usable in pylons? > Though this is not what you're looking for, I'll mention that I'm > beginning to create a very simple app-specific plugin framework here > https://blueprints.launchpad.net/reformedchurcheslocator/+spec/feeds-plugin-framework. > I've outlined a basic strategy for implementing the framework, but hope > I might be able to glean some insight from other plugin frameworks as I go. Interesting. From a quick look at the docs I assume this is to do with caching (atom/rss?) feeds? If so that at least one other example of a standard plugin use-case and I we ourselves have implement this kind of feed caching in http://www.openshakespeare.org/ as a way of pulling content from a wordpress CMS into the main site (that's how word of the day is generated for example: <http://www.openshakespeare.org/word/read/bilbo>) It also reminds me that another useful plugin would be (AMQP) messaging/celery integration. Again this is something we have experience of and could share our current approach. Regards, Rufus > Tim > > On 05/22/2010 02:12 PM, Rufus Pollock wrote: >> Hi, >> >> At the Open Knowledge Foundation (http://www.okfn.org) we have used >> Pylons for several of our projects (http://www.okfn.org/projects/). We >> think it is a great framework. >> >> However, there are some standard components which it would be nice to >> be able to "plugin" in a standard way -- e.g. users + auth, admin, >> settings, comments (more examples plus details below). In many other >> frameworks/platforms (including e.g. Django) you do indeed see some >> sort of plugin frameworks in which this sort of functionality does >> indeed become a plugin of some kind. >> >> Now, I'm well aware of Pylons different and more flexible (and IMO >> better) approach compared to e.g. django. And that this architecture >> may mitigate against providing any standard "plugin" (e.g. how do we >> know which template framework -- mako, genshi, jinja, etc -- a given >> pylons user is using ...). >> >> However, I think it is still possible to do something useful along >> these lines -- even if a formal plugin framework isn't >> possible/required just "packaging" up best-practice(s) *pattern* for >> how to do standard stuff it would be very valuable (especially if a >> pattern kept up to date!). >> >> Below I've given a list of some examples of the sorts of things that >> could be "plugins". What else should be on that list? Is there >> interest in having plugins? >> >> Regards, >> >> Rufus Pollock >> Open Knowledge Foundation - http://www.okfn.org/ >> >> >> ## Pylons plugin proposals >> >> ### 1. Users and Authentication - basic plugin to do users and >> authentication out of the box >> >> * Openid + Form (email confirmation etc) >> * Build on existing plugins (repoze.who, authkit, whatever) >> * Tie in to existing model (sqlalchemy) object (or provide demo code >> to create it) >> * Even if just a demo that *works* it would be useful >> * We've now done this ~ 6 times. There are commonalities and even if >> this were just a demo it would be useful >> >> ### 2. Admin - lightweight admin system >> >> 1. Model CRUD - provided an existing solution nicely wrapped up or >> just document how to do it and ensure it really works -- we've used >> FormAlchemy plenty (and other options) but ensuring something "just >> worked" would be useful >> >> 2. Settings module - think wordpress settings/options system >> * DB Table + web user interface >> * Config in db rather than ini file >> >> ### 3. Mini-CMS >> >> * Simple content management - post/page table plus editor >> * Slave CMS - pull content from an RSS feed from e.g. wordpress or other >> CMS >> * We implemented this ourselves in http://openshakespeare.org >> >> ### 4. Commenting >> >> * Commenting is a common functionality across many applications >> * A basic plugin that providing commenting functionality either >> directly or pased on an existing pluggable service (e.g. disqus) would >> be extremely useful >> >> > > -- > 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. > > -- Open Knowledge Foundation Promoting Open Knowledge in a Digital Age http://www.okfn.org/ - http://blog.okfn.org/ -- 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.
