<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I don't think most users have any problem locating "Theme options"
:-)<br>
<br>
A general problem, as I see it, if we widen the view, is that saving
an options page takes too long. Even in the tabbed ones, you have to
save to get to the next tab. That's why I prefer a simple jQuery
approach, one-button-saves-all.<br>
Changing things should be as fast as possible, it's good for the
creativity.<br>
<br>
As for what is is 3.4, I have no idea - "that day, that sorrow", as
the Swedish saying goes..<br>
<br>
<br>
On 2012-03-12 22:36, Chip Bennett wrote:
<blockquote
cite="mid:CAPdLKqcp0eOgb_E5+xPSzvOX0unnzJ+DHi1mGXsgi47uvw6_nQ@mail.gmail.com"
type="cite">The various appearance customizations ARE already in
one place: Dashboard -> Appearance sub-menu. :)
<div><br>
</div>
<div>Further, in WordPress 3.4, they will all be even more in "one
place". Refer to the Project Gandalf UI changes - and,
ultimately, that is part of the primary reason to support the
core implementation: so that users know where to find things
from Theme to Theme, and so that, as the core UI/UX changes,
those changes are propagated consistently from Theme to Theme.</div>
<div><br>
</div>
<div>Chip<br>
<div><br>
<div class="gmail_quote">On Mon, Mar 12, 2012 at 4:28 PM, Mats
Birch <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:birch@birchware.se">birch@birchware.se</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
It has been pointed out to me, during the last review of
my theme, Kippis (ticket 6839, the discussion is in ticket
6834), that I should implement add_custom_background().<br>
<br>
I have dug into it, and have some thoughts on the subject.
Here goes:<br>
<br>
I don't think it would be beneficial, neither to the user
nor the developer, to implement add_custom_background().<br>
<br>
The obvious one: All theme options should be in one place.<br>
<br>
The functionality of such a standardized feature could (of
course) never be versatile enough for all purposes.<br>
<br>
My theme, for example, have an option to toggle the
display (on/off) of the image. It also has a choice of
foreground color. I also plan to implement
scaling/cropping, a small gallery of images to choose
from, and a list of predefined "settings packs", of course
including images.<br>
<br>
So my conclusion is that it would be a waste of time to
implement add_custom_background().<br>
<br>
Your thoughts?<br>
<br>
<br>
(I haven't tried out add_custom_image_header() yet, but I
suspect similar issues there.)<br>
<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>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
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>