<?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>occasionally useful &#187; ramaze</title>
	<atom:link href="http://blog.maxaller.name/category/ruby/ramaze/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.maxaller.name</link>
	<description>ruby, ubuntu, etc</description>
	<lastBuildDate>Sun, 11 Jul 2010 07:01:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Announcing: Ramastic, a skeleton for Ramaze</title>
		<link>http://blog.maxaller.name/2009/04/announcing-ramastic-a-skeleton-for-ramaze/</link>
		<comments>http://blog.maxaller.name/2009/04/announcing-ramastic-a-skeleton-for-ramaze/#comments</comments>
		<pubDate>Sat, 18 Apr 2009 08:01:09 +0000</pubDate>
		<dc:creator>Max</dc:creator>
				<category><![CDATA[ramaze]]></category>
		<category><![CDATA[ruby]]></category>

		<guid isPermaLink="false">http://blog.maxaller.name/?p=130</guid>
		<description><![CDATA[This is something I've been working on since slightly before my original call for suggestions a while back.  It's not done yet (I'd say it's somewhere around 75% done) but I want to get it out there before I totally lose steam on it.  There are a few inline styles I was planning on removing, [...]]]></description>
			<content:encoded><![CDATA[<p>This is something I've been working on since slightly before my original call for suggestions a while back.  It's not done yet (I'd say it's somewhere around 75% done) but I want to get it out there before I totally lose steam on it.  There are a few inline styles I was planning on removing, but haven't gotten around to, so...apologies.  If you find it of use, please leave a comment.</p>
<p>And yes, it doesn't <em>look</em> that great.  But I'm expecting you to restyle everything anyway and possibly blow away the templates entirely in your instantiation of the skeleton.</p>
<p>Now, without further ado, here are features and screenshots:</p>
<h2>Features/requirements</h2>
<ul>
<li>Built on <a href="http://github.com/TwP/bones/tree/master" target="_blank">Bones</a></li>
<li>Edge Rack/Innate/Ramaze</li>
<li>Haml/Sass</li>
<li>Sequel + sqlite3</li>
<li>Blueprint CSS</li>
<li>jQuery, jQuery UI</li>
<li>OpenID (via <a href="http://www.rpxnow.com/" target="_blank">RPX</a>)</li>
<li><a href="http://github.com/adamwiggins/rest-client/tree/master" target="_blank">RestClient</a></li>
<li><a href="http://github.com/jnunemaker/crack/tree/master" target="_blank">Crack</a></li>
<li><a href="http://github.com/assaf/uuid/tree/master" target="_blank">UUID</a></li>
<li><a href="http://github.com/nakajima/rack-flash/tree/master" target="_blank">Rack-flash</a></li>
</ul>
<h2>Screenshots</h2>
<ul>
<li><a href="http://www.flickr.com/photos/7766113@N02/sets/72157616875804949/detail/" target="_blank">Individual pages</a></li>
<li><a href="http://www.flickr.com/photos/7766113@N02/sets/72157616875804949/show/" target="_blank">Slideshow</a></li>
</ul>
<h2>Repository</h2>
<p><a href="http://github.com/nanodeath/ramastic/tree/master" target="_blank">Github</a>.</p>
<p>Thanks for looking!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.maxaller.name/2009/04/announcing-ramastic-a-skeleton-for-ramaze/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Ideas Needed for Mr. Bones skeleton built on Ramaze</title>
		<link>http://blog.maxaller.name/2009/04/ideas-needed-for-mr-bones-skeleton-built-on-ramaze/</link>
		<comments>http://blog.maxaller.name/2009/04/ideas-needed-for-mr-bones-skeleton-built-on-ramaze/#comments</comments>
		<pubDate>Wed, 08 Apr 2009 08:00:50 +0000</pubDate>
		<dc:creator>Max</dc:creator>
				<category><![CDATA[idea]]></category>
		<category><![CDATA[ramaze]]></category>
		<category><![CDATA[ruby]]></category>
		<category><![CDATA[web 2.0]]></category>

		<guid isPermaLink="false">http://blog.maxaller.name/?p=124</guid>
		<description><![CDATA[If I were to make a skeleton using Mr. Bones that was built on Ramaze, what would people like to see in it?  It's for my use first, but the community's use a close second if I can generalize it enough.  I was thinking along the lines of openid support, having a decent home page [...]]]></description>
			<content:encoded><![CDATA[<p>If I were to make a skeleton using <a href="http://codeforpeople.rubyforge.org/bones/" target="_blank">Mr. Bones</a> that was built on <a href="http://ramaze.net/" target="_blank">Ramaze</a>, what would people like to see in it?  It's for my use first, but the community's use a close second if I can generalize it enough.  I was thinking along the lines of openid support, having a decent home page and logged-in-user gateway, appropriate nav-bars, haml+sass, jquery+ui, etc....thoughts?  What do you find yourself doing at the beginning of every website project that you'd like to not have to repeat every time you start a project?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.maxaller.name/2009/04/ideas-needed-for-mr-bones-skeleton-built-on-ramaze/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Gotcha with Sequel and Association Caching</title>
		<link>http://blog.maxaller.name/2009/03/gotcha-with-sequel-and-association-caching/</link>
		<comments>http://blog.maxaller.name/2009/03/gotcha-with-sequel-and-association-caching/#comments</comments>
		<pubDate>Sun, 08 Mar 2009 19:30:06 +0000</pubDate>
		<dc:creator>Max</dc:creator>
				<category><![CDATA[ramaze]]></category>
		<category><![CDATA[ruby]]></category>
		<category><![CDATA[sequel]]></category>

		<guid isPermaLink="false">http://blog.maxaller.name/?p=73</guid>
		<description><![CDATA[One thing to remember with Sequel is that it caches associations -- for an hour, by default.  Normally this is good -- if I say my_model.my_associated_models twice in one request, I'd like that to be cached.  But at least with Ramaze, where you can access a variable that persists between requests (via session, [...]]]></description>
			<content:encoded><![CDATA[<p>One thing to remember with <a href="http://sequel.rubyforge.org/">Sequel</a> is that it caches associations -- for an hour, by default.  Normally this is good -- if I say my_model.my_associated_models twice in one request, I'd like that to be cached.  But at least with <a href="http://ramaze.net/">Ramaze</a>, where you can access a variable that persists between requests (via session, like session[:user]), you have to remember that associations on that session object get cached, too.  So what does that mean?  That means if you have a user view their posts (with session[:user].posts), and then they go make a post, and then they come back to view their posts again...the new post won't be in the list of posts!  So you have two basic options here, that I know of -- either a) manually kill the cache by putting session[:user].refresh on the action that alters the associations of session[:user], or b) put session[:user].refresh in a place that gets executed at the beginning of every request.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.maxaller.name/2009/03/gotcha-with-sequel-and-association-caching/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
