
<?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>TRIGGERS &#38; SPARKS &#187; tutorial</title>
	<atom:link href="http://triggersandsparks.com/tag/tutorial/feed/" rel="self" type="application/rss+xml" />
	<link>http://triggersandsparks.com</link>
	<description>Beautiful graphic design for web &#38; print</description>
	<lastBuildDate>Sun, 15 Jan 2012 23:31:49 +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>AJAX Frameworks: Head. Desk. Head. Desk.</title>
		<link>http://triggersandsparks.com/blog/ajax-frameworks-head-desk-head-desk/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ajax-frameworks-head-desk-head-desk</link>
		<comments>http://triggersandsparks.com/blog/ajax-frameworks-head-desk-head-desk/#comments</comments>
		<pubDate>Tue, 02 Sep 2008 17:06:57 +0000</pubDate>
		<dc:creator>sarah semark</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[pretty]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[resources]]></category>
		<category><![CDATA[tutorial]]></category>
		<category><![CDATA[websites]]></category>

		<guid isPermaLink="false">http://kiss.triggersandsparks.com/?p=163</guid>
		<description><![CDATA[I usually use Scriptalicious for my AJAX needs, but I’m working on a set of AJAX-ified forms on a website that’s already using jQuery, so I figure hey, it can’t be that hard to change over! Twenty minutes later, cue the loud cursing and growling. I mean, the whole thing seems far more powerful, but [...]]]></description>
			<content:encoded><![CDATA[<p>I usually use <a href="http://script.aculo.us/">Scriptalicious</a> for my AJAX needs, but I’m working on a set of AJAX-ified forms on a website that’s already using <a href="http://jquery.com/">jQuery</a>, so I figure hey, it can’t be that hard to change over! Twenty minutes later, cue the loud cursing and growling. I mean, the whole thing seems <strong>far</strong> more powerful, but every time I’ve wanted to start implementing it, I’ve been turned off by how complex it seems to do simple things. (Like slide down a div window, which I hope to have accomplished before I turn 30. On a side note, I’ve been feeling old because I turned 25 today, until my little sister sent me a message saying that I’m “plenty young, for a president!” Which I suppose is technically true, so I don’t feel quite so washed up anymore.)</p>
<p>Anyway, back to my jQuery-induced headache: <a href="http://www.webdesignerwall.com/tutorials/jquery-tutorials-for-designers/">this very helpful thing to the rescue</a>! If I can stop being distracted by the gorgeous site design, I might be able to figure this stuff out, after all, without having to spend all day teaching my brain new methods of programming. I do so love programming tutorials written for designers. Thank you, pretty colourful website!</p>
]]></content:encoded>
			<wfw:commentRss>http://triggersandsparks.com/blog/ajax-frameworks-head-desk-head-desk/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How To Take a Screenshot And Get Your Problems Solved Faster!</title>
		<link>http://triggersandsparks.com/blog/how-to-take-a-screenshot-and-get-your-problems-solved-faster/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=how-to-take-a-screenshot-and-get-your-problems-solved-faster</link>
		<comments>http://triggersandsparks.com/blog/how-to-take-a-screenshot-and-get-your-problems-solved-faster/#comments</comments>
		<pubDate>Mon, 19 Nov 2007 20:40:53 +0000</pubDate>
		<dc:creator>sarah semark</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[how-to]]></category>
		<category><![CDATA[information]]></category>
		<category><![CDATA[resources]]></category>
		<category><![CDATA[screenshot]]></category>
		<category><![CDATA[tutorial]]></category>
		<category><![CDATA[websites]]></category>

		<guid isPermaLink="false">http://kiss.triggersandsparks.com/?p=56</guid>
		<description><![CDATA[So, let’s say you’re having a problem with your email, or if you’ve found a bug in your website. Your first instinct, naturally, is to fire off an email to your trusty web-person. But wait! Before you hit send, make sure you’ve included as much detail as possible—what you were trying to do when the [...]]]></description>
			<content:encoded><![CDATA[<p>So, let’s say you’re having a problem with your email, or if you’ve found a bug in your website. Your first instinct, naturally, is to fire off an email to your trusty web-person. But wait! Before you hit send, make sure you’ve included as much detail as possible—what you were trying to do when the error happened, what sort of error message (if any) you got, what software you were using at the time, etc. This will help your trusty web-person track down the problem far, far more quickly.</p>
<p>An excellent way of supplementing this information is by sending along a screenshot. I’ll often request this of clients when I can’t replicate a reported bug—if you’ve sent one to begin with, I can be that much more effective.</p>
<p>Here’s how you do it.<br />
<span id="more-230"></span></p>
<h2>On a PC:</h2>
<ul>
<li>Make sure your screen is showing what you’d like it to.</li>
<li>Find the “Print Screen” button on your keyboard. It should be to the right, above the arrow keys and the “Page Up” and “Page Down” keys, and will probably be marked “Prnt Scrn” or somesuch. If you use a laptop, it will probably be up along the top, sharing key space with a function key.</li>
<li>Once located, press the button! (If it’s on a function key, you’ll probably need to hold down your function key while you’re doing it.)</li>
<li>Open up a graphics editing program. Photoshop, Paint Shop Pro, and Paint will all work equally effectively for this. Open a new document the size of your screen.</li>
<li>Select “Edit » Paste” from your menu, or press Control-V. Your screenshot will appear in your new document.</li>
<li>Save this document (“File » Save” or Control-S) to your computer.</li>
<li>Open up your email program, attach the file you just saved, and send away!</li>
</ul>
<h2>On a Mac:</h2>
<ul>
<li>Open a Finder Window.</li>
<li>Browse to “Applications » Utilities”. Launch Grab.app.</li>
<li>Select “Capture” from Grab’s menu. Select one of the options according to your preferences (“Screen” will do quite nicely!) <em>or</em> just hit Command+Z.</li>
<li>Follow the on-screen instructions. Your Mac will make a clickity-camera noise when it takes the screenshot.</li>
<li>Back to Grab. It will contain a new document that is a picture of your screen. Save it to your computer (“File » Save” or Command-S).</li>
<li>Open up your mail program of choice, attach your saved file (it will be saved as a .tiff file, which is perfect), and send to your happy web-person!</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://triggersandsparks.com/blog/how-to-take-a-screenshot-and-get-your-problems-solved-faster/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

