<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Noel Schutt &#187; computers</title>
	<atom:link href="http://schutt.org/blog/tag/computers/feed/" rel="self" type="application/rss+xml" />
	<link>http://schutt.org/blog</link>
	<description></description>
	<lastBuildDate>Sun, 05 Feb 2012 12:14:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>BlockTarget and more on not opening new windows</title>
		<link>http://schutt.org/blog/2011/02/blocktarget/</link>
		<comments>http://schutt.org/blog/2011/02/blocktarget/#comments</comments>
		<pubDate>Sat, 05 Feb 2011 15:27:03 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[computers]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[AJAX]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[new window]]></category>
		<category><![CDATA[Safari]]></category>
		<category><![CDATA[target]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=1138</guid>
		<description><![CDATA[One of annoyances of using the web is that many webmasters (or at least their managers) think that forcing a browser to open a new window is a good idea. As I&#8217;ve said a number of times, creating a website that automatically opens a new window is almost always a Bad Idea. To eliminate this [...]]]></description>
			<content:encoded><![CDATA[<p>One of annoyances of using the web is that many webmasters (or at least their managers) think that forcing a browser to open a new window is a good idea. As I&#8217;ve said a number of times, creating a website that automatically opens a new window is almost always a Bad Idea. To eliminate this temptation, I have <a href="/blog/2011/01/not-opening-windows/">modified the text editor</a> used on some of my sites so that users cannot create new windows using the HTML <code>target</code> attribute. This still doesn&#8217;t solve the problem of new windows opened using JavaScript, or of new windows being opened by sites I visit. So I decided to look for a solution to automatically remove the <code>target</code> attribute from links on sites I visit.</p>
<p>Since I use the Safari and <a href="http://www.chromium.org/Home">Chromium</a> web browsers on OS X, my first impulse was to write a <a href="http://glimmerblocker.org/">GlimmerBlocker</a> script to remove the <code>target</code> from links. This would fix the problem on all sites I visit with any browser. I had already written a GlimmerBlocker filter to remove <code>target="_blank"</code> from some websites, so I just needed modify it into a cleaner general version. Since <a href="http://legoboy.com/">my brother</a> does much more JavaScript programming than I do, I asked him if he knew a more efficient way to do this. He mentioned one, and also suggested writing a Safari Extension instead of a GlimmerBlocker script.</p>
<p>Before starting a new Extension, I searched for an existing one. It wasn&#8217;t on the official Extension list, but someone had already written one:</p>
<blockquote><p><a href="http://dergraf.net/blocktarget/">BlockTarget</a> is an extension for Safari 5. It removes the ‘target’ attribute from links to prevent a new window being opened.</p></blockquote>
<p>After skimming the source (<a href="http://cheat.schuttdesign.net/hint/open-safari-extension/">how open a Safari Extension</a>) for this Extension, I decided to give it a try. I&#8217;ve been using BlockTarget for two weeks, and it seems to work well. If you use Safari, this Extension will make the internet a more pleasant place.</p>
<p>BlockTarget is a good solution to part of the problem of new windows, but it can&#8217;t fix all instances. It is still possible to open a new window using JavaScript. Developing a universal solution for the alternate methods of opening new windows is a problem for another time. There is also a disturbing trend to generate websites completely through the use of JavaScript. Even if these sites use the <code>target</code> attribute to open new windows, they do it after BlockTarget has run, so it misses these <code>target</code>s. I eventually need to find an efficient way to write a script to watch a page and remove all window opening code, but I won&#8217;t have time to work on that in the near future. So please, write a clean solution!</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2011/02/blocktarget/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Customizing Mac OS X PDF Services</title>
		<link>http://schutt.org/blog/2009/08/osx-pdf-services/</link>
		<comments>http://schutt.org/blog/2009/08/osx-pdf-services/#comments</comments>
		<pubDate>Tue, 18 Aug 2009 22:46:06 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[technology]]></category>
		<category><![CDATA[computers]]></category>
		<category><![CDATA[Mac]]></category>
		<category><![CDATA[OS X]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=360</guid>
		<description><![CDATA[One useful feature of OS X is the built in PDF handling. It is always easy to export a file as a PDF, and to do some basic editing of PDF files. A post on Mac OS X Hints today got me looking at some customizations. The hint is that creating an alias in the [...]]]></description>
			<content:encoded><![CDATA[<p>One useful feature of OS X is the built in PDF handling. It is always easy to export a file as a PDF, and to do some basic editing of PDF files. A <a href="http://www.macosxhints.com/article.php?story=20090817002247614" title="Add a Save to PDF directory to your Print options">post</a> on Mac OS X Hints today got me looking at some customizations. The hint is that creating an alias in the proper directory adds an item to the PDF menu. This can be done through Finder, or through the command line:</p>
<p><code>cd ~/Libary/PDF\ Services<br />
ln -s ~/path/ "descriptive_alias"</code></p>
<p>You may have to create the directory <code>~/Libary/PDF Services</code>. Some people recommend using the directory <code>/Libary/PDF Services</code>, but this is bad style unless you <em>really</em> want the change to be universal. Even if you are the only user on the computer, it is safer to use the <code>Library</code> folder under your user account.</p>
<p>When looking in the <code>/Libary/PDF Services</code> directory, I noticed that the contents are just Automator workflows. This means it is easy for non-programmers to customize the behavior. One option that I somehow hadn&#8217;t noticed before today is <code>Save PDF to Web Receipts Folder.pdfworkflow</code>. With online billing this is incredibly useful. I typically use the &#8220;Save PDF as&#8221; option, saving the PDF in this year&#8217;s receipts directory, with the date as a prefix. This makes receipts for monthly bills easy to find. I looked at &#8220;Save PDF to Web Receipts Folder&#8221; to see how easy it would be to alter to my preferred style. Instead of being an Automator workflow, this is actually a Python script and a few property lists. Great! Python is my favorite language. I copied the files to <code>~/Libary/PDF Services</code> and edited them. The Python script is in a file named <code>tool</code>. This script is well written, making it easy to modify. Here are the basic changes:</p>
<ul>
<li>Because I want to use timestamps, I added <code>import time</code> after the other import statements.</li>
<li>I changed the <code>destDirectory</code> to my preferred directory. The script already creates the destination directory if it doesn&#8217;t exist, so altering the directory by date is easy, I added <code>destDirectory = os.path.join(destDirectory, time.strftime("%Y"))</code> to automatically append the subdirectory for the year.</li>
<li>The file uses the title of the webpage as the filename. To add the date as a prefix, add the line <code>title = "%s-%s" % (time.strftime( "%Y%m%d"), title)</code> to the build path section. You can easily customize the date format.</li>
<li>I  prefer lowercase filenames, so I added <code>filename = filename.lower()</code> to the <code>safeFilename</code> function.</li>
<li>If a file with this name already exists, the script appends a number to the name. I prefer different character than the default, so I changed it.</li>
</ul>
<p>The final step was to I update the property list files so that the PDF menu shows the name I gave the command, instead of the original name from Apple.</p>
<p>I now have an even quicker way to save my receipts. Because the program is automatically generating the filenames using my preferences, I don&#8217;t have to change the name every time, and can avoid some typos and incorrect dates.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2009/08/osx-pdf-services/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>MacBook screens</title>
		<link>http://schutt.org/blog/2009/07/macbook-screens/</link>
		<comments>http://schutt.org/blog/2009/07/macbook-screens/#comments</comments>
		<pubDate>Thu, 16 Jul 2009 01:37:09 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[technology]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[computers]]></category>
		<category><![CDATA[glare]]></category>
		<category><![CDATA[MacBook]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=281</guid>
		<description><![CDATA[There are rumors that Apple may reintroduce matte screens as an option on their notebooks. Apple can&#8217;t return to glare free displays soon enough! I&#8217;m looking forward to buying an aluminum computer once they fix this design flaw. The latest 13 inch MacBook Pro would be almost perfect with an anti-glare screen. [Update 2009-08-11] Anti-glare [...]]]></description>
			<content:encoded><![CDATA[<p>There are <a href="http://arstechnica.com/apple/2009/07/dont-call-it-a-comeback-matte-apple-displays-may-reappear.ars">rumors</a> that Apple may <a href="http://www.appleinsider.com/articles/09/07/15/apple_may_extend_antiglare_display_option_to_more_macs.html"> reintroduce matte screens</a> as an option on their notebooks. Apple can&#8217;t return to glare free displays soon enough! I&#8217;m looking forward to buying an aluminum computer once they fix this design flaw. The latest 13 inch MacBook Pro would be almost perfect with an anti-glare screen.</p>
<p><span class="update">[Update 2009-08-11]</span> Anti-glare is <a href="http://arstechnica.com/apple/news/2009/08/matte-display-option-makes-a-quiet-return-to-15-macbook-pro.ars" title="Ars Technica">back</a> on the 15 inch MacBook Pro! Now for the 13 inch&#8230;</p>
<p><span class="update">[Clarification 2009-08-24]</span> By anti-glare, I don&#8217;t mean a matte display. Keep the glass covering, but use anti-reflection coating. The glass is nice, but reflections make the displays unusable.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2009/07/macbook-screens/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Crash</title>
		<link>http://schutt.org/blog/2008/12/crash/</link>
		<comments>http://schutt.org/blog/2008/12/crash/#comments</comments>
		<pubDate>Wed, 10 Dec 2008 02:50:01 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[technology]]></category>
		<category><![CDATA[computers]]></category>
		<category><![CDATA[hard drive crash]]></category>
		<category><![CDATA[MacBook]]></category>
		<category><![CDATA[script]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=93</guid>
		<description><![CDATA[The hard drive on my MacBook crashed. It took two weeks to get it back the way I like it. It took a week to get a new drive and do a temporary restore. I then had to use it as-is for a few days. I then went back and did a fresh install and [...]]]></description>
			<content:encoded><![CDATA[<p>The hard drive on my MacBook crashed. It took two weeks to get it back the way I like it. It took a week to get a new drive and do a temporary restore. I then had to use it as-is for a few days. I then went back and did a fresh install and spent a few days installing programs and making custom settings. It took so long because I forgot a couple of my usual backups. Now I am obsessed with creating an automatic archiving system. I have a good start. I&#8217;ll post details when I know it is bombproof. I need to convince myself to study for another week before finishing my scripts.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2008/12/crash/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Controlled Reading And Playing</title>
		<link>http://schutt.org/blog/2008/11/crap/</link>
		<comments>http://schutt.org/blog/2008/11/crap/#comments</comments>
		<pubDate>Sat, 29 Nov 2008 16:58:54 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[technology]]></category>
		<category><![CDATA[computers]]></category>
		<category><![CDATA[copyright]]></category>
		<category><![CDATA[CRAP]]></category>
		<category><![CDATA[DRM]]></category>
		<category><![CDATA[ethics]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=84</guid>
		<description><![CDATA[After a couple frustrating weeks with computers, we have been talking about copy-protection. With the switch to DTV, Blu-ray, and DisplayPort, it is getting harder to avoid buying copy-controlled products. Avoiding Blu-ray is easy, but avoiding encrypted DisplayPort will be harder. Luke and Adam wanted to use the acronym FARCE, but we couldn&#8217;t settle on [...]]]></description>
			<content:encoded><![CDATA[<p>After a couple frustrating weeks with computers, we have been talking about copy-protection. With the switch to DTV, Blu-ray, and DisplayPort, it is getting harder to avoid buying copy-controlled products. Avoiding Blu-ray is easy, but avoiding encrypted DisplayPort will be harder. <a href="http://legoboy.com/" title="Legoboy">Luke</a> and Adam wanted to use the acronym FARCE, but we couldn&#8217;t settle on a definition. The word &lsquo;crap&rsquo; came to mind. This gave a convenient definition: Controlled Reading and Playing. I thought may have heard this term before. I found a few references to the acronym CRAP for DRM on <a href="http://blogs.zdnet.com/BTL/?p=2416" title="ZDNet">ZDNet</a>, but using a different definition: Content Restriction, Annulment, and Protection. (A good video explanation: <a href="http://news.zdnet.com/2422-13569_22-156220.html" title="A load of CRAP">A load of C.R.A.P.</a> by ZDNet Executive Editor David Berlind.) Richard Stallman saw the article and <a href="http://blogs.zdnet.com/BTL/?p=2582" title="ZDNet">suggested</a> another definition: Cancellation, Restriction and Punishment. All of these definitions work. Please start using the acronym CRAP instead of the euphemism DRM.</p>
<p>P.S. For those less informed on the ethics of technology: DRM is an acronym for Digital Rights Management. It is used as a euphemism for copy-control. Some companies try to control the ethical&#8211;and legal&#8211;fair use of music, video, and text. A common method is encryption designed to only allow files to be accessed on approved devices. Good examples are Blu-ray disks and some PDF files. These encryption systems are superfluous and unethical. This is why the euphemism DRM commonly makes lists of technology terms to avoid: <a href="http://www.gnu.org/philosophy/words-to-avoid.html#DigitalRightsManagement" title="gnu.org: Philosophy">Some Confusing or Loaded Words and Phrases that are Worth Avoiding</a>, and <a href="http://pogue.blogs.nytimes.com/2008/10/16/tech-terms-to-avoid/" title="NY Times: David Pogue:Tech Terms to Avoid">Tech Terms to Avoid</a>. We settled on the term CRAP: Controlled Reading and Playing.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2008/11/crap/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

