chip at chipbennett.net
Mon Mar 12 21:36:13 UTC 2012
The various appearance customizations ARE already in one place: Dashboard
-> Appearance sub-menu. :)
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.
On Mon, Mar 12, 2012 at 4:28 PM, Mats Birch <birch at birchware.se> wrote:
> 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
> I have dug into it, and have some thoughts on the subject. Here goes:
> I don't think it would be beneficial, neither to the user nor the
> developer, to implement add_custom_background().
> The obvious one: All theme options should be in one place.
> The functionality of such a standardized feature could (of course) never
> be versatile enough for all purposes.
> 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.
> So my conclusion is that it would be a waste of time to implement
> Your thoughts?
> (I haven't tried out add_custom_image_header() yet, but I suspect similar
> issues there.)
> theme-reviewers mailing list
> theme-reviewers at lists.**wordpress.org<theme-reviewers at lists.wordpress.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the theme-reviewers