Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Disable unwanted features #16

Open
EvantheGrump opened this issue Jul 21, 2024 · 2 comments
Open

[Feature Request] Disable unwanted features #16

EvantheGrump opened this issue Jul 21, 2024 · 2 comments
Labels
priority: low this issue only has minor effects - adressing it is not immediately required status: investigating this issue is not easily reproducible or fixable, the cause is being investigated type: enhancement this issue requests additions or enhancements to the codebase

Comments

@EvantheGrump
Copy link

I think the ability to disable certain features of a book would help users be able to create more specialized or varied books.

Perhaps features such as:

  • Bookmarks
  • the Search Bar
  • the Index

could be disabled.

@gliscowo
Copy link
Member

Could you elaborate a bit on when exactly this would be appropriate? All of the features you mentioned exist to make books easier to browse for players - I'm having a hard time seeing why you would want to make your book actively difficult to use

Cheers

@gliscowo gliscowo added type: enhancement this issue requests additions or enhancements to the codebase priority: low this issue only has minor effects - adressing it is not immediately required status: investigating this issue is not easily reproducible or fixable, the cause is being investigated labels Jul 21, 2024
@EvantheGrump
Copy link
Author

Sure, I'll illustrate some potential use cases. My first idea, and the reason I suggested this, is the ability to create single page books. I wanted a way to display images and crafting recipes in a simple way, and in this book, there would be no need for the search bar, index, or bookmarks for obvious reasons. Another use case I can imagine is in a "realistic" setting, where there is a desire to create a book that supports images and crafting recipes, but without additional convenience features for the sake of a sort of realism. I can understand that these are edge-case uses, but I figured adding more modularity to a data-driven project such as this would always be appreciated. However, I also understand that this might require a substantial re-programming, and completely understand if this is one of the reasons you choose not to investigate this feature any further.

Thanks for hearing me out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low this issue only has minor effects - adressing it is not immediately required status: investigating this issue is not easily reproducible or fixable, the cause is being investigated type: enhancement this issue requests additions or enhancements to the codebase
Projects
None yet
Development

No branches or pull requests

2 participants