<div dir="ltr">Good point about calling it mobile. I like that...</div><div class="gmail_extra"><br clear="all"><div><i><b></b></i>Christine Rondeau<br>Bluelime Media<br><a href="http://www.bluelimemedia.com" target="_blank">www.bluelimemedia.com</a><br>
twitter: @bluelimemedia<div>skype: bluelimemedia<br><br><br><b><br></b><b><span style="font-size:9.0pt;font-family:"Verdana","sans-serif";color:red"></span></b><b><span style="font-size:9.0pt;font-family:"Verdana","sans-serif";color:black"><br>
</span></b><br><br><i></i><br></div></div>
<br><br><div class="gmail_quote">On Mon, Apr 15, 2013 at 2:11 PM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I wouldn't make it a child theme, as such. If it's a matter of CSS<br>
adjustments and possibly some minor HTML changes, then a checkbox<br>
option somewhere would be better. Something like "Enable Mobile<br>
version" or something like that. I'd even default it to enabled. For<br>
CSS at least, it's a simple matter of then just enqueue-ing the mobile<br>
CSS or not.<br>
<br>
Note, I would avoid using the word "Responsive" in the theme options.<br>
Nobody but designers really knows what that word means (and IMO, most<br>
of them will disagree with each other if you lock them in a room to<br>
fight about it). Real-world people do understand what "mobile" means<br>
though. :)<br>
<span class="HOEnZb"><font color="#888888"><br>
-Otto<br>
</font></span><div class="im HOEnZb"><br>
<br>
<br>
On Mon, Apr 15, 2013 at 3:21 PM, Edward Caissie<br>
<<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>> wrote:<br>
</div><div class="HOEnZb"><div class="h5">> I think I would simplify the idea of add-on versus new to the point of: if<br>
> the theme already has an options page, then add another to make it<br>
> responsive (if you choose to go forward); otherwise, simply create a new<br>
> (Child-)Theme to add the responsiveness. Personally, I would lean towards a<br>
> Child-Theme.<br>
><br>
> Edward Caissie<br>
> aka Cais.<br>
><br>
><br>
> On Mon, Apr 15, 2013 at 4:01 PM, Jose Castaneda <<a href="mailto:jomcastaneda@gmail.com">jomcastaneda@gmail.com</a>><br>
> wrote:<br>
>><br>
>> I'm with Emil on this one. As far as the options you could do a quick<br>
>> conditional to enqueue the responsive stylesheet. That is one method I can<br>
>> think of.<br>
>><br>
>><br>
>> On Mon, Apr 15, 2013 at 12:24 PM, Emil Uzelac <<a href="mailto:emil@uzelac.me">emil@uzelac.me</a>> wrote:<br>
>>><br>
>>> I would add-on vs create an additional Theme.<br>
>>><br>
>>> On Apr 15, 2013 2:12 PM, "Christine Rondeau"<br>
>>> <<a href="mailto:christine@bluelimemedia.com">christine@bluelimemedia.com</a>> wrote:<br>
>>><br>
>>> I've been asked if one of my themes will be converted to responsive<br>
>>> version. I'm wondering what people's thought are about this?<br>
>>><br>
>>> Should I update it to make it responsive or submit a separate responsive<br>
>>> version of the theme?<br>
>>> I have noticed in the forums that some folks would like the option to<br>
>>> turn off the responsiveness.<br>
>>> I guess I could investigate a way to have the responsiveness as an<br>
>>> option.<br>
>>> Has anyone come across a theme that offers an option to have it<br>
>>> responsive or not?<br>
>>><br>
>>> I do know that some themes release a lot of updates while others don't<br>
>>> and that folks will always grumble, but I'm just not sure what the best<br>
>>> practice on this matter.<br>
>>><br>
>>> Any thoughts?<br>
>>><br>
>>> C.<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><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>
>>><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>
>><br>
>><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>
><br>
><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>
_______________________________________________<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>
</div></div></blockquote></div><br></div>