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.
What in the fuck is Ben smoking?This should elevate the standard of weblogs in general, as it does away with any correlation between technical skill and artistic merit. We will no longer be reliant on geeks for top quality weblog reading. It takes the seething masses and pulls them up to the same technical level as the best Movable Type tweakers and hackers.
Renascent \Re*nas"cent\ (-sent), a. [L. renascens, p. pr. of renasci to be born again; pref. re- re- + nasci to be born. See {Nascent}.] 1. Springing or rising again into being; being born again, or reproduced. 2. See {Renaissant}. web1913
renascent adj : surging or sweeping back again [syn: {resurgent}] wn
Deleterious \Del`e*te"ri*ous\, a. [LL. deleterius noxious, Gr. dhlhth`rios, fr. dhlei^sqai to hurt, damage; prob. akin to L. delere to destroy.] Hurtful; noxious; destructive; pernicious; as, a deleterious plant or quality; a deleterious example. -- {Del`e*te"ri*ous*ly}, adv. -- {Del`e*te"ri*ous*ness}, n. web1913
deleterious adj : harmful to living things; "deleterious chemical additives" [syn: {hurtful}, {injurious}] wn
Garrulous \Gar"ru*lous\, a. [L. garrulus, fr. garrire to chatter, talk; cf. Gr. ? voice, ? to speak, sing. Cf. {Call}.] 1. Talking much, especially about commonplace or trivial things; talkative; loquacious. The most garrulous people on earth. --De Quincey. 2. (Zo["o]l.) Having a loud, harsh note; noisy; -- said of birds; as, the garrulous roller. Syn: {Garrulous}, {Talkative}, {Loquacious}. Usage: A garrulous person indulges in long, prosy talk, with frequent repetitions and lengthened details; talkative implies simply a great desire to talk; and loquacious a great flow of words at command. A child is talkative; a lively woman is loquacious; an old man in his dotage is garrulous. -- {Gar"ru*lous*ly}, adv. -- {Gar"ru*lous*ness}, n. web1913
garrulous adj : full of trivial conversation; "kept from her housework by gabby neighbors" [syn: {chatty}, {gabby}, {loquacious}, {talkative}, {talky}] wn
Apposite \Ap"po*site\, a. [L. appositus, p. p. of apponere to set or put to; ad + ponere to put, place.] Very applicable; well adapted; suitable or fit; relevant; pat; -- followed by to; as, this argument is very apposite to the case. -- {Ap"po*site*ly}, adv. -- {Ap"po*site*ness}, n. web1913
apposite adj : being of striking appropriateness and pertinence; "the successful copywriter is a master of apposite and evocative verbal images"; "an apt reply" [syn: {appropriate}, {apt}, {pertinent}] wn
Forlorn \For*lorn"\, n. 1. A lost, forsaken, or solitary person. Forced to live in Scotland a forlorn. --Shak. 2. A forlorn hope; a vanguard. [Obs.] Our forlorn of horse marched within a mile of the enemy. --Oliver Cromvell. web1913
forlorn adj 1: pitiable in circumstances especially through abandonment; "desolate and despairing"; "left forlorn" [syn: {desolate}, {godforsaken}, {lorn}] 2: marked by or showing hopelessness; "the last forlorn attempt"; "a forlorn cause" wn
Sunder \Sun"der\, v. t. To expose to the sun and wind. [Prov. Eng.] --Halliwell. web1913
sunder v : break apart or in two, using violence wn
<xsl:select value-of = "document($uri)/more/xpath/to/*[@id=$id]" > <!-- do stuff here --> </xsl:select>...so that all you'd need to do an otlml-blog are two stylesheets. The first slurps all the nodes -- note that
$uri
could just as easily live on a local fileshare as on the
network -- and builds a new document. The second transforms
it into whatever format is being requested. The problem
with this scenario is that it's not very smart about
caching changes and will trot out across the network to
slurp each embedded document, regardless of changes, for
every single request. Thinking out loud now: you could
enable the necessary feeping creaturitis on the user end to
send a
Hey, I've changed
notice, akin to the UserLand <cloud> thingy.
Those changes could be written to the server and read by
the XSLT processor which could be taught to return a cache
file... but that still has problems since you're can't
cache the individual nodes themselves from inside the first
stylesheet. Anyway, you get the idea. Meanwhile, Dries
writes:
See http://www.drop.org/node.php?id=752 . We had this thread/discussion (see link above) about template systems, and the use of XSL/XSTL when generating dynamic pages. Most of the others tend to favor Smarty, FastTemplate and similar template systems, yet I think XSL/XSTL (or after reading your blog maybe OTLML) might be the way to go.The issue, ultimately, revolves around the place where your security, performance and logic requirements meet. I have never been a fan of embedding code in markup. Partly for maintainability, partly for security. But XSLT, like HTML and RSS before it, is a funny beast being used "out of context", as some people in the thread have pointed out. While the built-in logic can be maddenly insufficient, XSLT also has enough power that a malicious or stupid programming error can bring your machine to its knees. So, if you're working in an environment where there are designers and developers and never the two shall meet (they should, but that's another story) you shouldn't fob off the writing of the stylesheets on the designers any more than you would the writing of embedded/evaluated Perl code. For a long time, I was a purist about templates, arguing that the only artificial construct they should contain are substitution variables. Which meant a lot of fucking templates, especially if you were doing tables. Lately, I've been coming around a bit. The ability to pass a data structure other than a scalar and have the tools to read them (minimal conditionals and looping) in place is nice. I'm still not convinced, though. Speaking of emebedded Perl code, I wonder how difficult it would be to write a Template::Toolkit module to build a "smart" OTLML guest/group blog rendering tool...
doc -> html -> pod -> docbook -> html -> doc...<wonk size = "tiny" type = "feeble" />