<?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>gwycon.com &#187; core</title>
	<atom:link href="http://www.gwycon.com/tag/core/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gwycon.com</link>
	<description>Silverlight, WPF and C# .NET development</description>
	<lastBuildDate>Sat, 10 Jul 2010 13:11:23 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Adding menus to WordPress 2.7 admin header</title>
		<link>http://www.gwycon.com/adding-menus-to-wordpress-27-admin-header/</link>
		<comments>http://www.gwycon.com/adding-menus-to-wordpress-27-admin-header/#comments</comments>
		<pubDate>Thu, 19 Mar 2009 16:07:04 +0000</pubDate>
		<dc:creator>David</dc:creator>
				<category><![CDATA[WordPress Plugins]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[core]]></category>
		<category><![CDATA[hook]]></category>
		<category><![CDATA[menu]]></category>
		<category><![CDATA[Plugin]]></category>
		<category><![CDATA[short cuts]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://gwycon.com/?p=1959</guid>
		<description><![CDATA[I noticed from the documentation that you are supposed to be able to hook into the new WordPress 2.7 admin short cuts menu (but it doesn&#8217;t say how)! Ok, so after a little digging around in the WordPress core, the admin-header.php file (in the wp-admin folder) contains the code for the admin header. In the [...]]]></description>
		<wfw:commentRss>http://www.gwycon.com/adding-menus-to-wordpress-27-admin-header/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Avoiding WordPress Plugin Conflicts</title>
		<link>http://www.gwycon.com/avoiding-wordpress-plugin-conflicts/</link>
		<comments>http://www.gwycon.com/avoiding-wordpress-plugin-conflicts/#comments</comments>
		<pubDate>Fri, 06 Mar 2009 18:01:18 +0000</pubDate>
		<dc:creator>David</dc:creator>
				<category><![CDATA[WordPress Plugins]]></category>
		<category><![CDATA[action]]></category>
		<category><![CDATA[administrator]]></category>
		<category><![CDATA[attributes]]></category>
		<category><![CDATA[conflicts]]></category>
		<category><![CDATA[core]]></category>
		<category><![CDATA[customise]]></category>
		<category><![CDATA[filter]]></category>
		<category><![CDATA[hook]]></category>
		<category><![CDATA[Plugin]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://gwycon.com/?p=1483</guid>
		<description><![CDATA[It has been an enjoyable experience delving into the inner workings of WordPress of late. And it has been during the development of one of our recent projects, the &#8216;WP Content Filter&#8217;, our first WordPress Plugin by the way , that we have come across some unanticipated subtleties. For instance, any WordPress Plugin is free [...]]]></description>
		<wfw:commentRss>http://www.gwycon.com/avoiding-wordpress-plugin-conflicts/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
