[wp-trac] [WordPress Trac] #18693: New feature pointers

[WordPress Trac]

#18693: New feature pointers
------------------------------------+--------------------------
 Reporter:  jane                    |       Owner:  koopersmith
     Type:  task (blessed)          |      Status:  new
 Priority:  normal                  |   Milestone:  3.3
Component:  UI                      |     Version:  3.3
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |
------------------------------------+--------------------------

Comment (by WraithKenny):

 A suggestion based on Nacin's patch:

 Instead of `dismissed_wp_pointers` wp should store the pointers left to
 queue: `queued_wp_pointers`. Core, Plugins, and Themes should
 register/enqueue once per pointer, say on activation, upgrade, on user
 input (as in "show me the walk-thru" btns), or via callback in case of
 series. user_meta will keep the pointer data until it's displayed and
 dismissed at which time it'll be deleted (via ajax like in Nacin's patch).
 (Alternatively, they can be deleted on shutdown during the run in which
 they were displayed. Function argument to chose?)

 This has the benefit of having one array of data stored in user_meta and
 after all pointers have been shown to the user, that array would be empty.
 Also, it'd require only one get_user_meta for all code using pointers,
 called by one core function that also handles the scripts/css. Pointer
 data can be organized by screen name (or whatever current page is called)
 and/or plugin slug (for multiple pointer on same screen from different
 sources) and contain a callback reference (called when dismissed) so that
 series of pointers on subsequent pages can be handled in that way.

 As for a series of consecutive pointers on a single page load, I like
 GuidedTour as a name :) Perhaps the class implementation can wrap a group
 of pointers to be stored in a single slot in `queued_wp_pointers` array
 and whatever output function can check for a flag.

 Just some midnight ideas...

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/18693#comment:36>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software