fyi: Blosxom 3.0+1i

Joseph Reagle <[email protected]>
Newsgroups gmane.comp.web.pyblosxom.user
Organization MIT
Message-ID <[email protected]>
I'm thrilled to announce the future of the Blosxom personal publishing 
system! 

 (Could that have been any more dramatic? ;-) 

 I've bundled up the first alpha of Blosxom 3.0 for perusal, fiddling with, 
and discussion by mature (aka stalwart, brave, Perl-savvy) Blosxom folk 
with an eye to seeing what the future of Blosxom holds and just how to 
write plugins for the thing. 

 It's been massively refactored, all but rewritten, object-oriented, and 
usable as a CGI script, module, or indeed subclassed. Oh, and I'm afraid 
it's grown a bit, now weighing in at a massive 15K (slightly less, 
actually) ;-) 

 It is by no means anywhere near fully baked and should not be considered in 
any way, shape, or form, to be ready for deployment. Things will change. 
Other things will break. If you're not ready for that, you'd best watch 
from the sidelines. I say this not to be rude, but for your own protection. 

 Blosxom 3.0 should run right out of the box. Unzip, drop somewhere 
Web-accessible, and visit http://servername/cgi-bin/Blosxom.pm (or 
appropriate). You may need to change its filename to Blosxom.cgi to have it 
run on your server. Blosxom works from its local directory and expects to 
find al the bits and bobs in its package thereabouts 

 The current Blosxom 3.0 package consists of: 
The Blosxom module (Blosxom.pm) that may be a) run as a CGI script with 
about the same effect as running Blosxom 2.0 out of the box, b) subclassed, 
or c) used as a module, naturally enough.
 
A data directory, wherein all entries, flavour components, settings and 
handler configuration files lie. I've prepopulated this with HTML and RSS 
templates, some posts (including this one) with which to test Blosxom, and 
basic settings and handlers files.
 
A plugins directory, wherein all plugins live. I've included a couple-three 
plugins which do little in particular, but provide some idea (until I get 
to the full documentation) of how plugins work.
 
A state directory, wherein to keep an state information used by your 
plugins.
 
Blosxom 3.0 will be distributed, eventually, with such a layout (subject to 
change), some goodly sprinkling of flavours or themes (designers, please do 
volunteer), a nice collection of modules that'll work well cross-platform 
and don't require anything more than themselves, and on-board documentation 
in the form of blog posts. 

...


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.