Why not store dbx states in usermeta?

[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.

[matt]

I think the functionality here is good, maybe we can get it using prototype for 2.2?

[rob1n]

Replying to 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.

I disagree. While it may take a bit of coding, it will make the user's experience better. And seem like magic.

[ajd777]

I like the idea, but I think it is kinda a waste to send a new request for every open/close. It might be a better to save the content of the cookie into the user meta when the page changes and the user meta is accessed.

It really doesn't need to be saved with every open/close because the user won't see the effects of it until the page is loaded again anyway, and if the information is somehow lost, it isn't critical data.

[Nazgul]

Closing as invalid as DBX is gone.