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

Use Resources as Glossary Entry Template #2219

Open
CakeVR opened this issue May 7, 2024 · 1 comment
Open

Use Resources as Glossary Entry Template #2219

CakeVR opened this issue May 7, 2024 · 1 comment
Labels
Enhance ⚡ Improve a feature's workflow. Feature✨

Comments

@CakeVR
Copy link
Collaborator

CakeVR commented May 7, 2024

Allow the user to define a resource to use for Glossary's entries instead of strictly defining what the Glossary entry looks like.

@CakeVR CakeVR added Feature✨ Enhance ⚡ Improve a feature's workflow. labels May 7, 2024
@CakeVR CakeVR added this to the Version 2.0 (beta) milestone May 7, 2024
@CakeVR CakeVR changed the title Add Custom Entries to the Glossary Use Resources as Glossary Entry Template May 7, 2024
@Pheubel
Copy link
Contributor

Pheubel commented Jun 7, 2024

This definitely sounds interesting, as you could then make a glossary that has a short form that will show up in dialogue, but a more complete description that can be used in a lore section for the visual novel.

Would this also mean that the glossary entries themselves could be stored outside of the glossary? Perhaps the role of the glossary is a bit too large and it could be broken up, like how in godot 4.3 the TileMap node, which contains layers has been superseded by TileMapLayers instead that you can control separately. Although it would add a little bit of project bloat and makes creating new entries a little bit more involved, i think it might make the entries easier to work with outside the context of dialogic.

I am not too sure how exactly it would be implemented, but here are some options i've come up with so far;

  • Folders act as a category (the root to the glossaries directory would most likely have to be saved in the project settings for that) and glossary entry resources inside that directory would automatically be added to that category. Adding and removing to entries can be pretty quick, but can be easy to mess up and have unrelated files in the directories.
  • The glossary would hold references to glossary entry files. With this approach glossary entries can be part of multiple categories.

As for how the entries would be visualized inside of the editor, i think that a system close to how timeline events are visualized could help out to make it easily modifiable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhance ⚡ Improve a feature's workflow. Feature✨
Projects
None yet
Development

No branches or pull requests

2 participants