View Single Post
Old 04-08-2013, 07:24 AM   #10
DoctorOhh
US Navy, Retired
DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.
 
DoctorOhh's Avatar
 
Posts: 9,864
Karma: 13806776
Join Date: Feb 2009
Location: North Carolina
Device: Icarus Illumina XL HD, Nexus 7
Quote:
Originally Posted by kovidgoyal View Post
In particular you would be able to use virtual libraries without using restrictions and vice versa. The question really is whether virtual libraries need to have the same set of persistence features as restrictions, namely, specifying a VL at startup, and perhaps for the content server as well.

Certainly, I imagine VL will become the primary way to use search restrictions in calibre. The restrict to dropdown will only be used when an additional level of restriction is needed.
Thanks for the clarification of the concept. This is exactly what I was thinking. Making virtual libraries simple to implement and calling them virtual libraries will be easier to convey, terminology wise, to the masses.

Sounds great!
DoctorOhh is offline   Reply With Quote