WordPress.org

Make WordPress Core

Changes between Initial Version and Version 7 of Ticket #33507


Ignore:
Timestamp:
09/16/2015 10:46:23 PM (4 years ago)
Author:
westonruter
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #33507

    • Property Owner set to westonruter
    • Property Status changed from new to accepted
    • Property Summary changed from Revamp widgets to be JS-driven to Allow widget controls to be JS-driven
  • Ticket #33507 – Description

    initial v7  
    2323While the above focuses specifically on making the `WP_Widget::form()` and `WP_Widget::update()` both JS-driven, there may also be an opportunity to allow widgets to opt-in to JS-driven rendering of a given widget (i.e. implementing `WP_Widget::widget()`, in JS). This would make a lot of sense if the widget defined its template in Mustache (or Twig) and then allowed the instance array to be applied to that template either server-side or client-side. The effect for client-side would be postMessage instant previews of changes to widgets in the Customizer. The PHP-driven performant alternative to this would be partial-refresh as outlined in #27355.
    2424
     25By using JS-driven widgets, we will be able to use control templates for the widget controls as opposed to having to include a separate copy of the widget form with each control's params. This can drastically reduce the page weight, since the control template only needs to be included once.
     26
    2527By implementing JS-driven widget controls, the user experience of managing widgets would be vastly improved and the server load would be greatly reduced.