Projects and cases listed per page

Gerhard, others, not sure how to go about applying a patch of an older version of the module to a newer version.

I know we're building in support for Views so that it can handle the display of cases, but this is probably a good addition nonetheless.

It'd be great to get these things in.

I'm not sure the use case for this - care to explain? This seems like an "easy" feature, sure, but why is it absolutely necessary for it to clutter up the settings page? Marking "won't fix" unless I get a decent reason. (Equivalency test: why isn't there a matching "Number of watchdog entries to show per page" or "Number of taxonomy terms to show per page"?)

Cases are "user-side" content unlike logs or taxonomy -- it's important to be able to specify e.g. whether 10 or 50 cases show per page.

Anyways, can't Views handle this completely?

But why is it important? We don't allow users to decide how many nodes per page in, say, taxonomy term listings or the front page.

Drupal does in fact allow one to set how many nodes for the front page (/admin/content/node-settings in dev).

Seems Views does all this anyways, so moot point?

Ok, fine, but I'm still searching for its "importance" - convince me why we should do this - what's the use case? Adding settings just because it's a few lines of code isn't a powerful enough motivation, nor am I entirely convinced that the equivalent you've posted is accurate (one is node content which doesn't have headers, and another is tablular content where the header row is important for visual and categorical information - losing that header because of a page scroll is bad usability). Anyways, no, I don't think Views is an equivalent to the new case page - the new case page is HuUUGely powerful with the new filter system I added (see the README.txt). It'd be quite difficult to reproduce that in Views.