new feature

6 posts / 0 new
Last post
1alfaebooksp
1alfaebooksp's picture
new feature

would it be possible for us to set a "hidden" flag and have a button to show "Unhidden/hidden/All"

thanks

admin
admin's picture

Please let us know why do you want to hide books?

stupidaccountse...
stupidaccountsecurityyournotthensa's picture

[quote=admin]Please let us know why do you want to hide books?[/quote]

in the same way that you have already decided it would be a good thing to hide books without covers etc (as per most of your query statements) there would be many reasons for hiding books ...or at least not having them in the view and query. It seems that you are not intending to include the NOT operator in future versions which would be so much better especially with tags, so a simple preformatted method (like your search without covers) of user flagging an item and then seeing the subset would be important to me. I have lots of books and documents that are just too obscure to be required on a daily basis. oh and what about all that PORN that we would't want the kids to see ;-)

having said that now...I wonder if you are going to suggest yet again creating a new database. It occurs to me that this could be your default solution for most things. - Although you have built in the ' no covers' and the like queries which of course could have been put into another database too! But you may be right. I need to get my head around keep making new databases with varying content and then loading those when needed. It all sound like hard work though, (better to have a NOT statement in the query) but then there may be technical reasons why NOT is problematic. Certainly the listing without moving/copying the file aspect of alfa is more appealing to me than calibre's method but it seems that a lot of organisation is required with alfa and that may be too much for me.

admin
admin's picture

We put the NOT operator into our To-Do list for next versions
But it seems that if you don't want to see some books - it's better to delete them or put to another place (database). Because the more books you have in the database - the slower is performance. And if the program would check every book To-Hide-Or-Not-To-Hide every time - the performance will be much more slower

1alfaebooksp
1alfaebooksp's picture

sure.. that makes sense. It's a very different way of working but I'm sure I'll get the hang of it.

Mr Reese
Mr Reese's picture

[quote=admin]We put the NOT operator into our To-Do list for next versions[/quote]
Thank you!