<?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>Robert Abramski</title>
	<atom:link href="http://robertabramski.com/feed" rel="self" type="application/rss+xml" />
	<link>http://robertabramski.com</link>
	<description>Web developer, designer and full time person.</description>
	<lastBuildDate>Thu, 23 Feb 2012 21:54:25 +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>PyroCMS Fonts Module</title>
		<link>http://robertabramski.com/blog/467</link>
		<comments>http://robertabramski.com/blog/467#comments</comments>
		<pubDate>Fri, 20 Jan 2012 04:49:03 +0000</pubDate>
		<dc:creator>robertabramski</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Work]]></category>

		<guid isPermaLink="false">http://blog.robertabramski.com/?p=467</guid>
		<description><![CDATA[I just released an addon module for PyroCMS. For those of you that may not know, PyroCMS is a content management system built on Codeigniter. For those of you that may not know Codeigniter, Google that shit. I can&#8217;t explain everything. The Fonts module manages, protects and obfuscates webfonts. Your webfonts are protected by checking [...]]]></description>
			<content:encoded><![CDATA[<p>I just released an addon module for <a href="http://www.pyrocms.com" target="_blank">PyroCMS</a>. For those of you that may not know, PyroCMS is a content management system built on <a href="http://www.codeigniter.com" target="_blank">Codeigniter</a>. For those of you that may not know Codeigniter, Google that shit. I can&#8217;t explain everything.</p>
<p>The Fonts module manages, protects and obfuscates webfonts. Your webfonts are protected by checking HTTP_REFERER to make sure that only requests from your website will be allowed to download the fonts. Direct directory download of the fonts is denied with an .htaccess rule in the fonts directory. The physical location of your fonts is hidden with programatic access through an encoded link.</p>
<p>This module allows you to manage all your webfonts. The fonts are accessible for any theme you use and can be disabled for usage if you aren&#8217;t using a particular font with the active theme. This module generates an @font-face stylesheet to display your fonts. This stylesheet link can be inserted into your themes with the {{fonts:css}} template tag. You can pick up a copy of it <a href="http://www.pyrocms.com/store/details/fonts_1">here</a> at the PyroCMS store for £2.</p>
<p>There are 2 branches of this module. One supports the 1.x.x version of PyroCMS and the other is made to 2.x.x and future versions of the CMS. As of the writing of this post, Fonts 1.0 is not on the store as they are having an internal meeting about how we&#8217;re handling 1.x modules in their new store.</p>
]]></content:encoded>
			<wfw:commentRss>http://robertabramski.com/blog/467/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cyntaxic Framework 0.1.2</title>
		<link>http://robertabramski.com/blog/459</link>
		<comments>http://robertabramski.com/blog/459#comments</comments>
		<pubDate>Fri, 19 Aug 2011 18:31:17 +0000</pubDate>
		<dc:creator>robertabramski</dc:creator>
				<category><![CDATA[ActionScript 3.0]]></category>
		<category><![CDATA[Flash]]></category>
		<category><![CDATA[Flex]]></category>
		<category><![CDATA[Work]]></category>

		<guid isPermaLink="false">http://blog.robertabramski.com/?p=459</guid>
		<description><![CDATA[The public release of my ActionScript framework is now available. Check out the shiny new site where you can find documentation and a user guide to help you get started. To make it even more simple, the site comes with Boilerplate, a utility that creates either a Flex or pure ActionScript project at a single [...]]]></description>
			<content:encoded><![CDATA[<p>The public release of my ActionScript framework is now available. Check out the <a href="http://cyntaxic.com" target="_blank">shiny new site</a> where you can find <a href="http://cyntaxic.com/docs" target="_blank">documentation</a> and a <a href="http://cyntaxic.com/guide" target="_blank">user guide</a> to help you get started. To make it even more simple, the site comes with <a href="http://cyntaxic.com#boilerplate" target="_blank">Boilerplate</a>, a utility that creates either a Flex or pure ActionScript project at a single click of a button.</p>
<p>I really think that the learning curve for this framework is minimal compared to some of the big names out there. I think that this is important for some less experienced programmers and some jobs that just don&#8217;t need a giant framework to get it done.</p>
<p>I don&#8217;t know how much I&#8217;ll be updating this framework, it really depends on the community. If it finds a place out there, then I will add to it and make it better. It also depends on jobs I get where I need to make something in ActionScript. If this framework is suitable for the project, I will probably improve upon it as I see where it needs improvement as I work.</p>
<p>A special thanks to <a href="http://www.facebook.com/markus.winkler1" target="_blank">Markus Winkler</a> for taking a look and giving his input. You can check out his site <a href="http://www.markuswinkler.com/" target="_blank">here</a>. You can follow the Cyntaxic framework on <a href="http://twitter.com/cyntaxic" target="_blank">Twitter</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://robertabramski.com/blog/459/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cyntaxic Framework 0.1.1</title>
		<link>http://robertabramski.com/blog/455</link>
		<comments>http://robertabramski.com/blog/455#comments</comments>
		<pubDate>Fri, 17 Jun 2011 02:34:10 +0000</pubDate>
		<dc:creator>robertabramski</dc:creator>
				<category><![CDATA[ActionScript 3.0]]></category>
		<category><![CDATA[Flash]]></category>
		<category><![CDATA[Flex]]></category>
		<category><![CDATA[Work]]></category>
		<category><![CDATA[actionscript]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[framework]]></category>
		<category><![CDATA[mvc]]></category>

		<guid isPermaLink="false">http://blog.robertabramski.com/?p=455</guid>
		<description><![CDATA[I just finished up the first public beta release on my ActionScript MVC framework, Cyntaxic. There is going to be a site launch for it coming soon. Right now, the beta can be checked out from my SVN repository. Comments are very welcome. The best place to put those comments is here until the site [...]]]></description>
			<content:encoded><![CDATA[<p>I just finished up the first public beta release on my ActionScript MVC framework, Cyntaxic. There is going to be a site launch for it <a href="http://cyntaxic.com" target="_blank">coming soon</a>. Right now, the beta can be checked out from my <a href="http://svn.robertabramski.com/cyntaxic" target="_blank">SVN repository</a>. Comments are very welcome. The best place to put those comments is here until the site launch. The documentation can for the framework can be found <a href="http://docs.cyntaxic.com" target="_blank">here</a>. I may make this prettier, or just less Adobe docs looking, but we will see about that for the official site launch.</p>
<p>Also, check out the demos built with Cyntaxic. The <a href="http://cyntaxic.com/demos/stickies" target="_blank">Stickies demo</a> is a pure ActionScript application showing off view management and the <a href="http://cyntaxic.com/demos/cyntils" target="_blank">Cyntils demo</a> is a Flex application displaying the Cyntaxic&#8217;s utility classes. The Stickies demo can be checked out from <a href="http://svn.robertabramski.com/stickies" target="_blank">here</a> and the Cyntils demo can be checked out from <a href="http://svn.robertabramski.com/cyntils" target="_blank">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://robertabramski.com/blog/455/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Looping with Nested Views in CodeIgniter</title>
		<link>http://robertabramski.com/blog/448</link>
		<comments>http://robertabramski.com/blog/448#comments</comments>
		<pubDate>Thu, 12 May 2011 16:40:53 +0000</pubDate>
		<dc:creator>robertabramski</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Work]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[codeigniter]]></category>

		<guid isPermaLink="false">http://blog.robertabramski.com/?p=446</guid>
		<description><![CDATA[I have been using CodeIgniter on my most current project and I am really happy with the way it works. If you know anything about MVC and OOP, there is very little learning curve to get moving with this framework. CodeIgniter allows you to create views to display information passed in from the controller and [...]]]></description>
			<content:encoded><![CDATA[<p>I have been using CodeIgniter on my most current project and I am really happy with the way it works. If you know anything about MVC and OOP, there is very little learning curve to get moving with this framework.</p>
<p>CodeIgniter allows you to create views to display information passed in from the controller and the models of the application. Usually if you are sending arrays of information to display you will have to loop over the array. I like to write as little markup as possible so I nest views of markup that are reusable. I came across a problem where I wanted to load a view in the middle of a loop and have that nested view be aware of where it is in the loop. I needed the information from that position in the loop. The nested views have access to the variables sent by the controller, but doesn&#8217;t keep track of foreach iteration variables.</p>
<p>Here is the solution that I cooked up to get that information over to the nested view. Instead of using a foreach loop I use just a for loop and pass the iterator over in the view&#8217;s data parameter. Below is pseudocode of how this might look.</p>

<div class="wp_syntax"><div class="code"><pre class="php" style="font-family:monospace;"><span style="color: #000000; font-weight: bold;">&lt;?php</span> <span style="color: #b1b100;">for</span><span style="color: #009900;">&#40;</span><span style="color: #000088;">$i</span> <span style="color: #339933;">=</span> <span style="color: #cc66cc;">0</span><span style="color: #339933;">;</span> <span style="color: #000088;">$i</span> <span style="color: #339933;">&lt;</span> <span style="color: #990000;">count</span><span style="color: #009900;">&#40;</span><span style="color: #000088;">$items</span><span style="color: #009900;">&#41;</span><span style="color: #339933;">;</span> <span style="color: #000088;">$i</span><span style="color: #339933;">++</span><span style="color: #009900;">&#41;</span><span style="color: #339933;">:</span> <span style="color: #000000; font-weight: bold;">?&gt;</span>
&lt;h1&gt;<span style="color: #000000; font-weight: bold;">&lt;?php</span> <span style="color: #b1b100;">echo</span> <span style="color: #000088;">$items</span><span style="color: #009900;">&#91;</span><span style="color: #000088;">$i</span><span style="color: #009900;">&#93;</span><span style="color: #009900;">&#91;</span><span style="color: #0000ff;">'title'</span><span style="color: #009900;">&#93;</span><span style="color: #339933;">;</span> <span style="color: #000000; font-weight: bold;">?&gt;</span>&lt;/h1&gt;
<span style="color: #000000; font-weight: bold;">&lt;?php</span> <span style="color: #000088;">$this</span><span style="color: #339933;">-&gt;</span><span style="color: #004000;">load</span><span style="color: #339933;">-&gt;</span><span style="color: #004000;">view</span><span style="color: #009900;">&#40;</span><span style="color: #0000ff;">'nestedview'</span><span style="color: #339933;">,</span> <span style="color: #990000;">array</span><span style="color: #009900;">&#40;</span><span style="color: #0000ff;">'i'</span> <span style="color: #339933;">=&gt;</span> <span style="color: #000088;">$i</span><span style="color: #009900;">&#41;</span><span style="color: #009900;">&#41;</span><span style="color: #339933;">;</span> <span style="color: #000000; font-weight: bold;">?&gt;</span>
<span style="color: #000000; font-weight: bold;">&lt;?php</span> <span style="color: #b1b100;">endfor</span><span style="color: #339933;">;</span> <span style="color: #000000; font-weight: bold;">?&gt;</span></pre></div></div>

]]></content:encoded>
			<wfw:commentRss>http://robertabramski.com/blog/448/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bulletproof Handling for IE6</title>
		<link>http://robertabramski.com/blog/436</link>
		<comments>http://robertabramski.com/blog/436#comments</comments>
		<pubDate>Sat, 02 Apr 2011 02:11:17 +0000</pubDate>
		<dc:creator>robertabramski</dc:creator>
				<category><![CDATA[Work]]></category>

		<guid isPermaLink="false">http://blog.robertabramski.com/?p=436</guid>
		<description><![CDATA[I&#8217;m going to be using this in all upcoming projects and you should too. It fixes every issue that IE6 has. It fixes the light blue PNG background issue, it fixes the box model, it fixes all the hover issues, it fixes all the JavaScript inconsistencies and probably even all the security holes. &#60;!--[if lte [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m going to be using this in all upcoming projects and you should too. It fixes every issue that IE6 has. It fixes the light blue PNG background issue, it fixes the box model, it fixes all the hover issues, it fixes all the JavaScript inconsistencies and probably even all the security holes.</p>

<div class="wp_syntax"><div class="code"><pre class="hmtl" style="font-family:monospace;">&lt;!--[if lte IE 6]&gt;
&lt;script&gt;location.href='http://ie6countdown.com'&lt;/script&gt;
&lt;![endif]--&gt;</pre></div></div>

]]></content:encoded>
			<wfw:commentRss>http://robertabramski.com/blog/436/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Eulogy for Past Electronics</title>
		<link>http://robertabramski.com/blog/429</link>
		<comments>http://robertabramski.com/blog/429#comments</comments>
		<pubDate>Tue, 22 Mar 2011 16:07:02 +0000</pubDate>
		<dc:creator>robertabramski</dc:creator>
				<category><![CDATA[Mac]]></category>
		<category><![CDATA[Work]]></category>

		<guid isPermaLink="false">http://blog.robertabramski.com/?p=429</guid>
		<description><![CDATA[I was recently forced to make some major upgrades to to my gear. I had two minor catastrophes befall me almost at the same time. First, my laptop died. I&#8217;m not sure what caused it but I suspect that it was turning it on before it was up to proper operating temperature. I had it [...]]]></description>
			<content:encoded><![CDATA[<p>I was recently forced to make some major upgrades to to my gear. I had two minor catastrophes befall me almost at the same time. First, my laptop died. I&#8217;m not sure what caused it but I suspect that it was turning it on before it was up to proper operating temperature. I had it in winter storage while moving. It will run for a while, but I reliably  get the &#8220;you are fucked in every language&#8221; screen. It was a Power Book G4, so it was like a great, great grandpappy to the MacBook Pro now available. It was not really an unexpected loss at that age.</p>
<p>To replace my old laptop which wasn&#8217;t even fast enough to run YouTube videos anymore, I bought the 11&#8243; MacBook Air. I am pretty happy with it. The only thing that I can even complain about is the shiny screen. I&#8217;ve never been a fan of the shiny; it makes your screen a mirror with ambient lighting. Also, battery life is no where near the 9 hours Apple boast. I&#8217;m running just Safari now and I am at half a tank just from writing this post.</p>
<p>Next , there was a power outage that claimed my 23&#8243; Apple Cinema Display despite having it plugged in to a surge protector. The monitor just never powered back up after the electricity came back. I can&#8217;t exactly tell if it was the 200 pound adapter I had to use to convert to the signal or the monitor itself that actually broke, but because the monitor was so old, I didn&#8217;t have any other device to test it with. Once again, this was an old piece of equipment and not really an unexpected loss.</p>
<p>One of the reasons that I kept this monitor so long was because I wasn&#8217;t a fan of the alternative monitors out there. The aluminum Cinema Display was pretty good, but Apple discontinued it before I got a chance to buy it. The new Apple lineup is a lineup of one monitor. I remember when there was three options, but the 27&#8243; Cinema Display is all they have in terms of a lineup these days. It only comes in shiny screen. The MacBook Pro has a matte finish option, but no such luck with the so called lineup. Despite the limited options, I am a Mac dick at heart and I had to buy Apple. So, I bought the Cinema Display and I am overall happy with it. The shiny screen took a while to get used to but if you keep your room lighting a certain way, it is not too noticeable. I think the MacBook Air screen kind of prepared me for the shiny on this thing. The other thing is the cord is way too short. I had to move my computer closer to the monitor to plug it in. On the pro side, the monitor has three USB 2 ports, an awesome iSight camera that works with Skype zero config and internal speakers if you don&#8217;t have speakers already. It even has a MagSafe plug if  you want to plug in and charge your laptop. That&#8217;s if the cord will reach. I guess you just got to take the good with the bad.</p>
<p>Overall, I am think I have some good products that will last me just as long as my retired Apple products.</p>
]]></content:encoded>
			<wfw:commentRss>http://robertabramski.com/blog/429/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Automator Workflows</title>
		<link>http://robertabramski.com/blog/425</link>
		<comments>http://robertabramski.com/blog/425#comments</comments>
		<pubDate>Sun, 23 Jan 2011 21:48:18 +0000</pubDate>
		<dc:creator>robertabramski</dc:creator>
				<category><![CDATA[Mac]]></category>
		<category><![CDATA[Work]]></category>

		<guid isPermaLink="false">http://blog.robertabramski.com/?p=425</guid>
		<description><![CDATA[I&#8217;ve written a few Automator workflows to handle some pretty specific things. For the most part, they are just shell scripts I&#8217;ve found around and written into a workflow. I&#8217;ve posted them here. There is a workflow to copy a path of the selected folder, a script to show system files and script to hide [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve written a few Automator workflows to handle some pretty specific things. For the most part, they are just shell scripts I&#8217;ve <a href="http://www.michaelhanley.org/blog/2010/10/remove-subversion-svn-folders-on-mac-os-x.html" target="_blank">found</a> around and written into a workflow. I&#8217;ve posted them <a href="http://robertabramski.com/wp-content/uploads/2011/01/workflows.zip">here</a>. There is a workflow to copy a path of the selected folder, a script to show system files and script to hide them, and a script to remove all SVN metadata from a selected folder.</p>
]]></content:encoded>
			<wfw:commentRss>http://robertabramski.com/blog/425/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Notifying Facebook &amp; Twitter From WordPress</title>
		<link>http://robertabramski.com/blog/418</link>
		<comments>http://robertabramski.com/blog/418#comments</comments>
		<pubDate>Fri, 21 Jan 2011 21:40:50 +0000</pubDate>
		<dc:creator>robertabramski</dc:creator>
				<category><![CDATA[Work]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[post]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://blog.robertabramski.com/?p=418</guid>
		<description><![CDATA[Are you still copying and pasting blog entry links into Twitter and Facebook after you write a post? That&#8217;s for senior citizens. Below is a way to hook it up so when you write a post in your blog it will show up on both Twitter and Facebook. The first thing to do is to [...]]]></description>
			<content:encoded><![CDATA[<p>Are you still copying and pasting blog entry links into Twitter and Facebook after you write a post? That&#8217;s for senior citizens. Below is a way to hook it up so when you write a post in your blog it will show up on both Twitter and Facebook.</p>
<p>The first thing to do is to add the Twitter app to your Facebook account using the <a href="http://apps.facebook.com/twitter/" target="_blank">Twitter Facebook app</a>. Input your Twitter information or just accept if you are already signed in to Twitter. Now anything you write in Twitter will show up in Facebook.</p>
<p>The next step is to connect your blog to Twitter. <a href="http://crowdfavorite.com/wordpress/plugins/twitter-tools/" target="_blank">Download Twitter Tools</a> from <a href="http://crowdfavorite.com/" target="_blank">Crowd Favorite</a>. Activate the plugin on your blog and go to the settings page. The plugin will ask for some very specific information from Twitter. Twitter just changed their API to OAuth and you have to jump through a lot of hoops, which is kind of annoying. Go to <a href="http://dev.twitter.com/apps/new" target="_blank">this page</a> to setup a new Twitter app.</p>
<p>The Twitter app form will ask for some information. Fill out the form and it will give you a Consumer Key, Consumer Secret, Access Token and Access Token Secret. Insert this information into the plugin. Once the Twitter app information is saved, you are done. This will make it so your blog will send to Twitter and Twitter will send to Facebook.</p>
]]></content:encoded>
			<wfw:commentRss>http://robertabramski.com/blog/418/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Uploader WordPress Plugin</title>
		<link>http://robertabramski.com/blog/409</link>
		<comments>http://robertabramski.com/blog/409#comments</comments>
		<pubDate>Fri, 21 Jan 2011 20:50:14 +0000</pubDate>
		<dc:creator>robertabramski</dc:creator>
				<category><![CDATA[Work]]></category>
		<category><![CDATA[plugin]]></category>
		<category><![CDATA[uploader]]></category>
		<category><![CDATA[uploadify]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://blog.robertabramski.com/?p=409</guid>
		<description><![CDATA[I&#8217;ve written my first WordPress plugin and added it to WordPress&#8217; plugin repository. It is available for download here. It&#8217;s a pretty simple plugin that I hope to add into a larger plugin that I am planning to put together for the rollout of my personal site, which has been a long time coming. Now [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve written my first WordPress plugin and added it to WordPress&#8217; plugin repository. It is available for download <a href="http://wordpress.org/extend/plugins/uploader/">here</a>. It&#8217;s a pretty simple plugin that I hope to add into a larger plugin that I am planning to put together for the rollout of my personal site, which has been a long time coming. Now that I don&#8217;t have a job, maybe I can complete some of these projects I have building up over the years. Below is the description of the plugin.</p>
<p>Uploader creates an Uploader role (a Subscriber role with an extra <code>uploader_upload</code> capability) for blind file uploading within wp-admin after credentials have been input in wp-login.php. This plugin is based on the <a href="http://www.uploadify.com/">Uploadify</a> project.</p>
]]></content:encoded>
			<wfw:commentRss>http://robertabramski.com/blog/409/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>M is for Bone</title>
		<link>http://robertabramski.com/blog/402</link>
		<comments>http://robertabramski.com/blog/402#comments</comments>
		<pubDate>Thu, 22 Jul 2010 19:05:38 +0000</pubDate>
		<dc:creator>robertabramski</dc:creator>
				<category><![CDATA[Flash]]></category>
		<category><![CDATA[Work]]></category>
		<category><![CDATA[adobe]]></category>
		<category><![CDATA[commands]]></category>
		<category><![CDATA[keystroke]]></category>

		<guid isPermaLink="false">http://blog.robertabramski.com/?p=402</guid>
		<description><![CDATA[It looks like Creative Suite CS5 has amended their zoom keystroke bungle they released with CS4. I wrote a post about it here. They changed the default keystroke of zoom to m (and renamed it Magnify) to make room for a third string tool like the Bone tool. Firstly, bone doesn&#8217;t even begin with z, [...]]]></description>
			<content:encoded><![CDATA[<p>It looks like Creative Suite CS5 has amended their zoom keystroke bungle they released with CS4. I wrote a post <a href="http://robertabramski.com/2009/02/07/m-is-for-zoom/" target="_blank">about it here</a>. They changed the default keystroke of zoom to m (and renamed it Magnify) to make room for a third string tool like the Bone tool. Firstly, bone doesn&#8217;t even begin with z, so why would it make sense to transpose those? The keystroke for the Zoom tool is z in every Adobe program, so why was an exception made for Flash? I guess there was a public outcry or Adobe checked their user data and found that everyone changing it back to the way it should be.</p>
]]></content:encoded>
			<wfw:commentRss>http://robertabramski.com/blog/402/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

