Re: pycon talk?
will guaraldi <[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.devel |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 29 Dec 2004, Ted Leung wrote: > > Thanks for the quick feedback. Just one piece of clarification. You > don't have to bust your tail to get all the documentation all lined up. > We'll have to supply a paper for the conference in March, so we have > some breathing room. We just need an outline of the presentation. > More comments below Oh, right. Duh! Though, I'm trying to get the documentation to a critical mass of "I'm a new user--what do I need to know to get up and running *happily*" centralized into one place before doing the PyBlosxom 1.1 release. So it's all good. > On Dec 29, 2004, at 11:46 AM, will guaraldi wrote: >>> * plugins >>> * comments >>> * categories >>> * archives >>> * searching >>> * metaweblog >>> * caching >>> * conditional http >> >> This part I'm a little hesitant about. Are you planning on talking about >> how these plugins fit in with PyBlosxom's architecture? Are you planning >> to talk about how to install these plugins? If the latter, then which >> plugins are you talking about specifically because, for example, there are >> several searching and archives plugins in the plugin registry. >> >> I dunno... I think if it were me, I'd do a quick blurb on plugins in >> general: where to get them, how they're generally installed and configured, >> and what resources exist to build your own. Then maybe list some of the >> plugins that are currently available. > > The focus in this section is configuring and installing. I want to give > people an idea of what's there. The list of plugins is taken from my > config.py, although I did generalize things like archives and searching. > I'll probably just talk about what I have installed. Ahh... Ok. Yeah, that sounds good. > Good points that I didn't have are: > 1. the plugin registry > 2. general plugin installation and configuration. I can talk about the second point in the plugins chapter I write because it's something that all plugin authors should be thinking about when writing their plugins. I have vague memories of writing some of it in the plugin tutorials I wrote a while back. >>> * Pyblosxom Architecture and Internals >> >> If you can be more specific about what this entails, I can help you >> write/plan it out. I did up some lifecycle stuff in the pyblosxom >> manual, but haven't gotten in-depth about callbacks and plugins yet. >> Chapter 7 is about callbacks. Chapter 8 will be about building >> plugins. > > There's two categories of stuff here. First I think I want to talk > about plugins, because I hope that more people will write plugins than > hack the core. But I also want to talk about the core/framework because > we do have some things (see below) where we could probably use some > help. Cool. >> Going beyond that, I have no idea how solid the xmlrpc_bloggar and >> xmlrpc_metaweblog plugins are or what state they're in. > > I use the xmlrpc_metaweblog (which in some cases falls back to > xmlrpc_blogger) on a daily basis to post and manage posts via Ecto or > MarsEdit. For that last little while I'm the only person that's worked > on them, so you can consider them mine. I also will probably work on an > Atom API plugin one of these days. Right--I had forgotten you wrote it. I need to figure out a way of listing all the plugins that come in the contributed feed and associating them with maintainers. Anyhow... all in good time. Rock on Ted-- /will ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/