- This topic has 6 replies, 4 voices, and was last updated 10 years, 9 months ago by
.
-
Posts
-
Weaver Xtreme Version 2.0 has been released on our site, and will soon be available from the WordPress.org repository.
I’ve just posted a somewhat detailed commentary on the conversion process to the Customizer that might be of some interest.
http://weavertheme.com/wordpress-customizer-supporting-600-theme-options/
Nice write-up, hopefully the WP core developers will respond positively to the suggestions for future improvement.For me the time required to entered the customizer is still a major drawback, and makes it only suitable in the initial design phase when needing to tweak colors, fonts and layout.But any further editing that needs back and forth between the WP options/posts/pages and the Customizer is way too slow, and the legacy interface remains the only productive way to work.Hopefully WP core developers will take to heart to fix that issue and find a way to open the customizer within a second or two on any browser / computer.I think the problem right now is that they try to process the entire customizer option structure before opening, when in fact they could just load the various levels as they are being used. Caching could also help optimize the re-openings of the customizer once it has been opened once.All in All, Congratulations ! this is a move in the right direction, WYSIWYG is the way of the future 🙂Don’t know if you’ve loaded WP 4.4 yet, but the difference of the preview refresh is quite significant.
And once the Customizer interface itself is loaded, there is no particular reason to close it as long as are doing any development. If you need to open other dashboard menus to edit posts or whatever, just do that in a new browser tab. I guess that might be another use case for adding a review window refresh button.” If you need to open other dashboard menus to edit posts or whatever, just do that in a new browser tab”My experience with opening and saving from several browser tabs on WordPress settings is a high risk of a disaster in settings saving, but may be it is safe between the customizer and everything else….I’ll give it a try though 🙂But regardless, they will need to fix that loading time for the customizer to have a chance as being the primary editing toolI guess the point is you should only have one browser tab open for WordPress settings (if you are developing), and another one for page/post edits, and never the twain shall meet 🙂
A very interesting read, although I had been dabbling with the beta releases and could see the potential of the customiser interface I hadn’t really given it a great deal of thought, however this write up has really made me think about the level of effort required to develop the theme to V2. Great work!
- You must be logged in to reply to this topic.