SUGG: Background Loading/Optimization
I'm not sure if this has been suggested in the past, but I suggest that Logos employ background loading. For example, the population of the parallel resources seems to be extremely long. It would be quicker if Logos populated this information for the windows that are open in the background and had it ready for your request when you needed it instead of populating the information when you requested it.
Also, this would be great for the Home page.
Comments
-
[Y]
Something like that is definitely needed.
Dave
===Windows 11 & Android 13
0 -
+1 [Y] Great minds think alike. I was just thinking earlier today of making this suggestion, and hadn't read your post yet.
Also some caching is needed. Once that list is populated, it doesn't need to be repopulated every time you drop it down. But I see the dreaded "No parallel resources" again every time I scroll just a few verses in the current resource. Couldn't there be some rule that only if you change testaments (or at least books) in your scroll does it need to be repopulated? Or am I not thinking of some scenarios where the list might be incorrect if you simply scroll a little way within the current book of the Bible?
0 -
Rosie Perera said:
Also some caching is needed.
My head was spinning with Suggestion vs Implementation and I decided not to mention caching!
Rosie Perera said:Or am I not thinking of some scenarios where the list might be incorrect if you simply scroll a little way within the current book of the Bible?
If a bible is linked to a commentary set then the PRS of the commentary could change within a book eg. Is 39 to 40 in NAC.
Dave
===Windows 11 & Android 13
0 -
Rosie Perera said:
Also some caching is needed. Once that list is populated, it doesn't need to be repopulated every time you drop it down.
I had previously suggested this and it was already a case in our database. Not all parallel resource sets are the same after switching to a different resource - so only certain ones could be cached. I will link to this thread in that case, thanks.
0 -
OR . . .
Maybe - unnecessary graphics - could be removed (or in some cases reduced) from certain areas of the program, like drop-down menu's and the Library pop-ups, etc.
There are certain areas in the program that do not need to have all the flashy graphics, the Library pop-ups and drop-down menu's come to mind first.
Removing or reducing unnecessary graphics in a few areas would go a long way toward speeding up performance because Logos wouldn't have to continually keep loading all those little images. And besides, they're unnecessary in those areas. Who needs all those little pictures in the Parallel Resources drop-down? Why are they there?
We could do without them in places like that.
Just a thought.
0 -
OR . . .
Put them on the users hard drive and have them cached there so that they load almost instantaneously.
Just another thought.
0
