How are you remembering popup sizing on VL-WEB? Users want their popups to stay the size they like.
Should we use sys_web local storage?
Also, for VL-WIN and VL-WEB, are you remembering when users change the grid column widths? A long time ago there was a grid helper RP that did some cool stuff but that required a line of code in for each grid column. I think it might have been a dingo special.
Thanks for any ideas.
Art
Remember popup position, grid column changes
Remember popup position, grid column changes
Art Tostaine
Re: Remember popup position, grid column changes
As far as I know native VL-Web applications do not remember pop up locations or size, nor the width and order of columns in lists – you’d have to add your own code to do that.
Whether you use local storage or a server-based database table to remember this information depends I guess on whether you want the saved details to follow users from device to device.
Even with local storage I think you’d probably need to consider whether the device is going to be used by multiple users because that would change the composition of the local storage key you use.
Whether you use local storage or a server-based database table to remember this information depends I guess on whether you want the saved details to follow users from device to device.
Even with local storage I think you’d probably need to consider whether the device is going to be used by multiple users because that would change the composition of the local storage key you use.
-
JamesDuignan
- Posts: 85
- Joined: Thu Nov 26, 2015 1:43 pm
Re: Remember popup position, grid column changes
Just to add, it is also important to consider the online/offline capabilities. If it is needed to be used offline as a big proponent of the application, then I would be considering using the local storage in one form or another.
If not, then storing it on the server gives you the versatility aspect of being able to have your settings follow you from Device A to Device B and Browser X and Browser Y.
Regards,
James
If not, then storing it on the server gives you the versatility aspect of being able to have your settings follow you from Device A to Device B and Browser X and Browser Y.
Regards,
James