[wp-trac] Re: [WordPress Trac] #2654: Why not store dbx states in usermeta?

[WordPress Trac]

#2654: Why not store dbx states in usermeta?
----------------------------+-----------------------------------------------
       Id:  2654            |      Status:  new                     
Component:  Administration  |    Modified:  Tue Apr 11 03:39:01 2006
 Severity:  enhancement     |   Milestone:  2.1                     
 Priority:  normal          |     Version:  2.0.2                   
    Owner:  anonymous       |    Reporter:  skeltoac                
----------------------------+-----------------------------------------------
Comment (by ringmaster):

 You're adding 40+ lines of code and additional client/server ajax calls to
 store per-user open states and positions of the boxes on the Write page
 that work just fine when stored in cookies (if slightly inconvenient for
 people who don't always use the same terminal).  That seems like a reason
 not to include this.

 If you're looking to implement something with Ajax, here's an idea:

 Ditch tw-sack (No error handling/debugging?  Can't handle equals signs as
 passed values with the standard functions?) and build a WP-pluggable ajax
 library.  Move all of the floating PHP functions that respond to the
 various ajax requests into a single file that dispatches those requests to
 plugin hooks.  Include some way to hook client-side events to server-side
 code on-demand so that things like this can be customized by plugins.

 My $2.  Inflation, don't ya know.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/2654>
WordPress Trac <http://wordpress.org/>
WordPress blogging software