Request for Comment: Have any quality of life change suggestions for the quest log for v11?
Greets, @FVTT ▹ Quest Log users!
I am currently planning small modifications and quality of life changes for Forien's Quest Log for the upcoming Foundry v11 launch. The nice thing is that FQL will continue to be available on Foundry versions 9 - 11 from the same release / codebase. I'll be doing some general housekeeping for this release, but would like to find out if there are any small quality of life enhancements that anyone from the community might have in mind. I'm always keen to implement any good ideas coming from the community.
Planned development for Foundry v11 release:
✓ Convert to legacy Handlebars TRL (TyphonJS Runtime Library) support - allowing:
- Significantly smoother dragging of app windows.
- New "Settings" button on quest log app header bar for built in settings inside main FQL quest log app itself.
- New client setting: hide app header text strings; streamlines app headers w/ icons only.
- Move GM & player macros from compendiums to being located in the in-app settings.
- Add a right click / context menu to hide / unhide objectives in the quest tracker (suggested: @crumb97).
✓ Make default hidden folder visible and remove requirement for quest journal entries to be located in
_fql_quests folder.
- Allows quests journal entries to be visible in the Foundry journal sidebar; allows manual moving into any folder (suggested: @Arkangel).
~ (Maybe) add icon / color for quest status type to documents in sidebar; verify no conflicts w/ MEJ.
✓ Add a new public GM only hook that will show the quest log to all players reliably by socket communication.
✓ Update Spanish translation from Weblate.
----
What are your small quality of life suggestions?
This is also the appropriate time to add more language translations, but FQL already supports 15!
Please do keep in mind that major features are not being considered. I know we all want XP / currency support w/ party split, but that is a major feature.UU
Unknown User•394d ago
TM
TyphonJS (Michael)•394d ago
Thanks @crumb97! Indeed it's easy enough to add a context menu to right clicking on objectives in the quest tracker to hide / unhide them. This is exactly the small quality of life type features that make sense to add! 😄
UU
Unknown User•393d ago
TM
TyphonJS (Michael)•393d ago
This is indeed being tracked and something I'd really like to implement especially expiry and the ability to potentially show visual results automatically when such events occur. However, it is a major new feature as things go and not a small quality of life enhancement.
I am keen on potentially working on a complete next-gen overhaul of the quest log using the modern UI framework I release. Lots of really cool things to implement and external integration for date / time / expiry / result display is certainly one of them. I'll be doing a crowdfunding campaign possibly near the end of the year to try and fund the next-gen quest log effort.
This major enhancement is definitely known about and being tracked:
https://github.com/typhonjs-fvtt/typhonjs-quest-log/issues/146
UU
Unknown User•392d ago
H
holycheeseduck•363d ago
Maybe a way to drag/reorder Subquests around the Quest Objectives list? It can look a little jarring when a Subquest is supposed to happen after a certain point in the quest, but always appears up top
TM
TyphonJS (Michael)•363d ago
That one is just a bit more tricky due to the way the data is currently stored. The write in objectives are stored internally in a separate list than the sub-quests, so in the UI they are being displayed together, but aren't from the same data source which is the explanation for why sub-quests can't be dragged around to re-order them presently and can't be easily intermixed w/ write in objectives.
Unfortunately this is likely going to have to wait until the next-gen / complete overhaul of the quest log in a pretty massive effort implementing all of the tracked enhancement issues https://github.com/typhonjs-fvtt/typhonjs-quest-log/issues. I'll be running a crowd funding campaign at some point as I'd like to free up and work full time+ for 5 months to really make the quest log something special.
H
holycheeseduck•363d ago
Gotchu, but I'm atleast glad that it's on the docket and noted <3
TM
TyphonJS (Michael)•363d ago
I'm definitely aware of it. I'll have to make sure an enhancement issue is filed though. Taking a quick scan through the ones there I'm not sure there is one that specifically addresses it. The next-gen rework of the quest log will be using my high powered modern UI library I've been working on since Oct '21 and there are so many awesome improvements that are possible with it.
H
holycheeseduck•363d ago
Nah it is, just found it actually
C
capn_cat•339d ago
@mleahy I'm running two parties in the same world - a QoL improvement I'd like to see is a 'duplicate' quest button 🙏 Thanks for your hard work!
TM
TyphonJS (Michael)•339d ago
Yeah.. There is an enhancement issue for quest duplication and a lot of other management aspects already being tracked for a "next-gen" rework of the quest log. You can find that particular enhancement issue here: https://github.com/typhonjs-fvtt/typhonjs-quest-log/issues/65; you can read through all of the other enhancements there as well.
Anyway.. I'll be starting a crowdfunding campaign next spring (~March '24) to attempt to raise funds for a full 5 month development cycle to massively improve the quest log working through all current enhancement issues and significantly improving the UI / UX. As things go I can't continue to fund full time development out of my pocket and give things away for free. Hopefully the crowdfunding campaign is successful as I'm looking forward to continuing to wow everyone with a very slick quest log moving forward.
This particular thread was for short term small improvements for the next release. As things go I only had time for the essentials. I'll be looking at implementing the rest from the list in this particular thread for the v12 update in the fall.
All in all though FQL is rock solid / no bugs and will continue to do its thing!
C
capn_cat•339d ago
Thanks for the link! I had a search in here and didnt find it mentioned
Not surprised at all to learn duplication is harder than it looks on face value haha
TM
TyphonJS (Michael)•339d ago
I think it comes hand it hand with a lot of other enhancements along with UX improvements that will be much easier to pull off w/ the next-gen version of the quest log. I've been developing a very modern UI framework full time since Oct '21 that I'll be using; it's available right now for other 3rd party Foundry developers and being put to good use. At this time though FQL is a well oiled machine and any changes come at a potential cost. In any future rework of the quest log I'll be drastically changing around how quest data is stored to better serve some of the advanced feature development. An example of some of the hidden challenges in such a feature though is how to handle duplicating a quest that has sub-quests; specific ownership permissions, etc.
293Members
View on DiscordWant results from more Discord servers?
More PostsQuestion: Modifying class list of SvelteApplicationA question from @dorako:
> so, my module hooks into renderApplication and modifies the html[0].classBlur on moving elementsAfter a few months of being gone, this started showing up for me again. Not sure why.
It seems thatQuest Log: Is there a way to arrange quests within folders or collapsible quest lines?Hi @Arkangel. Apologies it took me a bit to get around to addressing your question. This is a two paCreating a svelte store of a document's flagsIs this wise, if even possible?
Like I want to create a writable store of a message's flags, so thaDropdowns are not mouse-interactable inside ApplicationShellI can't click on the entries created by either Svelecte or svelte-select if that dropdown is inside Welcome to our Foundry VTT package discussion forum!Hello fellow Foundry VTT enthusiasts. This forum channel is for discussing and asking questions abouChat Message Failed to RenderAttempting to load multiple svelte elements into a chat message. So far I was successful, but the moSettings are not a store and Chat Messages TalkI wanted to grab the `TJSGameSettings` stores, but it seems that they are not actual stores? They haSettings PageI was looking at ways to override the default foundry tab for settings and was wondering if there's Release: `svelte-standard` 0.0.23 - "secrets" in editor components respect GM user level.Greets @FVTT ▹ Developer!
Just a small patch note for `svelte-standard` that went out earlier thisRelease: `svelte-standard` 0.0.22 - small fix for new a11y warnings in latest Svelte.Greets @FVTT ▹ Developer. I just pushed out a small update to `svelte-standard` to handle the new a1Core chat sidebar extensionContinuing a discussion with @voodoofrog about a project to extend the core chat sidebar panel.Release: `svelte-standard` 0.0.21 - Svelte sidebar apps refinement (final?)Greets @FVTT ▹ Developer. This update provides what should be the final refinement for `FVTTSidebarCSequencer: Powered by SvelteI've started on the long overdue conversion for sequencer to have its UI powered by Svelte, which alRelease: `svelte-standard` 0.0.20 - More Svelte sidebar appsGreets @FVTT ▹ Developer. Following on the heels of `svelte-standard` 0.0.19 the latest release furtRelease: `svelte-standard` 0.0.19 - Svelte sidebar applicationsGreets @FVTT ▹ Developer. I have put out a patch to `svelte-standard` fixing the ProseMirror librarySidebar Tab ApplicationI have, after diving deep into the Foundry Code, figured out how to actually add new Sidebar tabs.
Svelte error when instantiating a component that wasn't bundled in the same moduleas discussed in the lounge, you can find the load point here: https://github.com/FaeyUmbrea/obs-utilBackspace doesn't work on TJSProseMirror components if content is blank when edit button is clickedThink I found a bug with TJSProseMirror.
When I click the edit button on an editor component with nWhy is this update causing a duplicate Actor sheet to be opened?On my ActorSheetShell.svelte I have a button:
```
<i class="fas fa-lock" on:click="{toggleLock}" />