Das eez kaput! Sometime around 2002 I spaced the entire database table that mapped individual entries to categories. Such is life. What follows is a random sampling of entries that were associated with the category. Over time, the entries will be updated and then it will be even more confusing. Wander around, though, it's still a fun way to find stuff.
Date: Tue, 10 Sep 2002 11:06:31 -0400 (EDT) From: Aaron Straup Cope To: Ben Hammersley Subject: the unbearable twingularity of it all >From the thinking out loud department : You might be able to rig something using Mail::Audit and the BBDB (written by Mr. Intertwingle himself.) All of which will inevitably necessitate some sort of intersecting of the BBDB and FOAF... http://bbdb.sourceforge.net/ http://search.cpan.org/author/LAXEN/BBDB-1.34/ http://search.cpan.org/author/SIMON/Mail-Audit-2.1/Audit.pm See also : http://aaronland.info/weblog/category/email/recent http://aaronland.info/weblog/archive/4058 # This part is easy and implemented in a gazillion different # ways already. I include it only for thoroughness : http://perl.aaronland.net/rss/ Cheers,
thumb=>"75x50",small=>"25%"
) and generate all the necessary static HTML files, complete with
next|prev links that know which size of the image you're looking at and
links to the other scaled versions of the image. The design is
purposefully simple since eventually the idea is to have the internals
use
XML::SAX::Machines
so that you can filter the output of individual files to your hearts
content. First though, I'd like to add support for
XML::Filter::Sort
on the front-end. Anyway, all the meta-data for an image is read from
IPTC
and
EXIF
tags. The former can be edited in Photoshop and the latter are written
automagically by many cameras. Sadly, the Gimp supports neither and
only allows for comments not exceeding 512 characters in length.
Karl
threatened to put together some sort of hairy, scary document based on
the many emails we exchanged on the subject but I guess he has been
busy enjoying the summer, and rightly so. Oh yeah, and the interface?
use Gallery; Gallery->create(directory=>"/htdocs/images", url=>"mysite.com/images", static=>1, # Don't use Apache::Image::Shoehorn scales=>[ ["thumb","x50"],["small","25%"] ], );
Fulminate \Ful"mi*nate\, n. [Cf. P. fulminate. See {Fulminate}, v. i.] (Chem.) (a) A salt of fulminic acid. See under {Fulminic}. (b) A fulminating powder. {Fulminate of gold}, an explosive compound of gold; -- called also {fulminating gold}, and {aurum fulminans}. web1913
fulminate n : a salt or ester of fulminic acid v 1: criticize severely; "He fulminated against the Republicans' plan to cut Medicare"; "She railed against the bad social policies" [syn: {rail}] 2: come on suddenly and intensely; "the disease fulminated" 3: cause to explode violently and with loud noise wn
use XML::SAX::Writer; use XML::Directory::SAX; use XML::Filter::XML_Directory_2RSS; my $writer = XML::SAX::Writer->new(); my $rss = XML::Filter::XML_Directory_2RSS->new(Handler=>$writer); $rss->exclude(exclude=>["RCS"],ending=>["~"]); my $directory = XML::Directory::SAX->new(Handler=>$rss, detail=>2, depth=>1); $directory->order_by("a"); $directory->parse_dir("/path/to/aaronland.net");XML::Filter::XML_Directory_2RSS inherits from XML::Filter::XML_Directory_Pruner so that it can pass along all the necessary information to a 2RSS::Items handler for populating the
channel/items/rdf:Seq
node (ah RDF, let me rdf:Bag the ways...) In the end, I may have to
subclass XML::Directory::SAX itself and rename the package as a
"Handler" so that I can also pass/enforce ordering, detail and depth
configs. BTW, does anyone know whether the mod_threading
<thr:children>
element can contain <thr:children> of its own?
Pecuniary \Pe*cun"ia*ry\, a. [L. pecuniarius, fr. pecunia money, orig., property in cattle, fr. pecus cattle: cf. F. p['e]cuniaire. See {Fee}, and cf. {Peculiar}.] 1. Relating to money; monetary; as, a pecuniary penalty; a pecuniary reward. --Burke. web1913
pecuniary adj : relating to or involving money; "monetary rewards"; "he received thanks but no pecuniary compensation for his services" [syn: {monetary}] wn
Countervail \Coun"ter*vail`\ (koun"t?r-v?l`), n. Power or value sufficient to obviate any effect; equal weight, strength, or value; equivalent; compensation; requital. [Obs.] Surely, the present pleasure of a sinful act is a poor countervail for the bitterness of the review. --South. web1913
countervail v 1: compensate for or counterbalance; "offset deposits and withdrawals" [syn: {offset}] 2: oppose and mitigate the effects of by contrary actions; "This will counteract the foolish actions of my colleagues" [syn: {counteract}, {neutralize}, {counterbalance}] wn
sandwich ::= lower_slice [ mustard | mayonnaise ] lettuce? tomato? [ bologna | salami | ham ] {2,4} cheese+ top_sliceI sense a Perl module being born...
alt.binaries.sounds.mp3.rap-hiphop
skipping the ones that didn't suit your taste.
dude, where's my car
This document uses CSS kung-fu and a small amount of JavaScript for rendering its contents. Efforts have been made to separate the form from the content so if you are viewing this in a text-based browser it shouldn't be an issue.
On the other hand it may look funny if you are viewing it in a browser with incomplete CSS and/or JavaScript implementations. Internet Explorer 6 comes to mind.
It's not that I don't love you. However, my time is limited and I no longer feel very good about spending it working around any one browser's inconsistencies with little, or no, confidence that they will ever be fixed or otherwise made more inconsistent at some later date.
On the other hand, if something is down-right unreadable please let me know and I will endeavour to fix it.
yes, we have no bananas
This page may not validate. It's not that I don't care, it's just that I'm not aware of it yet. Part of the reason that I rewrote the entire back-end for managing this site is that the old stuff made it too easy for these kinds of mistakes to slip through the cracks.
See also : W3C::LogValidator.pm
it's the software, stupid