You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Heyyo! Yes this is a big one and many have asked. very much the next task I will hit up when I have the bandwidth again (soonish I think)
I have some ideas recently for managing collapse/expand that I think would mesh into the existing framework decently.
Basically, any change or RFE that requires changing of the html structure generated causes big problems and requires complicated refactoring in other areas that I am trying to avoid if at all possible.
The complicated way (but possibly the "correct" way) to do this is to maybe integrate a wrapper div for each page group, and then through JS hide/show those divs and their content.
The slightly easier way is to flag certain page names, store them in extension list or table dat for visibility, and simply re generate the UI, omitting parameters that are children of pages flagged as collapsed. This is probably the way I'll go since it will not require any structural changes.
glad to know its a common request! thank you for your insight, the first option seems more performant, mainly because of the redraw glitch that the regen of the second option will probably cause.
I've built a version of this with page and par filtering, and collapses that is kind of clever. let me know if you've got some time coming up to rap about it, its a solid prototype but a bit hacky as i tried to integrate with the way you're doing things here... you'd likely have insight on a better way to implement
would be really neat to be able to double click the header of each page to collapse / expand that page :)
The text was updated successfully, but these errors were encountered: