<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
	>
<channel>
	<title>Comments on: When I Mean Context</title>
	<atom:link href="http://aloedream.animeblogger.net/archives/257/feed" rel="self" type="application/rss+xml" />
	<link>http://aloedream.animeblogger.net/archives/257</link>
	<description>enjoying my nightmare</description>
	<pubDate>Mon, 23 Nov 2009 01:45:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ryan A</title>
		<link>http://aloedream.animeblogger.net/archives/257/comment-page-1#comment-18338</link>
		<dc:creator>Ryan A</dc:creator>
		<pubDate>Wed, 18 Mar 2009 14:31:43 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=257#comment-18338</guid>
		<description>Yay! Well, as you know the new melative is running on nuclear, so it's basically that (and I don't have to modify how it works, plug-n-play). The good thing is that most of the API calls are totally independent of each other (but possibly related = copy-pasta or inheritance). Honestly, the php is rather lax aside from nuclear. Really all it does is a couple validity checks on ids and mostly SQL calls (I'd say 70% of the source file sizes are in SQL).... minimal php theory, so it's pretty straightforward (usually).

I would spend more time with javascript/xsl/xml/css, but then the php or db stuff would never get finished... btw, I will be making the javascript for the nuclear api; simple, abstract, precise for API calls, just pass the thing to an xml request and whoosh.</description>
		<content:encoded><![CDATA[<p>Yay! Well, as you know the new melative is running on nuclear, so it&#8217;s basically that (and I don&#8217;t have to modify how it works, plug-n-play). The good thing is that most of the API calls are totally independent of each other (but possibly related = copy-pasta or inheritance). Honestly, the php is rather lax aside from nuclear. Really all it does is a couple validity checks on ids and mostly SQL calls (I&#8217;d say 70% of the source file sizes are in SQL)&#8230;. minimal php theory, so it&#8217;s pretty straightforward (usually).</p>
<p>I would spend more time with javascript/xsl/xml/css, but then the php or db stuff would never get finished&#8230; btw, I will be making the javascript for the nuclear api; simple, abstract, precise for API calls, just pass the thing to an xml request and whoosh.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mellow_bunny</title>
		<link>http://aloedream.animeblogger.net/archives/257/comment-page-1#comment-18332</link>
		<dc:creator>mellow_bunny</dc:creator>
		<pubDate>Wed, 18 Mar 2009 07:32:31 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=257#comment-18332</guid>
		<description>THIS STUFF ROX MY SOX AND YOU KNOW IT. Now if I could only apply myself to learning how the code works I could help you.</description>
		<content:encoded><![CDATA[<p>THIS STUFF ROX MY SOX AND YOU KNOW IT. Now if I could only apply myself to learning how the code works I could help you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
