|
RE: Update on View Updates
why not give the user the option to choose and integrate both?
This way, weberp can exist in both worlds.
1) Have a system checkbox which decides whether jquery etc will be send. All pages strictly fall back to the current layout if jquery is not transmitted.
2) Each table (only !!!) needs 4 extra html tags: thead /thead tbody /tbody. It is easiest to send those even if jquery is deselected.
Together, the four tags don't create much overhead - it is 30 extra characters for the four tags (30 bytes - not kbytes) for users deciding for higher speed.
Altogether, that is al lthat would be need to be transmitted to those not having the bandwidth. We also transmit data in the tables: rows and columns have content, and that is significantly more than 30 charactrers.
So I think this actually is not a decision between two seperate ways - both worlds can easily be combined without disadvantages for the users not using one or the other.
Some scenarios even bring speed:
Editing inside a table cell can bring speed, because I do not need to transfer the whole table upon every edit. Only the edited cell (e.g. a price) will be posted to the server and will be returrned as acknowledgement that the edit went fine. This substantially saves bandwidth.
For users with fast lines this will bring usage enhancement.
For users on slow lines, it is more difficult to decide: if tables (data) are really big, jquery can actually speed up because more can be done in the browser without loopback to the server.
I know from personal experience - for a long time, we were still on ISDN lines when all Germany already was into DSL. So I well know how one suffers if all webpages are big and need 50s to display in an ISDN line. So having the fast option is a good decision.
But I think the user friendly can be added with very little code that is only transmitted to users selecting it, because jquery can fall back to the current implementation if not transmitted.
Klaus
|
