<?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: Release 0.8.3</title>
	<atom:link href="http://www.metabates.com/2009/01/18/release-083/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.metabates.com/2009/01/18/release-083/</link>
	<description>The technical ramblings of Mark Bates.</description>
	<lastBuildDate>Wed, 17 Aug 2011 16:45:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Philip MacIver</title>
		<link>http://www.metabates.com/2009/01/18/release-083/comment-page-1/#comment-180</link>
		<dc:creator>Philip MacIver</dc:creator>
		<pubDate>Wed, 28 Jan 2009 06:52:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.mackframework.com/?p=214#comment-180</guid>
		<description>Okay, just used the haml thing and it seemed to work, all except the layout. When I use a layout with an erb extension it works fine, but when I use one with a haml extension it gives me the following

 /progs/web/test_app/app/views/layouts/application.html.*

Maybe a small bug where views only expect erb layouts?</description>
		<content:encoded><![CDATA[<p>Okay, just used the haml thing and it seemed to work, all except the layout. When I use a layout with an erb extension it works fine, but when I use one with a haml extension it gives me the following</p>
<p> /progs/web/test_app/app/views/layouts/application.html.*</p>
<p>Maybe a small bug where views only expect erb layouts?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip MacIver</title>
		<link>http://www.metabates.com/2009/01/18/release-083/comment-page-1/#comment-179</link>
		<dc:creator>Philip MacIver</dc:creator>
		<pubDate>Wed, 28 Jan 2009 05:28:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.mackframework.com/?p=214#comment-179</guid>
		<description>By the way, what is the difference between the first parameter, and the one that is passed in that is called :libs, are they not just one and the same?</description>
		<content:encoded><![CDATA[<p>By the way, what is the difference between the first parameter, and the one that is passed in that is called :libs, are they not just one and the same?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip MacIver</title>
		<link>http://www.metabates.com/2009/01/18/release-083/comment-page-1/#comment-178</link>
		<dc:creator>Philip MacIver</dc:creator>
		<pubDate>Wed, 28 Jan 2009 05:08:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.mackframework.com/?p=214#comment-178</guid>
		<description>Thanks for that.

One thing that I have noticed of all frameworks, not just this one, is that when there is a default there is nowhere that shows it is a default in the running app.

I just think that for the sake of clarity, that if something is a default it is a default because there is a line in a config file, in the running app that says something similar to what you have for the haml example you put up

require_gems do &#124;gem&#124;  
  gem.add &quot;mack-haml&quot;, :libs =&gt; &quot;mack-haml&quot;  
end

But this should be for every default action in the running app. And if it isn&#039;t there then the individual things that make up app wont work.

I see this as having 2 advantages

1. Anyone creating an app, especially for the first time like I did can see exactly what is being loaded by just looking at one file

2. People can rip out and put in whatever gems they want, and it can be more customised stack of applications.

But only really looking at this app really for a day, I don&#039;t  know if the above makes sense to do. I just think that if this was how frameworks laid out themselves it would make a lot more sense to me, and less like a black box that magic things happen in.

Just my cents.

But again thanks for the piece of documentation you provided</description>
		<content:encoded><![CDATA[<p>Thanks for that.</p>
<p>One thing that I have noticed of all frameworks, not just this one, is that when there is a default there is nowhere that shows it is a default in the running app.</p>
<p>I just think that for the sake of clarity, that if something is a default it is a default because there is a line in a config file, in the running app that says something similar to what you have for the haml example you put up</p>
<p>require_gems do |gem|<br />
  gem.add &#8220;mack-haml&#8221;, :libs =&gt; &#8220;mack-haml&#8221;<br />
end</p>
<p>But this should be for every default action in the running app. And if it isn&#8217;t there then the individual things that make up app wont work.</p>
<p>I see this as having 2 advantages</p>
<p>1. Anyone creating an app, especially for the first time like I did can see exactly what is being loaded by just looking at one file</p>
<p>2. People can rip out and put in whatever gems they want, and it can be more customised stack of applications.</p>
<p>But only really looking at this app really for a day, I don&#8217;t  know if the above makes sense to do. I just think that if this was how frameworks laid out themselves it would make a lot more sense to me, and less like a black box that magic things happen in.</p>
<p>Just my cents.</p>
<p>But again thanks for the piece of documentation you provided</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Bates</title>
		<link>http://www.metabates.com/2009/01/18/release-083/comment-page-1/#comment-177</link>
		<dc:creator>Mark Bates</dc:creator>
		<pubDate>Wed, 28 Jan 2009 03:56:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.mackframework.com/?p=214#comment-177</guid>
		<description>Hi Philip, yeah, the documentation definitely needs work. To quote the Beatles, it&#039;s getting better all the time. I&#039;ve gone and added a section on mack-haml, just for you. :)

http://www.mackery.com/mack_more/haml/index

That should help you, it&#039;s pretty darn easy. Let me know if you have any questions.</description>
		<content:encoded><![CDATA[<p>Hi Philip, yeah, the documentation definitely needs work. To quote the Beatles, it&#8217;s getting better all the time. I&#8217;ve gone and added a section on mack-haml, just for you. <img src='http://www.metabates.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p><a href="http://www.mackery.com/mack_more/haml/index" rel="nofollow">http://www.mackery.com/mack_more/haml/index</a></p>
<p>That should help you, it&#8217;s pretty darn easy. Let me know if you have any questions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip MacIver</title>
		<link>http://www.metabates.com/2009/01/18/release-083/comment-page-1/#comment-176</link>
		<dc:creator>Philip MacIver</dc:creator>
		<pubDate>Tue, 27 Jan 2009 23:16:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.mackframework.com/?p=214#comment-176</guid>
		<description>I have been trying to look for more documentation than currently exists in the user manual, but I am finding it very hard to track any down. 

What I am looking for is things like, if I want to use haml instead of erb, what do I need to do? Do I have to require a gem in some file? or set it in a config file somewhere. 

I would love to jump in and build an app with this, but the lack of documentation and resources to find out the things that I want is very frustrating.

Any help would be welcome. 

Thanks</description>
		<content:encoded><![CDATA[<p>I have been trying to look for more documentation than currently exists in the user manual, but I am finding it very hard to track any down. </p>
<p>What I am looking for is things like, if I want to use haml instead of erb, what do I need to do? Do I have to require a gem in some file? or set it in a config file somewhere. </p>
<p>I would love to jump in and build an app with this, but the lack of documentation and resources to find out the things that I want is very frustrating.</p>
<p>Any help would be welcome. </p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Takita</title>
		<link>http://www.metabates.com/2009/01/18/release-083/comment-page-1/#comment-175</link>
		<dc:creator>Brian Takita</dc:creator>
		<pubDate>Wed, 21 Jan 2009 18:59:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.mackframework.com/?p=214#comment-175</guid>
		<description>@Geezzzer:
http://www.mackery.com/</description>
		<content:encoded><![CDATA[<p>@Geezzzer:<br />
<a href="http://www.mackery.com/" rel="nofollow">http://www.mackery.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Kubb</title>
		<link>http://www.metabates.com/2009/01/18/release-083/comment-page-1/#comment-174</link>
		<dc:creator>Dan Kubb</dc:creator>
		<pubDate>Tue, 20 Jan 2009 09:55:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.mackframework.com/?p=214#comment-174</guid>
		<description>I just wanted to drop a note to let everyone using the Mack Framework that DataMapper 0.9.10 was released today and now provides Ruby 1.9 support.</description>
		<content:encoded><![CDATA[<p>I just wanted to drop a note to let everyone using the Mack Framework that DataMapper 0.9.10 was released today and now provides Ruby 1.9 support.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geezzzer</title>
		<link>http://www.metabates.com/2009/01/18/release-083/comment-page-1/#comment-172</link>
		<dc:creator>Geezzzer</dc:creator>
		<pubDate>Sun, 18 Jan 2009 20:17:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.mackframework.com/?p=214#comment-172</guid>
		<description>So, what is  Mack  anyway?</description>
		<content:encoded><![CDATA[<p>So, what is  Mack  anyway?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.334 seconds -->

