[wp-trac] [WordPress Trac] #12718: Better structure for admin $menu

[WordPress Trac]

#12718: Better structure for admin $menu
-------------------------+--------------------------------------------------
 Reporter:  scribu       |       Owner:  scribu         
     Type:  enhancement  |      Status:  accepted       
 Priority:  normal       |   Milestone:  Awaiting Triage
Component:  Plugins      |     Version:                 
 Severity:  normal       |    Keywords:                 
-------------------------+--------------------------------------------------
Changes (by mikeschinkel):

 * cc: mikeschinkel@… (added)


Comment:

 Replying to [comment:9 nacin]:
 > Replying to [comment:8 mikeschinkel]:
 > > cags?
 > It was in reply to http://profiles.wordpress.org/cags - see comment
 above.

 Arghh, those cryptic user names, always tripping me up! ;-)
 >
 > > Also note that I wrote those to be '''100%''' compatible with the
 current structure.
 >
 > That's good. Excellent, in fact. I don't think we'll be looking too far
 ahead (you reference 3.5 for example) but severing plugins from direct
 access is indeed the next step. That said I doubt you'll see a refactoring
 of the underlying storage on a roadmap in the near future, as long as an
 abstraction layer does everything we need it to.

 I was just trying to think through all the angles.  It's not a perfect API
 because, for example when you look at the object in the debugger you don't
 see the menus and because it has to be refreshed, but it's fully
 abstracted.  I guess it would/should be possible to add some functions
 that will build an object structure for those who want to see if via
 `print_r()`, etc.

 Anyway, love feedback on this or to contribute in any way.  I'm itching to
 provide some material contribution to core finally vs. the one line patch
 in v3.0. :)

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