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.
I know what the meaning of "is" is.
http_proxy
-ing hooks to Net::Blogger now too...
Heaven help me, I am saying that if I had been given a chance years ago to spare the lives of so many of my dearest friends, given the chance to end my exile and alleviate the grief of millions of my fellow countrymen, I would have rejected it if the price we would have had to pay was clusters of bombs killing the innocent, if the price was years of foreign occupation, if the price was the loss of control over our own destiny. Heaven help me, I am saying that I care more about the future of this sad world than about the future of your unprotected children.
It's all Kellan's fault. see also : docsBecause, you know, it may be important to your Perl module that it's raining outside...
Categories
and
Zeldman
functions are gone, added support for REST interface (including 2-url
form) and support for RPC categories. Still considering whether or not
to submit this to the CPAN. see also :
docs
Date: Wed, 11 Sep 2002 09:11:25 -0400 (EDT)
From: Aaron Straup Cope
To: Benjamin Trott
Subject: Re: MT - two unrelated thingies
> > I mention all of this because it seems like it would be a nifty bit
of
> > featuritis for Movable Type. Actually, I mention it because it would
be
> > nice to have some kind of universal glossary system and MT is rapidly
> > approaching universal status (congrats!)
>
> I agree that a glossary system would be pretty cool. Though, it's quite
> doable currently just using the MT-Macro plugin. Have you taken a look
> at that?
Ah, I see. No I hadn't. That's cool - I gather I can do something like :
<MTApplyGlossary>
<$MTEntryBody$>
</MTApplyGlossary>
MT::Template::Context->add_container_tag(MTApplyGlossary => sub {
my $ctx = shift;
my $args = shift;
my $path = $args->{path'};
if (! $path) {
my $cfg = ... " # Remember how to get MT config manager here
$path = $cfg->{GlossaryPath} ||
return $ctx->error($ctx->errstr);
}
#
my $builder = $ctx->stash('builder');
my $tokens = $ctx->stash('tokens');
my $output = "";
my $writer = XML::SAX::Writer->new(Output=>$output);
my $glossary = XML::Filter::Glossary->new(Handler=>$writer);
my $parser = XML::SAX::ParserFactory->parser(Handler=>$glossary);
# Would also need to $glossary->no_do_startend_document_methods();
$glossary->set_glossary($path);
eval { $parser->parse_string($builder->build($ctx, $tokens)); };
if ($@) {
return $ctx->error($ctx->errstr.": $@");
}
return $output;
}
Which will almost certainly break because it is very possible that the
data passed to the plugin will not be well-formed. I suppose I could just
export the code for parsing double-quoted keywords as a package function.
I'm about to add
support
for <my_ns:glossary id = "some keyword with
spaces" />
per a request which I'm not keen to parse with regex(p)s since
you can also do <my_ns:keyword />.
I suppose the whole thing could be hacked together using HTML::Parser to
do the parsing since it is very forgiving. Well, it's something to work
with anyway.
Question : When a plugin is called, has the FH associated with the
document already been opened or are you just building a string? If there
is a FH, is there any way that it could be passed to the plugin?
I suppose not since that would make managing nested tags/plugins
impossible. Alas.
In the unsolicited advice department, I would only mention the docs for
plugins are less than inviting. I've noticed that
other people
who've
written plugins have posted code which is helpful, since you can sort of
infer what 'foo' does and how to get 'bar' from them.
But, if plugins are really more exciting that just returning the value of
system calls it isn't readily apparent how.
107 ->perldoc MT::Template::Context
No documentation found for "MT::Template::Context".
Malfeasance \Mal*fea"sance\, n. [F. malfaisance, fr. malfaisant injurious, doing ill; mal ill, evil + faisant doing, p. pr. of faire to do. See {Malice}, {Feasible}, and cf. {Maleficence}.] (Law) The doing of an act which a person ought not to do; evil conduct; an illegal deed. [Written also {malefeasance}.] web1913
malfeasance n : a wrongful act that the actor had no right to do; improper professional conduct; "he charged them with electoral malpractices" [syn: {malpractice}] wn
Quondam \Quon"dam\, n. A person dismissed or ejected from a position. [R.] ``Make them quondams; . . . cast them out of their office.'' --Latimer. web1913
quondam adj : belonging to some prior time; "erstwhile friend"; "our former glory"; "the once capital of the state"; "her quondam lover" [syn: {erstwhile(a)}, {former(a)}, {once(a)}, {onetime(a)}, {quondam(a)}, {sometime(a)}] wn
my $outline = "/path/to/io.otlml";
my $output = IO::File->new("+<$outline");
my $writer = XML::SAX::Writer->new(Output=>$output);
my $filter = XML::Filter::OTLML::IO->new(Handler=>$writer);
my $parser = XML::SAX::ParserFactory->parser(Handler=>$filter);
$parser->parse_uri($outline);
An exclamation of surprise. Originates from Oor Wullie as chronicled in the Sunday Post (Uk)
ex. Jings, would you look at the size of that.
Postprandial \Post*pran"di*al\, a. [Pref. post- + prandial.] Happening, or done, after dinner; after-dinner; as, postprandial speeches. web1913
postprandial adj : following a meal (especially dinner); "his postprandial cigar"; "took a postprandial walk" [ant: {preprandial}] wn
Joe User's Radio Weblog
listings on the
weblogs.com
sidebar
is testimony enough of that. But it doesn't explain why I've spent the
last hour and a half rebooting the computer, re-installing the program
three
times and downloading it twice and finally reacquainting myself with
the Frontier debugger. And still,
nothing
. This must be some kind of a joke for having been such a sourpuss,
today...
