<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Just interested, where the discussion on this matter will take
place? As a theme developer I'd like to express my opinion.<br>
<br>
On 29.05.2011 23:52, Diana K. Cury wrote:
<blockquote cite="mid:008901cc1e42$749f8d30$0100a8c0@corpfe1f3cd943"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta content="MSHTML 6.00.2900.2180" name="GENERATOR">
<style></style>
<div><font face="Tahoma" size="2">Thanks for reply,</font></div>
<div> </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> </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> </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> </div>
<div> </div>
<div>----- Original Message ----- </div>
<blockquote style="padding-right: 0px; padding-left: 5px;
margin-left: 5px; border-left: 2px solid rgb(0, 0, 0);
margin-right: 0px;">
<div style="background: none repeat scroll 0% 0% rgb(228, 228,
228); font: 10pt arial;"><b>From:</b> <a
moz-do-not-send="true" title="chip@chipbennett.net"
href="mailto:chip@chipbennett.net">Chip Bennett</a> </div>
<div style="font: 10pt arial;"><b>To:</b> <a
moz-do-not-send="true"
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
moz-do-not-send="true" 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: 1px solid
rgb(204, 204, 204);">
<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> </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> </div>
<div> </div>
<blockquote style="padding-right: 0px; padding-left:
5px; margin-left: 5px; border-left: 2px solid rgb(0,
0, 0); margin-right: 0px;">
<div class="im">
<div style="font: 10pt arial;">----- Original
Message ----- </div>
<div style="background: none repeat scroll 0% 0%
rgb(228, 228, 228); font: 10pt arial;"><b>From:</b>
<a moz-do-not-send="true"
title="chip@chipbennett.net"
href="mailto:chip@chipbennett.net"
target="_blank">Chip Bennett</a> </div>
<div style="font: 10pt arial;"><b>To:</b> <a
moz-do-not-send="true"
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 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 moz-do-not-send="true"
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: 1px solid rgb(204,
204, 204);">
<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> </div>
<div> </div>
<div> </div>
<blockquote style="padding-right: 0px;
padding-left: 5px; margin-left: 5px;
border-left: 2px solid rgb(0, 0, 0);
margin-right: 0px;">
<div>
<div>
<div style="font: 10pt arial;">-----
Original Message ----- </div>
<div style="background: none
repeat scroll 0% 0% rgb(228,
228, 228); font: 10pt arial;"><b>From:</b>
<a moz-do-not-send="true"
title="chip@chipbennett.net"
href="mailto:chip@chipbennett.net"
target="_blank">Chip Bennett</a>
</div>
<div style="font: 10pt arial;"><b>To:</b>
<a moz-do-not-send="true"
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
moz-do-not-send="true"
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: 1px solid
rgb(204, 204, 204);">
<div bgcolor="#ffffff">
<div>
<div><font face="Tahoma"
size="2">Please,
someone could
clarify </font><a
moz-do-not-send="true"><font
face="Tahoma"
size="2">http://themes.trac.wordpress.org/ticket/4032</font></a></div>
<div> </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> </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;"> </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;"> </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 moz-do-not-send="true"
href="mailto:theme-reviewers@lists.wordpress.org"
target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a moz-do-not-send="true"
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>
<hr>
<div>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a moz-do-not-send="true"
href="mailto:theme-reviewers@lists.wordpress.org"
target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a moz-do-not-send="true"
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</div>
</blockquote>
</div>
<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a moz-do-not-send="true"
href="mailto:theme-reviewers@lists.wordpress.org"
target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a moz-do-not-send="true"
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>
<hr>
<div class="im">
_______________________________________________<br>
theme-reviewers mailing list<br>
<a moz-do-not-send="true"
href="mailto:theme-reviewers@lists.wordpress.org"
target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a moz-do-not-send="true"
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</div>
</blockquote>
</div>
<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a moz-do-not-send="true"
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a moz-do-not-send="true"
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> </p>
<hr> _______________________________________________<br>
theme-reviewers mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a class="moz-txt-link-freetext" href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</blockquote>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
theme-reviewers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a>
<a class="moz-txt-link-freetext" href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
</blockquote>
<br>
</body>
</html>