I have just released OpenGuides 0.60. It's available from
and, in due course, CPAN.
Debian packages have been uploaded to unstable. Please note, I'm
reworking the way I provide Debian packages; this release won't be
available from my repository on larted.org.uk. I will post early next
week once I have tested how the Debian package installs on etch and
Kake lists the sellings points as:
- improved stylability of the edit form
- the possibility of excluding categories and locales from the random page
- new random page link macro
A full changelog is below:
0.60 13 May 2007
Removed footer search from edit page (shouldn't have been there).
Upgraded Module::Build requirement to cope with API change.
Added new parameters to action=random - you can now supply category
and/or locale to get a random page chosen from that category/locale.
To go with this, added a new macro:
@RANDOM_PAGE_LINK [[Category Pubs|View a random pub]]
Fixed bug in OpenGuides::Feed - HTML equivalent link now works even
if your script_name isn't blank.
Rewrote the HTML of the edit page to use <div>s rather than tables.
Note that you will probably want to provide at least basic styling
for these classes. As part of this, added a new template,
Moved node image boxes below phone/address/etc on the edit form, and
moved summary field from openguides information section into main
Made div#maincontent on the edit form wrap the preview view only, not
the whole form.
Added links to the "revision N" and "Last edited" text in the navbar.
Added format => "raw" option to OpenGuides::Search->run to let you get
your results back as a hash.
"New page name" disappears when you click in the field (it doesn't
make anything other than "New page name" diappear).
Move node RDF generation from inline to node_rdf.tt and replace
home-grown escaping with encode_entities_numeric from HTML::Entities
(technically this is an added dependency, but we already require
the package it comes in, via Wiki::Toolkit::Formatter::UseMod).
Move random page functionality from wiki.cgi into OpenGuides.pm and
add some tests.
Add config options to let admins omit category and/or locale pages
from the list of pages that can be returned by the Random Page link.
Use full URLs for all links in navbar, so people can INCLUDE navbar.tt
in their own scripts. (May revisit this later using "base href".)
Added some stylesheet hooks to newpage.tt; see README.CSS for details.
Documented the stylesheet hooks in the admin interface (see README.CSS)
Bugfix: uninitialized variable warning in script_url
Bugfix: Make sure clean target works
----- Forwarded message from Michael Kr?ll <michael.kroell(a)uibk.ac.at> -----
From: Michael Kr?ll <michael.kroell(a)uibk.ac.at>
Subject: [Conferences] YAPC Europe 2007 Reminder - CFP and CFH Deadlines
Date: Tue, 08 May 2007 11:02:55 +0200
The deadline to submit Hackathon proposals for this year's YAPC Europe
in Vienna is just around the corner. Please do not forget to submit your
proposals by Sunday, 13th May 2007. Information on what we're looking
for exactly and what we can offer to moderators (e.g.
travel/accommodation refund) can be found at:
The Call for Papers deadline is less than 3 weeks away from today:
The theme for this year's conference is "Social Perl", which we hope
will inspire submissions for this and related topics. If Perl has helped
you or your company to get people together, or if you can report how
Perl is "social" to other programming languages, or how Perl may profit
from inspirations from other languages, we'd like to hear about it.
Although this is our main topic for the conference, it will not be the
only one, and as such we will also be accepting talks on just about any
Types of talks include 20 or 40 minutes talks, 60-90 minute tutorials,
or 3 hour Hack-a-thons, BOFs or Workshops.
There are still some slots free!
Hope to see you in Vienna,
on behalf of Vienna.pm
063A F25E B064 A98F A479 1690 78CD D023 5E2A 6688
Conferences mailing list
----- End forwarded message -----
#!/usr/bin/perl ... http://domm.zsi.at
I was muttering at Kake in the pub a few days ago about making a "Guide
in a Box" available. By which I mean an image of a bootable
disk/filesystem, with OS, web server, database and OpenGuides all
pre-installed and configured. On first boot, it would ask for minimal
configuration information - IP address, guide name, passwords. I can
see this being useful for people who want to run a guide but are less
technically minded - they'd be able to just use the filesystem in
VMware/Parallels/Xen/whatever without having to know about what's going
on underneath. It might also be useful for developers who could use it
as the basis for installing a guide hacking environment on their
machines without it interfering with anything else that they do.
David Cantrell | London Perl Mongers Deputy Chief Heretic
It's my experience that neither users nor customers can articulate
what it is they want, nor can they evaluate it when they see it
-- Alan Cooper
Hello. I've been thinking recently about the various different
OpenGuides we have floating around, and the individual styles that
they're all evolving.
I've been doing a bit of copyediting on some of the non-RGL guides
recently; I feel pretty comfortable doing this on the Oxford Guide
because Socks thanked me for it on #openguides. I was wondering if it
might be a good idea if we maybe chose a week some point soon to visit
each other's guides and do a bit of editing. Even if we're unfamiliar
with a particular city, we can still do typo fixing, tidying up
formatting, sorting out any duplicated content, making sure
everything's in the category it should be in, even adding new
categories to pull together existing content, or adding content such
as external links if that's appropriate for that particular guide.
(Maybe making progress on the OGL Great Renaming could form part of
this, if that project is still going on? Though I wouldn't want it
to dominate the week.)
I think this would build up the community feeling a bit more, as well
as breathing fresh life into all of the guides, and being a project
that even non-coders can get their teeth into. What do people think?
A prerequisite for this would be some documentation about what
is/isn't appropriate on a given guide, since this isn't always obvious
- for example, I've not been sure whether it's appropriate for me to
add new categories to the Oxford Guide - but having this documentation
would be very useful anyway, and is a worthwhile project in itself. I
think it's also a project that _demands_ external input, since it's
only by having other people asking "is it OK to do this?" that we can
be sure we've set down the things that are so embedded in our minds
that we never actually think about them.
In the absence of a redesign of openguides.org (I just haven't found
the time, don't know if anyone else has?) I offer the following
suggestion for fitting the Randomness Guide into the list of links:
It's not perfect by any means, but it's good enough, I reckon. Any
objections to me committing this to svn and asking Earle to update the