APY
Session-distinct Grids
Something to consider for this version or 3.0. I have users who often open many tabs of the same grid. We manage grid state exclusively in the session, which means that although multiple tabs are open, only one filtered state is available for all of the tabs. Can be confusing.
I agree but how do you suggest that ? how do you know which filter is for each tab ?
Cookie ? ( https://github.com/chrisdew/subsession ) localStorage HTML5 SessionStorage ? (Data stored using sessionStorage do not persist across browser tabs, even if two tabs both contain webpages from the same domain origin. In other words, data inside sessionStorage is confined to not just the domain and directory of the invoking page, but the browser tab in which the page is contained in.)
If we can do that, we can have three states of persistence. (false, session, tab) It could be great.
I was thinking about keeping it simple and adding some kind of key to the url. For example:
/app_dev.php/usersgrid/?abc123
/app_dev.php/usersgrid/?abc456
Each url above would have a distinct grid state.
If we went with this approach, it's probably something we would want users to be able to turn on/off. Some will want distinct grid states, some will want "clean" urls. That said, if I was using the Ajax grids then the above approach would work and I'd still get clean urls.
Hadn't thought about HTML5 SessionStorage. Might be the way to go if it's not overkill.
I think only cookie can perform this task. Html 5 storage is local and isn't compatible with all browsers.
+1 @alibahsisoglu I need filters and sorting parameters in query string, I need this to make a shareable (between users) grids with pre-setted filter values and column orders.
@Abhoryo news?
