miyagawa at gmail.com
Fri Jun 30 15:17:12 BST 2006
On 6/30/06, Simon Wistow <simon at thegestalt.org> wrote:
> > Yes, they're horrible. I'm very sorry about that and I appreciate any
> > feedback to make it suck less.
> At least you *have* documentation. Most of my big projects don't get
> released to CPAN or have a website.
> After installing half of CPAN (perhaps hitting 'y' to every optional
> dependency wasn't such a good idea :) I'll admit that plagger was
> amazingly easy to install.
Thanks. Yeah, hitting "y" for all the plugins is a very bad idea :)
> I'll join the Plagger dev list but my suggestions would be
> 1) trimmed down core distro - just enough to be minimally useful
> (maybe just handle consuming and generating rss at first)
Yeah, I plan to do this on version 1.0.
For now, I recommend developers to commit all the plugins into svn
core to ease out the issues of plugin mutual dependencdies and 100
times of typing install from CPAN, but splitting out the core, minimul
distro should be a good thing to do.
> 2) the website should have a front page that says "This is plagger -
> this is a screen shot - it can do this this and this"
Agreed. The problem is that Plagger can do (virtually) everything that
you want, if you write plugins to deal with that. Maybe I'll stick
with most useful ones on the top page and say "Of course you can
possibly do this, this and that by writing plugins."
> 3) A proper quick start - it took me a while to realise that there was
> no mod_perl handler or anything and plagger ran as a cron job
> 4) Descriptions of which each of the examples are - I guessed what I
> wanted was a planet but I have no idea what the other config files
> 5) Comment the config files to
> 6) Make the plagger script quieter - only spew errors out to STDERR. At
> the moment I've had to do
> plagger -c config.yaml >/dev/null 2>&1
> which means I'm missing any errors
You can add:
to shut it up. (Yes again, no documentation :/)
Glueing Log::Log4perl (or Log::Dispatch) for pluggable logging is also planned.
> 7) A list of plugins and what they achieve. Each plugin should have
> example, commented config in their SYNOPSIS
I'm sure most of recent plugins have the example config in SYNOPSIS,
but there're still some leftovers.
> 8) Simple docs on how to create a plugin
> 9) Use File::ShareDir to put all the assets in and make that the
> default. If necessary give a plagger command line option to copy them
> to the current directory
> 10) A tutorial on how to write a new skin would be great. A list of
> other people's skins would also be fantastic
If you use "sixapart-std" as a skin, it's Six Apart's Movable Type /
TypePad compatible and there would be a good document how to create
one somewhere on the web, like http://www.thestylecontest.com/
Thank you so much for the very valuable feedback.
More information about the london.pm