My reply follows in my next email.
---------- Forwarded message ---------- From: Graham Higgins <[EMAIL PROTECTED]> Date: Nov 21, 2007 4:27 AM Subject: Re Pylons-compatible CMS tools To: Mike Orr <[EMAIL PROTECTED]> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Mike, On Nov 18, 11:46 am, "Mike Orr" <[EMAIL PROTECTED]> wrote: > Are there any other Pylons-compatible CMS tools > around? I had a paddle around in this area at the end of last year. Purely for my own porpoises, I hacked about with Turboblog, adapting the core from TG+Kid to Pylons+Genshi. It was mainly a proof-of-concept exercise designed to give me some direct experience with issues of integrating multiple apps at the top end of the WSGI stack but it did get me a part-usable blog (http://bel-epa.com/weblog/). I'd be happy to dump what I've got but I'm not sure that it's much of a contribution and it's certainly nowhere near what you described. IMHO, Turboblog's history is instructive to those considering developing Pylons apps for general consumption. Originally developed by Eli Yukelzon in early in 2006, Turboblog was largely ignored by the TG community, to the extent that Eli was disinclined to develop it further and offered it up for adoption. Earlier this year, the project was adopted by Florent Aide and moved to dejavu. The mailing list (http://groups.google.com/group/tb-discuss) reveals a similar apparent lack of interest, with the last posting made in mid-May. I don't know the current status of Turboblog. It may be that the lack of interest that Florent is experiencing is simply coincident with a slackening of interest in TG between Kevin taking a Real Job(tm) and Alberto's redefinition of TG as a pre- developed Pylons installation, but that doesn't really explain why it also languished while under Eli's care, TG was receiving quite a lot of interest at that time. It may be that an effective, well-designed framework (e.g. Pylons) gives developers such a wide range of possible approaches to developing an app that the idea of hacking on a pre-published generic app is less appealing than the idea of hacking it up oneself from scratch. Or, it may be that there just isn't enough critical mass in the userbase ATM to sustain the development of a generic app. Or, we're maybe we're trying to work at the wrong level. I've recently added ElixirGenXML to my stack of interesting things to fire up and test, perhaps that's the level at which we should be working. But even so, a simple thought experiment brings a dash of cool rationality: someone produces a spec of a Wordpress-alike blog for Pylons. How many folks are likely to rush to join the development team? I got quite a lot of illumination from Ben's ruminations on how the early adopters of Pylons took it in a different direction to that which the dev team initially anticipated. As Pylons gains more traction and exposure, the ratio between developers-doing-it-for- themselves and, ah, "deployers" will change and we'll probably see a lot more calls/bleats for deployer-friendly features like TG's DB browser (which people perceive as flattening the learning curve) and ready-built apps that can be deployed out of the box. OTOH, we do seem to be presented with an opportunity to lay down some best practice principles for integrating multiple apps in a single Pylons stack (at arbitrary levels in the cascade), mainly in terms of providing integrated cross-app support for user admin, prefs and privs --- a topic which, up to now, every app developer has felt free to address independently. Unfortunately, it rather requires a stable and commonly-accepted auth'n'auth solution, something which has yet to emerge from the mix, IMO. Cheers, Graham. --- END FORWARD --- -- 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 -~----------~----~----~----~------~----~------~--~---
