|
So I got this scenario where I have like 4000+ objects which can all be linked to the 3999+ other objects.
One lookup containing 4000 objects (needs to be paged or whatever).
One table containing 3999 objects minus the ones that are already linked (needs to be paged).
Another table containing 3999 objects minus the ones that aren't linked yet (needs to be paged).
The problem isn't getting the data from the back-end to the front-end, I've optimized the sh*t out of that (it's probably even faster than doing additional round-trips).
The problem also isn't that so much data makes everything unclear to users, paging will only make it less clear I think.
The processing of the data on the front-end is pretty simple, so that's also not the bottleneck.
The only problem is that a browser can't render so much data in under ten seconds, which is pretty detrimental to the user experience 
So I've got all this data in the front-end and now I'm going to write the necessary JavaScript to only show about a 40th of it at a time 
|
|
|
|
|
Perfect application for the (new) FrammusJS framework. 
User: Technical term used by developers. See Idiot.
|
|
|
|
|
That doesn't exist, according to Google (and that's final).
|
|
|
|
|
Blame the browser. Isn't that lesson one of web development?
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
The first rule of web development is: Always blame the browser.
The second rule of web development is: ALWAYS blame the browser.
|
|
|
|
|
Actually rule 1 is
1) Blame the browser.
2)If it's not the browser, then see rule 1.
CQ de W5ALT
Walt Fair, Jr., P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
|
Can't remember seeing that when I grew up 
|
|
|
|
|
I know, I'm stick-old 
|
|
|
|
|
|
Yes, I'm a bit of a Dino I know, but to my defense I can say that I never programmed in Cobol
|
|
|
|
|
Don't know about your scenario, but how about an master-detail (vertical split screen) endless list (loading more data dynamically when needed/visible) combined with some filtering to easy the pain to begin with?
In order to understand stack overflow, you must first understand stack overflow.
|
|
|
|
|
The trouble with the endless list is that the items can be modified, so you certainly want some filtering, and you need to be able to "remember" edits even when the data is unloaded.
Luckily, my list isn't endless though
|
|
|
|
|
If you show 100 items on the page then that is 40 pages.
Perhaps not out of bounds but certainly close. If you presume that the data will grow at all then your current scheme will not work.
You need to use real paging. Only return 20/100 items, not 4000.
Sander Rossel wrote: browser can't render so much data in under ten seconds
Yep, so that is why you need to really page it.
|
|
|
|
|
The data won't grow all that much, so my current scheme will work at least for the years to come.
I've currently got 8000 items and it still performs really well (except for a lookup, which takes a second to open).
I've found a select module that will handle a lot of the work for me, so I might do this the "will-scale-up-to-infinity" way after all.
That will pose new difficulties, like you're trying to edit data that's not actually loaded yet and may unload when a new page is selected.
Man, I hate paging and the additional work that comes with it 
|
|
|
|
|
Sander Rossel wrote: I've currently got 8000 items and it still performs really well
I seriously doubt that it works "really well" for the users that actually need to use the page.
They presumably need to find something on that page and they know what they are looking for. So rather than tell you so you can return just that they must manually scan those 8000 items, one average of course probably at least 4000 lines, to find it.
|
|
|
|
|
... but "WOW!" anyway: Hercules A[^]
It's a composite of visible light from Hubble (the central galaxy, over 1000 times more massive than the Milky Way) and radio data from VLA - the plasma jets are over 1,000,000 light years long.
Hercules A - Wikipedia[^]
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
A beginners guide: Welcome To The Tutorial[^] - and judging by many of those I've seen recently in the moderation queue, it's working!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Or we can just point to this CP[^] link.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
I'm not sure if I should take that as a complement or an insult!
So ... do I have to fetch the epees and slap your face with my glove? (Warning: it's pretty solid and has kevlar knuckles)
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I didn't get the question. Must be some cultural thing. But you can take it as a compliment.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
|
Yes, injections are good, especially for the hurt and wounded
|
|
|
|
|
@OriginalGriff has been involved in a fight and won't be able to attend to his CP duties today sadly ...
|
|
|
|
|
Oh, I'm sorry to hear that! Was I badly injured? Did the other guy have a knife?
Where am I? If I'm in hospital, I'd probably like to go and visit me ...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
