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 was then perplexed at [MovableType's] lack of any kind of automated setup script to assist folks who might not be too comfortable with editing even a few lines of a configuration file.
I want to be able to do the following:
span.footnote { display:inline; }
span.footnote:before {
content: "<footnote/>";
margin-right:5px;
margin-left:5px;
font-family:monospace;
color:brown;
}
span.footnote:hover:before {
content: "<footnote>";
}
span.footnote > span.content {
display:none;
}
span.footnote:hover > span.content {
display: inline;
font-family:monospace;
}
span.content:first-letter {
color:#fff;
}
span.footnote > span.content:after {
content: "</footnote>";
margin-right:5px;
margin-left:5px;
font-family:monospace;
color:brown;
}
<div>hello
<span class = "footnote">
<span class = "content">
* This is the network of our disconnect.
</span>
</span>
world.</div>
Which should render like this in a CSS-enabled browser :
And like this in a text-browser:
But it doesn't. Specifically, the leading asterix (which is
included to denote a text as a footnote or afternote in user-agents
that don't do formatting) is supposed to
hidden
by assigning it the same colour as the background.
span.content:first-letter {
color:#fff;
}
If you're wondering why I didn't just define the
:first-letter
's display property as
hidden
it's not for lack of trying. Based on my experiments it simply
doesn't work. Another mystery.
But it only works when the
span.content
element is displayed as a block. I want to display it inline for
foofy design considerations, which since we're talking about CSS is
as a good a reason as any.
Actually, I'd also like a
last-letter
or
nth-letter
selector so that I could wrap my footnotes in parentheses for
text-browsers and then hide them when the CSS kung-fu enters the
building.
So a close examination of Canadas past can disclose both a strong foundation in the ethic of tolerance and inclusion, as well as the dark side of group belonging in the form of intolerant treatment. I want to explore both of these aspects of our heritage, in the hopes of ultimately demonstrating that, as Canada has matured and grown as a nation, we have embraced and cultivated the first of these traditions in order to do a better job of confronting the second we have learned to value and institutionalize the ethic of respect for difference as a means of combating exclusionary thinking.
how many virtual operating systems can you run on top of one anothermeme has gotten a bit stale of late.
You could always dump the data structure out as YAML in Python and then read it back in with YAML in Perl.
So that [he] can't flush it down the toilet. Gary Shteyngart, please get a fucking clue. The guy never even bothered to learn how to speak French...But Richler certainly had a compassion and understanding for French Canadians; many of the most honest, exemplary characters in his fiction are Francophones. I remember the cabdriver in Barney's Version who complains to Barney about the excitement of the Canadiens playing for the Stanley Cup. " 'Mon blood pressure est sky-high,' said the driver. 'C'est le stress.' "
[O]utliners force us into a way of thinking that is actively inimical to creativity. They corral us down a linear pathway. They make us focus on what we just thought, rather than freeing us for what to think next. They are entirely left-brain tools and, while they may offer an illusion of rationality and control, what they largely do is prevent us thinking.
Extirpate \Ex"tir*pate\ (?; 277), v. t. [imp. & p. p. {Extirpated}; p. pr. & vb. n. {Extirpating}.] [L. extirpatus, exstirpatus, p. p. of extirpare, exstirpare; ex out + strips stock, stem, root.] To pluck up by the stem or root; to root out; to eradicate, literally or figuratively; to destroy wholly; as, to extirpate weeds; to extirpate a tumor; to extirpate a sect; to extirpate error or heresy. Syn: To eradicate; root out; destroy; exterminate; annihilate; extinguish. web1913
extirpate v 1: destroy completely, as if down to the roots; "the vestiges of political democracy were soon uprooted" [syn: {uproot}, {eradicate}, {exterminate}] 2: pull up by or as if by the roots; "uproot the vine that has spread all over the garden" [syn: {uproot}, {deracinate}, {root out}] wn
"to relax, to chill out"
ex. i'm going to veg out for the afternoon...see also : veg dict-ified
to go to the bathroom.
ex. I'll be right back. I have some paperwork to take care of.see also : paperwork dict-ified
When asked to elaborate on that last bit :I'm not sure that the API, per se, will do much. It's got a pretty high hack-value and gee-whiz factor...
- http://aaronland.net/weblog/archive/4210
- http://www.decafbad.com/news_archives/000087.shtml#000087
- http://interconnected.org/googlematic/
...but I doubt that it will make the Earth move.
Notwithstanding the fact that the search widget combined with the cache widget will return non-HTML documents, you sort of have to ask yourself : why wouldn't I search for web documents in a web browser?
On the other hand, it will probably give a big push towards making people more familiar and comfortable building sites/tools using distributed widgets.
See also : http://use.perl.org/~gnat/journal/4163
It's sort of the same idea as the one that the "internet operating system" gang like to trumpet. For example, pulling in remote content or manipulating your own content via a remote function as a page (let's just imagine we're talking about the web) is being published [1].
You can sort of see this happening with the many publish/subscribe widgets that are popping up [2]. That is, there is a growing interconnectedness among pages, sites, applications.
I'm not sure I buy it, though. It's plenty cool but there are lots of problems that need to be worked out. All the same problems that plague popular websites (bandwidth, scaling, etc.) are going to plague popular web services and not everyone has a thousand servers like Google does[3].
Not to mention issues of reliability and the nagging sense that I think a lot of people have that it's just the carrot (cool-ness!) before the stick (micro-payments!)
Mostly I was just trying to say that being able to "plug" Google-ness in to your website will, if nothing else, provide an example of "distributed computing" that is not as abstract as those that have come before it.
- RSS feeds are a good example
- http://radio.weblogs.com/0100059/stories/2002/02/25/whatIsPublishAndSubscribe.html
- http://fyuze.com/api
Nescience \Nes"cience\, n. [L. nescientia, fr. nesciens, p. pr. of nescire not to know; ne not + scire to know.] Want of knowledge; ignorance; agnosticism. God fetched it about for me, in that absence and nescience of mine. --Bp. Hall. web1913
nescience n : ignorance (especially of orthodox beliefs) [syn: {ignorantness}, {unknowing}, {unknowingness}] wn
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
