Last modified: 2012-12-30 20:59:03 UTC
Currently you load 200 files by default. A waste of resources of the user just wants to see the pages categorized. Why loading 200 thumbs without knowing what's the user's intention? Perhaps the user is interested in file 300 to 310 or in file 201. Better: Provide an AJAX-solution that loads contents on demand. Of course there must be a fall-back-system. ---- You don't have a feedback system. That's why I have to use Bugzilla. If I get the impression that you don't care about, I will stop it.
>You don't have a feedback system. That's why I have to use Bugzilla. If I get >the impression that you don't care about, I will stop it. We have a feedback system. Its named "bugzilla" :P Bugzilla is meant both for "bugs" and enhancement/feature requests, so this is the right place. However, bear in mind that there's lots of "requests", so unless you specifically get someone interested in fixing your issue or you provide a concrete reason for how lack of the feature is hurting users (which is hard for most enhancement requests given their nature), there is a good change the bug may sit here without anyone working on it for a long time.
It's not a problem that if this is not processed for a long time. It's just important that it is tracked, so if other people are the same opinion or you run the next usability initiative, it may picked up.
Ah, its always cool to see bugs I've commented on, but don't remember commenting on. Even with ajax magic, one would still want to preload some stuff so that the initial page view has content. But I suppose if paging was quick (with the ajax) one might not load all 200 entries at the initial get go.
