<?xml version="1.0" encoding="UTF-8"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>ThemeShaper Forums Topic: fao: ian or chris</title>
<link>http://themeshaper.com/forums/</link>
<description>Help In Shaping WordPress Themes</description>
<language>en</language>
<pubDate>Sat, 25 May 2013 12:48:08 +0000</pubDate>

<item>
<title>Jonny Janiero on "fao: ian or chris"</title>
<link>http://themeshaper.com/forums/topic/fao-ian-or-chris#post-16691</link>
<pubDate>Tue, 02 Nov 2010 17:46:18 +0000</pubDate>
<dc:creator>Jonny Janiero</dc:creator>
<guid isPermaLink="false">16691@http://themeshaper.com/forums/</guid>
<description>&#60;p&#62;if poss, wanted your opinion on this.&#60;/p&#62;
&#60;p&#62;there has been much talk about selling thematic child themes on themeforest, etc.&#60;/p&#62;
&#60;p&#62;this is something i'm looking into. the obvious approach would be to bundle the latest thematic folder alongside the child theme. keeping both, obviously seperate. or direct them to a direct download (which may be confusing to some)&#60;/p&#62;
&#60;p&#62;i noticed someone sold a thematic theme on themeforest in which they merged both.&#60;br /&#62;
adding...&#60;br /&#62;
&#60;pre&#62;&#60;code&#62;//include  Functions (last to override others)
require_once(TEMPLATEPATH.&#38;#39;/child_theme/functions.php&#38;#39;);&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;to the original thematic function.php&#60;/p&#62;
&#60;p&#62;this then becomes self-bundled, then renamed as one theme.&#60;br /&#62;
no longer does the thematic theme stand-alone in wp-admin-themes.&#60;br /&#62;
(all credits still intact in files and theme description).&#60;/p&#62;
&#60;p&#62;would you consider this good practice / ethical to thematic ?&#60;/p&#62;
&#60;p&#62;appreciate any thoughts on this. i want to do things properly as i love thematic and i'm very grateful for such a great framework and community.
&#60;/p&#62;</description>
</item>

</channel>
</rss>
