<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2180" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Tahoma size=2>Thanks for reply,</FONT></DIV>
<DIV><FONT face=Tahoma size=2></FONT> </DIV>
<DIV><FONT face=Tahoma size=2>I'm aware about plugin being better than theme, so
users don't get theme dependent, but I though that plugins should handle very
specific or advanced tasks, not content, I mean...post types is all about
content isn't?! </FONT></DIV>
<DIV><FONT face=Tahoma size=2></FONT> </DIV>
<DIV><FONT face=Tahoma size=2>Thought that a subject/content driven theme could
ok, since there are seasonal themes in repository.</FONT></DIV>
<DIV><FONT face=Tahoma size=2></FONT><FONT face=Tahoma size=2></FONT><FONT
face=Tahoma size=2></FONT> </DIV>
<DIV><FONT face=Tahoma size=2>I don't mind extract it to a plugin, I'm
just upset about spent time on a theme instead a plugin because no one said
that before.</FONT></DIV>
<DIV><FONT face=Tahoma size=2></FONT> </DIV>
<DIV><FONT face=Tahoma size=2></FONT><FONT face=Tahoma
size=2></FONT> </DIV>
<DIV>----- Original Message ----- </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=chip@chipbennett.net href="mailto:chip@chipbennett.net">Chip
Bennett</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Sunday, May 29, 2011 5:22 PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [theme-reviewers] Help on
theme review - Did I waste my time?</DIV>
<DIV><BR></DIV>Of course I can disagree. My opinion is my own, and only I
inform my own opinion. I claim no "authoritarian" viewpoint; I was merely
clarifying a question from a ticket review.
<DIV>
<DIV><BR></DIV>
<DIV>We're right now in the process of thinking out handling of specialized
Themes. It was the major topic of yesterday's meeting. It will be posted as a
discussion topic on the Make site. Nothing is set in stone. Further, nobody
has said anything about removing the possibility of specialized Themes in the
Repository. Part of that implementation is going to be outside of the
control of the Theme Review Team (see also: Child Themes), and I am 100% in
favor of finding all possible means of supporting specialty/niche Themes. The
vast untapped potential of WordPress lies in such Themes.</DIV>
<DIV><BR></DIV>
<DIV>But I will continue to argue the principle of separation of content
*creation* and content *presentation*, and the principle of user content not
being locked-in to any particular Theme.</DIV>
<DIV><BR></DIV>
<DIV>Chip</DIV>
<DIV><BR>
<DIV class=gmail_quote>On Sun, May 29, 2011 at 3:00 PM, Philip M. Hofer
(Frumph) <SPAN dir=ltr><<A
href="mailto:philip@frumph.net">philip@frumph.net</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<DIV bgcolor="#ffffff">
<DIV><FONT face=Arial size=2>Unfortunately I disagree that you "can"
disagree. This is not a position that you have authoritarian viewpoint
over. The "stance" that the theme review team will remove any
possibility of 'specialized' themes on the repository including mine, as
well as any future themes that are contain as such; not withholding themes
like the one that was on the repo for awhile that handled 'trouble tickets'
if you remember that one.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Again, you are limiting the repository again
and this needs to be rethought out a bit more.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV class=im>
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV style="BACKGROUND: #e4e4e4; FONT: 10pt arial"><B>From:</B> <A
title=chip@chipbennett.net href="mailto:chip@chipbennett.net"
target=_blank>Chip Bennett</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A> </DIV></DIV>
<DIV>
<DIV></DIV>
<DIV class=h5>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Sunday, May 29, 2011 12:55
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [theme-reviewers] Help
on theme review - Did I waste my time?</DIV>
<DIV><BR></DIV>I disagree.
<DIV><BR></DIV>
<DIV>There needs to be some assurance that the Plugin will be maintained
for as long as the Theme is maintained, otherwise, the Plugin will simply
be a release-one-and-forget affair. Requiring the Theme to *use* the
Plugin, rather than incorporate the functionality, ensures that users will
have a maintained Plugin, and will retain use/control of their data,
without being locked in to any particular Theme.</DIV>
<DIV><BR></DIV>
<DIV>Chip<BR><BR>
<DIV class=gmail_quote>On Sun, May 29, 2011 at 2:47 PM, Philip M. Hofer
(Frumph) <SPAN dir=ltr><<A href="mailto:philip@frumph.net"
target=_blank>philip@frumph.net</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<DIV bgcolor="#ffffff">
<DIV><FONT face=Arial size=2>A plugin is just an extension of the theme
to allow for usage in multi-variety themes, while content creation that
is specific for an individual theme should be allowed.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>
<DIV></DIV>
<DIV>
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV style="BACKGROUND: #e4e4e4; FONT: 10pt arial"><B>From:</B> <A
title=chip@chipbennett.net href="mailto:chip@chipbennett.net"
target=_blank>Chip Bennett</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Sunday, May 29, 2011 12:42
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [theme-reviewers]
Help on theme review - Did I waste my time?</DIV>
<DIV><BR></DIV>The reason for that review comment is that it is the
current stance of the Theme Review Team that Theme functionality
should involve *presentation* of data only, and that *creation* of
content should be handled by Plugins. User data should not be subject
to Theme "lock-in", but should be available to the user, regardless of
what Theme is used.
<DIV><BR></DIV>
<DIV>The Repository/WordPress are not yet well-suited to handle
"niche" Themes - though we certainly hope that both will
better-accommodate such Themes in the future, given the vast potential
of such Themes.</DIV>
<DIV><BR></DIV>
<DIV>As a compromise, we are currently asking that any Theme that
*creates* data (such as via a Custom Post Type) port that
functionality to a Plugin (approved and available in the Plugin
Repository), and use/integrate the Plugin functionality. This way, if
the user switches Themes, his data are still available, since such
data will be handled by the Plugin.</DIV>
<DIV><BR></DIV>
<DIV>(Note: this requirement means that the Theme should actually be
*dependent* upon the Plugin, rather than making the Plugin itself part
of the Theme. It ensures that the Plugin functionality is kept current
with Theme development, so that users retain access to/control of
their content for as long as the developer maintains the Theme - and
therefore, the Plugin.)</DIV>
<DIV><BR></DIV>
<DIV>In the case of your Theme, porting the CPT functionality to a
Plugin shouldn't be more than a 5-minute (or so) process. Then, you'll
just need to ensure that the Theme checks for the Plugin being active
and/or the CPT being available.</DIV>
<DIV><BR></DIV>
<DIV>Chip<BR><BR>
<DIV class=gmail_quote>On Sun, May 29, 2011 at 1:21 PM, Diana K. Cury
<SPAN dir=ltr><<A href="mailto:dianakac@gmail.com"
target=_blank>dianakac@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<DIV bgcolor="#ffffff">
<DIV>
<DIV><FONT face=Tahoma size=2>Please, someone could clarify
</FONT><A><FONT face=Tahoma
size=2>http://themes.trac.wordpress.org/ticket/4032</FONT></A></DIV>
<DIV><FONT face=Tahoma size=2></FONT> </DIV>
<DIV><FONT face=Tahoma size=2>I'm not undertanding
this:</FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV><EM><FONT face=Tahoma size=2>Even though there are a few
changes to be made I cannot approve this theme because of the
implementation of custom post types which is required to be
implemented as a plugin. (...)</FONT></EM></DIV>
<DIV><FONT face=Tahoma
size=2></FONT> </DIV></BLOCKQUOTE></BLOCKQUOTE>
<DIV dir=ltr style="MARGIN-RIGHT: 0px"><FONT face=Tahoma
size=2>Where, who said that post types should be implemented only as
a plugin, if so, why anyone said me tha before I re-submit the theme
ten times? </FONT></DIV>
<DIV dir=ltr style="MARGIN-RIGHT: 0px"><FONT face=Tahoma
size=2></FONT> </DIV>
<DIV dir=ltr style="MARGIN-RIGHT: 0px"><FONT face=Tahoma
size=2>Also, that stands for a built in plugin or a standalone one
(submit as a plugin in Plugin Directory)?</FONT></DIV>
<DIV dir=ltr style="MARGIN-RIGHT: 0px"><FONT face=Tahoma
size=2></FONT> </DIV>
<DIV dir=ltr style="MARGIN-RIGHT: 0px"><FONT face=Tahoma
size=2>Thanks,</FONT></DIV></DIV></DIV><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></DIV></DIV>
<P></P>
<HR>
<DIV>
<P></P>_______________________________________________<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></DIV>
<P></P></BLOCKQUOTE></DIV><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></DIV></DIV>
<P></P>
<HR>
<DIV class=im>
<P></P>_______________________________________________<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></DIV>
<P></P></BLOCKQUOTE></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></DIV></DIV>
<P>
<HR>
<P></P>_______________________________________________<BR>theme-reviewers
mailing
list<BR>theme-reviewers@lists.wordpress.org<BR>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<BR></BLOCKQUOTE></BODY></HTML>