+1<br><br><div class="gmail_quote">On Tue, May 3, 2011 at 1:09 PM, Justin Tadlock <span dir="ltr"><<a href="mailto:justin@justintadlock.com">justin@justintadlock.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div text="#000000" bgcolor="#ffffff">
If a theme creates a custom post type, the theme developer should
really be creating an additional plugin for users that eventually
switch themes to handle that post type so that there's no data that
can't be used and nothing that "locks in" the user.<br>
<br>
I just had a long discussion over this situation a week or so ago.
The solution we came up with instead of bundling custom post types
in themes:<br>
<br>
The best option is to create a plugin for custom post types. Then,
build themes that support this plugin with custom templates and CSS
(or whatever would be required on the theme's end). It's a win-win
situation for both users and developers. The developer can corner
the market on whatever functionality that plugin is providing and
users will have more than one theme to choose from.<br>
<br>
Suppose you had a "real estate" plugin. The plugin would handle all
of the complex functionality. The theme would simply house the
templates and styles to handle the display of the content.<div><div></div><div class="h5"><br>
<br>
On 5/2/2011 11:22 AM, Chip Bennett wrote:
<blockquote type="cite">What is the content of the slideshow?
<div><br>
</div>
<div>Chip<br>
<br>
<div class="gmail_quote">On Mon, May 2, 2011 at 11:17 AM, Curtis
McHale <span dir="ltr"><<a href="mailto:curtis@curtismchale.ca" target="_blank">curtis@curtismchale.ca</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">I reviewed a theme recently that used a
CPT to add slideshow functions. Would that use of CPT be
acceptable?<br clear="all">
<font color="#888888"><br>
Curtis McHale<br>
PH: 604.751.3482<br>
<a href="http://www.curtismchale.ca" target="_blank">http://www.curtismchale.ca</a><br>
Linkedin: <a href="http://www.linkedin.com/in/curtismchale" target="_blank">http://www.linkedin.com/in/curtismchale</a><br>
Twitter: <a href="http://twitter.com/curtismchale" target="_blank">twitter.com/curtismchale</a><br>
</font><br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<pre><fieldset></fieldset>
_______________________________________________
theme-reviewers mailing list
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
</blockquote>
</div></div></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br>