NCIDpop is a network Caller ID client for Mac OS X and Windows 2000/XP based on John L. Chmielewski’s NCID package. It is a background application that displays pop-up Caller ID information when information about an incoming call is received over the network.
Copy the NCIDpop application to your hard drive. Double-click to launch it. There will be no visual indication, but you can verify that it is running by looking for “NCIDpop” in Process Viewer. NCIDpop will automatically quit when you log out or shut down your Mac.
To launch NCIDpop automatically when you log in to Mac OS X, add it to the Login Items panel in System Preferences.
To change the NCID server, hold down the command key while double-clicking NCIDpop.
Download ncidpop.exe to your hard drive. Double-click to launch NCIDpop. The NCIDpop status icon will be installed in your task bar’s notification option. You can quit NCIDpop by right-clicking its icon and choosing “Remove Icon” from the context menu.
To launch NCIDpop automatically when you log in to Windows, copy ncidpop.exe
to the Startup folder in your Start menu.
To change the NCID server host, choose “Set NCID Server…” from the context menu. You will need to quit and re-launch NCIDpop for the change to take effect.
Before you can use NCIDpop, you will need to be running a Network Caller ID server. NCIDpop is designed for use with ncidd. When NCIDpop first starts, you will need to enter the hostname or IP address of the server running ncidd. If the server is running on the local computer (currently possible only with Mac OS X), enter “localhost”. If you make a mistake, see the directions above to change the NCIDpop server setting for your operating system.
If you are running ncidd on a non-default port (i.e., not 3333), enter the server name followed by a colon and the port number, e.g., callerid.domain.name:1234.
MTValidate is a Movable Type plugin based on the W3C MarkUp Validation Service. It lets you embed the results of arbitrary of text in HTML or XHTML into the documents generated by your weblog.
Current version: 0.1
MTValidate.pl and the
validator directory to your Movable Type
plugins directory.sgml-lib into the
plugins/validator directory.plugins/validator/config/validator.config to
reflect your setup.This plugin provides the MTValidate container tag.
The contents of this tag should be a complete HTML, XHTML, SGML or XML
document, which will be replaced with the results of the validation.
There are also several attributes you can provide. Set their value to
“1” to enable, “0” to disable:
META
element or XML declaration.DOCTYPE declaration in the document
itself, but you
can override it using this attribute. For example,
HTML 3.2 or XHTML 1.0 Transitional
Here is an example that validates the title and body of an entry, based on the default templates from Movable Type 2.51:
<MTValidate> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <title><$MTBlogName$>: <$MTEntryTitle$></title> </head> <body> <h3 class="title"><$MTEntryTitle$></h3> <$MTEntryBody$> <a name="more"></a> <$MTEntryMore$> </body> </html> </MTValidate>
For information on using Movable Type template tags like
MTValidate in entry previews, see the documentation for
MTSpeling.
The text that appears in the output of the MTValidate
tag is controlled by the templates in the
plugins/validator/templates directory. Edit these to
change the validation output.
MTThreadedComments adds full-fledged threaded commenting features to a Movable Type weblog. Inspired by the comment features of LiveJournal, it adds threading and subject lines to Movable Type comments. This means your readers can carry on more complex discussions, adding their own titles and replying directly to other comments.
Note: MTThreadedComments includes a standard Movable Type plugin to add new tags, but it also requires modification of the main Movable Type source code. Do not install MTThreadedComments unless you are comfortable modifying your Movable Type installation.
MTThreadedComments.pl into your Movable
Type plugins directory.cd
to your Movable Type directory (the one that contains
mt.cgi, lib, extlib,
etc…) and type the following command:
patch -p0 < /path/to/where/you/downloaded/mt-threaded-comments.patchWatch the output of the
patch command for any errors.alter table mt_comment add column comment_subject text alter table mt_comment add column comment_parent_id integer alter table mt_comment add index comment_parent_id
mt-comments.cgi script) will contain the sole form
for posting comments. It will no longer show all comments on an
entry, but instead will show only the entry or comment that is being
responded to.<form to
</form>). Replace it instead with a link to the
comment posting CGI script:
<a href="<$MTCGIPath$><$MTCommentScript$>?entry_id=<$MTEntryID$>">"Post a new comment</a>
<MTComments>—with this:
Note that if you are using anything other than<MTRootComments> <div class="comments-body"> <$MTInclude module="Nested Comments" $> </div> </MTRootComments>
<MTComments> (for example, if you have any
attributes),
you will not be able to use <MTRootComments>.
Instead, continue using your current container tag to list your comments,
but use <MTCommentUnlessParent> to
restrict output to only the root comments in the entry. If you use
SimpleComments,
your comment listing might look like this:
<MTSimpleComments> <MTSimpleCommentIfComment> <MTCommentUnlessParent> <div class="comments-body"> <$MTInclude module="Nested Comments"> </div> </MTCommentUnlessParent> </MTSimpleCommentIfComment> <MTSimpleCommentIfTrackback> <!-- your trackback code here --> </MTSimpleCommentIfTrackback> </MTSimpleComments>
Use your weblog menu to create a new template module, named “Nested Comments”. The contents should be as follows:
This template (included by the Individual Entry Archive for each root comment) formats and displays a comment, and then recursively includes itself for each child comment. This is what allows nested comments to display correctly.<MTIfCommentSubject> <h3 class="title"><$MTCommentSubject$></h3> </MTIfCommentSubject> <$MTCommentBody$> <span class="comments-post"><b>Posted by:</b> <$MTCommentAuthorLink spam_protect="1"$> on <$MTCommentDate$> <MTEntryIfCommentsOpen> | <a href="<$MTCGIPath$><$MTCommentScript$>?entry_id=<$MTEntryID$>;parent_id=<$MTCommentID$>">Reply to this</a> </MTEntryIfCommentsOpen> </span> <MTCommentIfChildren> <div class="comments-nest-box"> <MTCommentChildren> <div class="comments-body"> <$MTInclude module="Nested Comments" $> </div> </MTCommentChildren> </div> </MTCommentIfChildren>
<MTComments> to
</MTComments>) with this:
<MTCommentPreviewUnlessParent> <div class="blogbody"> <h3 class="title"><$MTEntryTitle$></h3> <$MTEntryBody$> <$MTEntryMore$> <div class="posted"><p>Posted by <$MTEntryAuthor$> at <$MTEntryDate$></p></div> </div> </MTCommentPreviewUnlessParent> <MTCommentPreviewIfParent> <MTCommentPreviewParent> <div class="comments-body"> <h3 class="title"><$MTCommentSubject$></h3> <$MTCommentBody$> <span class="comments-post">Posted by <$MTCommentAuthorLink spam_protect="1"$> at <$MTCommentDate$></span> </div> </MTCommentPreviewParent> </MTCommentPreviewIfParent>
This will display the context being replied to. You may wish to
change the contents of the <div class="comments-head"> tag above the
context to reflect its new nature.
Comments: text area label:
<input type="hidden" name="static" value="1" />
<input type="hidden" name="parent_id" value="<$MTCommentPreviewParentID$>" />
<label for="subject">Subject:</label>
<MTCommentPreviewUnlessParent>
<input id="subject" name="subject"
value="Re: <$MTEntryTitle encode_html="1" $>" />
</MTCommentPreviewUnlessParent>
<MTCommentPreviewIfParent>
<MTCommentPreviewParent>
<input id="subject" name="subject"
value="<$MTCommentResponseSubject encode_html="1" $>" />
</MTCommentPreviewParent>
</MTCommentPreviewIfParent>
<br /><br />
Subject entry box to the form, and
populate it with the appropriate values. The parent_id
value is used for threading (to indicate where to nest the new
comment), and setting the static value tells Movable Type
to redirect back to the entry archive page after posting the comment,
since the Comment Listing Template is no
longer appropriate for this.
Comments: text area label:
<input type="hidden" name="parent_id" value="<$MTCommentPreviewParentID$>" />
<label for="subject">Subject:</label>
<input id="subject" name="subject"
value="<$MTCommentPreviewSubject encode_html="1"$>" /><br /><br />
In order for threaded comments to appear nested in your comment listing, you will need to add a nested command style to tell your browser how to display nested comments. To display nested comments as they appear in my weblog, add this to your Stylesheet template:
.comments-nest-box {
padding-left:15px;
border-left:5px solid #AAA;
}
Finally, you will need to alter any templates that link to your comment script or individual entry archive. This includes the Main Index, Date-Based Archive and Category Archive templates.
Find the section in each template that links to the comments. It
will probably be wrapped in a
<MTEntryIfAllowsComments> tag. In the default
templates, it is located between the date posted and the trackback
link. We want to replace the comment link with the following:
<MTEntryIfAllowComments> | <a href="<$MTEntryLink type="Individual"$>#comments">Comments (<$MTEntryCommentCount$>)</a> <MTEntryIfCommentsOpen> | <a href="<$MTCGIPath$><$MTCommentScript$>?entry_id=<$MTEntryID$>">Post a new comment</a> </MTEntryIfCommentsOpen> </MTEntryIfAllowComments>
This provides a link to the comment section of the individual entry archive to read existing comments, and a link to the comments CGI script to post a new one.
The following tags are available for use in displaying
information about the subject of a comment. Except where noted, they
require that a comment be in context, e.g., within a
<MTComments> tag:
<MTIfCommentSubject> and
</MTIfCommentSubject> will be displayed
if this comment has a subject.
<MTUnlessCommentSubject> and
</MTUnlessCommentSubject> will be displayed
if this comment does not have a subject, or if the subject is the
empty string.
Re: ” followed by the subject of
the current comment, unless the comment has no subject or the subject
already starts with Re.
The following tags are available for use in displaying information
about comment threading. Except where noted, they require that
a comment (or comment preview, for tags with Preview in
the name) be in context, e.g., within a
<MTComments> tag.
Comments are threaded in a tree structure; the children of a comment are those comments that are direct replies to it (replies to replies are not children, but children of children). Root comments are those that are attached directly to an entry, and are not replies to another comment.
<MTRootComments> and
</MTRootComments> will be displayed once for each
root comment in the entry. The comments will be displayed in the
order they were posted. This tag can be used in an entry context.
<MTCommentChildren> and
</MTCommentChildren> will be displayed once for each comment that is
a direct child of the current comment, in the order they were posted.
<$MTComment*$> tags to refer
to the parent comment. After you end this context, tags return to
referring to the current comment.
0 if the current
comment is a root comment (has no parent).
None
MTSpeling is a Movable Type plugin by Alexei Kosut to add spell-checking capabilities to a Movable Type weblog. It adds a global filter that allows any template tag output to be spell-checked, and provides tags for fully-customizable suggestion output.
Current version: 0.2
extlib directory.MTSpeling.pl into your Movable
Type plugins directory.MTSpeling.pl if necessary with your
configuration information. You will need to know the full path
location of the ispell binary on your system.check_spellingAdd the check_spelling attribute to any Movable Type
template tag to check its spelling. Pass a value of
“1” to make red any term not in the dictionary (by adding
an HTML font tag). For example, to display the
body of an entry with misspelled words in red, you might use:
<$MTEntryBody check_spelling=”1”$>
Use an attribute value of “2” to wrap misspelled words
with a <span class="spellingerror"> tag, which
allows you to customize the display with a style sheet. To check
spelling, but leave the tag’s output unmodified use a value of
“0”.
Each tag that is spell-checked will add to the results available
using the <MTSpellingResults> tag. Following
</MTSpellingResults>, the results will be cleared
for future uses.
The following tags are available for use in displaying the results of
spelling suggestions (see the Movable Type manual for information on
the use of template tags). These results will include misspelled words from
each prior use of the check_spelling attribute.
check_spelling
attribute. Each of the following tags are used to display a
particular piece of information about a suggestion.
<MTSpellingResultSuggestions>
container, represents a suggestion for the current term.
The following template HTML code will display a comment preview with misspelled words displayed in red, followed by suggestions:
<$MTCommentPreviewBody check_spelling="1"$>
<MTSpellingIfErrors>
<h4>Spelling Suggestions</h4>
<table>
<MTSpellingResults>
<tr><th align="left"><$MTSpellingResultTerm$></th>
<td><MTSpellingResultIfSuggestions>
<MTSpellingResultSuggestions>
<$MTSpellingSuggestion$>
</MTSpellingResultSuggestions>
</MTSpellingResultIfSuggestions>
<MTSpellingResultUnlessSuggestions>
<em>No suggestions</em>
</MTSpellingResultUnlessSuggestions></td>
</tr>
</MTSpellingResults>
</table>
</MTSpellingIfErrors>
You might use code similar to this in the comment preview template to provide spell-checking for comments.
You can add spell-checking to comment previews by modifying the comment preview template, as shown above. However, since Movable Type does not provide access to the templates use to generate the content management system, adding spell-checking to the entry preview requires modifying the Movable Type software, as follows:
CMS.pm in the lib/MT/App
subdirectory of your Movable Type installation.preview_entry subroutine, and the location
where the $preview_code variable is set. This will be line
2034 in Movable Type 2.51.$preview_code initialization (the lines
before HTML) with your
new HTML, including any template tags to display spell-checking
information.<$MTInclude$> tag work, you will first need to add
the following line of Perl code above the $preview_code
initialization:
$ctx->stash('blog_id', $blog_id);
Don’t forget to make a backup copy of your Movable Type software before making changes, as modifications could make your weblog inaccessible!
MTSpeling provides support for a personal dictionary of words that
it will treat as spelled correctly, stored as a cookie on the user’s
web browser. The only support in the plugin is to be able to read and
parse the spelling-dict cookie as a colon-seperated list
of words. If you want to make use of this, you’ll have to write your
own code to create and add to this cookie. In my weblog, I use
JavaScript to provide an ‛add to dict“ link in the list of
spelling suggestions that adds a word to this cookie. You could also
write a server-side script to do something similar.
There is no current support in the plugin for dictionaries stored anywhere other than as a cookie in the browser.
ResolveURLs is a Movable
Type plugin by Alexei Kosut to resolve
relative URLs in weblog entries. It adds a new global filter
resolve_urls that can be used in any MT template tag.
Enabling this causes relative URLs to be resolved against your
weblog site URL, and output as absolute.
This is useful, as relative URLs are convenient to type, but unsafe, since weblog entries can be seen from a number of different pages (e.g., from the index or from an archive page), each of which might resolve a relative URL differently. RSS feeds make the problem of relative URLs even worse, since your links may end up on another site where relative URLs will not point to your pages at all.
Current version: 1.0.2
To install, copy ResolveURLs.pl into your Movable
Type plugins directory.
Add resolve_urls="1" to any template tag where you
want relative URLs expanded. For example, to display the body of an
entry with URLs expanded, you might use:
<$MTEntryBody resolve_urls=”1”$>
The filter will search for any HTML tags with href or
src attributes, and make sure the corresponding URLs are
absolute. Relative URLs are resolved against the weblog site URL, as
configured in Movable Type.
The resolve_urls filter can be used in any template
tag where a weblog is in context. I use it in my weblog for all
<$MTEntryBody$> and <$MTEntryMore$>
tags, to make sure no relative URLs sneak out.
#foo),
since these usually refer to anchors inside the entry itself, and are
“safe” for encapsulation.I recently started reading my email using the Mail application that comes with Mac OS X, after years of using Mutt. I discovered right away that Mail was missing a number of features I was used to in Mutt that made it slow and cumbersome to read my mail. I wrote these AppleScripts to add some of the missing functionality.
Displays a dialog where you can enter the name of a mailbox to save the currently-selected message(s) to, similar to the S key in Mutt or Pine. Defaults to suggesting a folder based on the email address, so in many cases you can save mail to the right place with only a few keystrokes.
Edit the applySaveRules function in the script to
define your own rules about what default mailbox to use based on the
sender and receipients.
Displays a dialog where you can type in the name of a mailbox, and it will be displayed. Modeled on the C key in Mutt.
Opens the currently-selected message as its own mailbox, showing
each attachment of type message/rfc822 as its own message. Some
mailing lists (e.g., those at run by Apple) can be configured to send
digests in this format.
These scripts let you easily set the sender when composing a new or existing
message. Displays a dialog where you can change the text that will be
used in the From header of the message when it is sent,
allowing you to send email with a sender of any name or address.
Note that Mail will not display the sender address during composition unless you already have configured multiple accounts or multiple addresses (use a comma in the “Email Address” account preference). I recommend enabling this option when using these scripts.
Download and expand the scripts. You can run them as you would any other AppleScript, including:
The Open Digest script uses an auxiliary Perl script
parsedigest, which uses the MIME::Parser
Perl module to do the actual parsing of MIME digests. This script
needs to be installed where the AppleScript can find it.
After mounting the disk image, you will find two files,
Open Digest.scpt and parsedigest. The
former is the AppleScript; run it like any of the others. The latter
needs to be moved to a folder named bin just inside
your home directory. You will need to create this folder if it does
not already exist.