@ehelms because in the whole purpose of these widgets is to select a content view within an environment.  So the error would be much more obvious to someone using it, and unlikely to occur in the first place.

Here when grabbing objects for a select input, it makes perfect sense to use Object.query as that's what you want to do.  Because you are not thinking about paging, you're unlikely to think that the data coming back is paged as its a simple select box.  No one is likely to notice (possibly even during testing) that only 25 objects are returned.  So we have an error condition that is easy to arrive at and hard to detect to a dev or qa member.  

I do agree that all the 'query' methods should be changed to be more explicit, i was about to suggest the same exact thing.  I kinda like queryPaged and queryUnpaged,  thoughts @waldenraines.  

Any objections to me changing to this new model for Content views and migrating the rest of the app in another issue?