[theme-reviewers] Formal Request for Change of Methodology.

Wed Jun 26 17:31:03 UTC 2013

Again, you are limiting the development of a theme.

Case in point, I have a biography theme I created for a well known actor, 
custom taxonomies post types shortcodes, templates the whole works.  That 
will NOT work with the same effectiveness as a plugin that’s made for 'all' 
themes.   The amount of work required to support all of the different themes 
would be astronomical with the templates alone.

My ComicPress theme the same way, it's completely embedded with options that 
are specific to the code required to run it, while there's an addon 
available in plugin that plugin will only work for the theme.   It's useless 
otherwise.

And there's no "just do away with plugins completely" because in some cases 
like the wp-supercache and things that are developed for all themes those 
are quite useful.  Plugin enhance themes beyond their making.   keywords 
there, beyond their making.

Removing CHOICE is never a good idea.

..then your stuck with cookie cutter themes that have no special qualities 
or features beyond visual...

I do see your point and I disagree with it.

-----Original Message----- 
From: Dane Morgan
Sent: Wednesday, June 26, 2013 10:21 AM
To: theme-reviewers at lists.wordpress.org
Subject: Re: [theme-reviewers] Formal Request for Change of Methodology.

Developers are welcome to make plugins to add features that create content.

And that IS the sticking point.

If themes and plugins are supposed to do the same thing why are we
confusing the issue by having both. Lest just do away with one or the
other and have a free for all.

If themes should just have whatever capabilities the developer cares to
insert, just do away with plugins. Anyone who doesn't want to bother
with the css and html can just grab one at random and stick their code
in it.

On 2013-06-26 12:17, Philip M. Hofer (Frumph) wrote:
> aaaand this accounts for all things that would be construed as 'plugin 
> territory',   Developers should have the option to decide for themselves 
> if they want to make something available to all, or primarily for their 
> theme.
>
>
> -----Original Message----- From: Philip M. Hofer (Frumph)
> Sent: Wednesday, June 26, 2013 10:16 AM
> To: theme-reviewers at lists.wordpress.org
> Subject: Re: [theme-reviewers] Formal Request for Change of Methodology.
>
> If it was warranted, yes.    However, that is not the point. Feature rich
> customizable themes with specific shortcodes dedicated to that theme 
> should
> not be discounted.   Just because the theme has something MORE then the 
> next
> theme should not be the reasoning behind requiring the developer to make 
> it
> available to all.
>
>
>
>
> -----Original Message----- From: Dane Morgan
> Sent: Wednesday, June 26, 2013 10:13 AM
> To: theme-reviewers at lists.wordpress.org
> Subject: Re: [theme-reviewers] Formal Request for Change of Methodology.
>
> But making the cookie look different, the display of the site, is
> precisely what a them is. No one is talking about a 'level playing
> field'.  There is no socialist agenda to drag you down. It is simply
> that a theme should display the content, not create it.
>
> Plugins create any additional content needed, and and can displayed
> differently by simply switching to a new theme.
>
> You seem to feel that HTML and CSS are somehow lesser things that you
> can not stand apart upon.
>
> Have you considered that you might be more fulfilled as a plugin
> developer and let others mess with that all round?
>
> On 2013-06-26 12:05, Philip M. Hofer (Frumph) wrote:
>> I'll provide a different set of logic.
>>
>> Limiting the potential of a theme that has features that no other theme 
>> has is akin to making cookies all in the shape of Santa, but have one in 
>> the shape of a reindeer.    Just because the reindeer is unique they're 
>> all still cookies and taste just as good; one just has a different 
>> feature then the others.
>>
>> This isn't an "Equal Playing Field for all" situation, which is pretty 
>> much how some are looking at it.     While the core components need to be 
>> up to date, pass the theme unit test, not have errors.   The themes 
>> themselves could be as feature rich as the developer wants to have them.
>>
>> Let's take the scenario that all themes must be created equal, not have 
>> features that are only available to it by programming it into the theme. 
>> You might as well just hand someone the back end programming of a theme 
>> and say, here .. change the CSS and HTML to your liking, everything else 
>> is required to be the way it is.    I certainly do not want that.
>>
>>
>>
>> -----Original Message----- From: Dane Morgan
>> Sent: Wednesday, June 26, 2013 9:50 AM
>> To: theme-reviewers at lists.wordpress.org
>> Cc: Philip M. Hofer (Frumph)
>> Subject: Re: [theme-reviewers] Formal Request for Change of Methodology.
>>
>> On 2013-06-26 00:29, Philip M. Hofer (Frumph) wrote:
>>> If they use the theme and use those shortcodes, then that is the theme 
>>> that is using it, to require shortcodes to be cross compatible and in a 
>>> plugin is simply ridiculous.
>>>
>>> The end user, while picking a theme will choose a theme that has 
>>> features that they want.   When they choose another theme that doesn't 
>>> have those previous themes features they miss out, it's not a question 
>>> of requiring a compatibility.
>>
>> it isn't ridiculous in the least. themes should control the appearance
>> of the site, not the content. Short codes create content and should thus
>> be in a plugin so that the user can creat the content and then keep it
>> should they decide they want the page to look differently.
>>
>> Saying otherwise is like saying the guy who soaps the store windows
>> should have control of the inventory. That is what ridiculous looks like.
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers

_______________________________________________
theme-reviewers mailing list
theme-reviewers at lists.wordpress.org
http://lists.wordpress.org/mailman/listinfo/theme-reviewers 