Roadmap / Feature development status

[sircharlo]

---

Released

See release notes, changelog or issues and discussions labeled implemented

Will be released in the next version

See issues and discussions labeled awaiting-release

In development

See issues and discussions labeled in-progress

To be developed in the future

• Allow for files greater than 512MB to be synced with a congregation, by converting to file streams rather than synchronously loading files in memory

[mtdvlpr]

Hey @sircharlo, I'm currently working on another major refactor. This time it's the migration from Vue/Nuxt/Vuetify v2 to Vue/Nuxt/Vuetify v3. Vue 2 will reach EOL (End Of Life) at the end of this year. Vuetify is still missing some components in v3 that we are using, so we are dependent on their release planning, but it doesn't hurt to prepare, since it's quite some work. You can find it at mtdvlpr/meeting-media-manager/refactor/next if you're curious :)

[mtdvlpr]

@sircharlo, I have completely migrated the codebase to Vue 3. I'm currently busy testing the UI and different features. Feel free to assist whenever you feel like it :)

P.S. Check out the updated CONTRIBUTING.md before you do so.

[sircharlo]

GUI Revamp Roadmap

A revamp of the UI is under way. This comment will track changes as they are completed:

Todo

Congregation selector page

Done

• Allow congregation delete from the congregation selector page
• Show congregation name instead of ID on switcher button
• Hide congregation switcher button when no congregation selected

Media sync and playback page proof-of-concept

Done

• Merge media playback and fetch pages
• Rethink look-and feel of elements on media calendar/playback page
• Differentiate tile if media is present in filesystem for that date
• Look into adding watches for days not in past (if folder created/deleted)
• Show sync progress on individual days
• Implement daily congregation sync
• Show progress for JWPUB fetching
• Show progress on each day for every action and/or download (not just JW sync on meeting days)
• Show progress granular percentage for downloads (increment while downloading, not when file is done downloading)
• Figure out why percent is greater than 100%
• Benchmark streamed copy with progress vs simple copy: not advantageous as of yet
• Fix media order (CBS media shows up before middle song)
• Move syncJWMediaByDate to where it needs to be
• Add "manage media that should repeat at every meeting" button, if recurring media is enabled in settings Will be in settings instead
• Add a "no media! try managing media" message in present view if no media in a date
• Account for CO week
• Make the automatic sync non-blocking, prevent GUI lockup
• Don't start a new auto-sync every time user browses to media calendar, but rather on app load
• Add manual "force resync" button to calendar
• Link the "refresh" button to an actual action in calendar
• Prevent more than one sync at a time (and disable refresh button if sync is ongoing)
• Fix panzoom not resetting on image stop
• Fix panzoom causing scrollbars on media display when image is zoomed
• Automatically go into current day's date folder if it is a meeting day
• Display progress for current day when in that day's present page (in case user is in present page before sync is complete)
• Once in present mode in a particular date, watch for changes (to allow to go to today's date folder while sync is still happening in the background, and also if someone drags/drops media files into media folder using system file explorer)
• Remove "refresh" button from present view, since folder is being watched now
• Watch for modified files, not just new and deleted
• Remove watcher when change page
• Remove files from media list when hidden in cloud sync
• add watcher for hidden files (when file is added to hidden, delete from media folder if exists)
• add watcher for additional files (when file is added to additional, copy to media folder; when removed from additional, remove from media folder if exists)
• add watcher for recurring files (when file is added to recurring, copy to all media folder; when removed from recurring, remove from all media folders)
• Change all watcher delay to something more reasonable (250ms?)
• Clear media store when changing settings or before every sync (for example to prevent issues when sync > disable "exclude th" setting > sync again)
• Fix converted svg width/height issue
• Allow for drag and drop image from web page/email
• Allow for drag and drop straight from present view
  If len = 1 and type = zip: unzip files, return files
  If len = 1 and type = jwpub: select document, return files
  convert unusable files
  if cloudSync: copy all dropped files to dated additional folder (watcher will pick up); else: copy all dropped files to current date folder
• Add jwlplaylist feature to manage media screen
• Add jwlplaylist feature to dragdrop
• Move music and display buttons to navigation drawer bottom
• Show footer only when OBS scenes are visible, hide otherwise
• Allow sorting without toggling; remove toggle
• Change fetchResource for files to return a readable stream, pipe to writeable stream using a new writeStream function
• Create a fetchJson function
• Add a "publication from JW.org" tab to allow downloading publication and extracting media from one of its documents, using cached file when available
• Make sure that media from song, jw video or jw publication actually gets added
• Add a "media updating" notification loading spinner to calendar view when sync is launched
• Remember custom sort
• Add menu item to reset custom sort
• Only show reset custom sort button when sort file exists
• Add a loading spinner to day view if sync for that day is underway
• Test what happens when offline
• Add an "you're offline" banner or snackbar
• Test drag drop local file vs remote file (file path set properly?)
• Add notification/banner if CO week

• Add progress bar to present and manage media pages (while downloading/uploading)
• Fade (transition) files in and out as they're added/removed by file watcher
• Backport audio file vs fade to black change
• Backport MepsDocumentId change

On first run / after congregation creation

Done

• Fix initial load errors when no settings configured yet
• Go to settings screen
• Make a modal proof-of-concept
• Add a friendly "Welcome! Let's configure a few things" message
• Show required fields in the modal, one at a time, with helpful hints and a "next" button that goes to the next required setting
• 1. App display language
• 2. Using at Kingdom Hall?
• 2A. (2Y ? Congregation or group : Profile) name
• 2B. (2Y ? Congregation or group : Media) language
• 2Y ? (Enable second screen, background music)
• 2Y ? Alright! That's enough information to show the yeartext. But lets keep going!
• 3. What are your meeting days and times?
• 4. Where should the prepared media for playback at meetings be saved? (Default: Documents)
• (At this point, start media sync)
• Very well, we'll start fetching media while we wrap up with our initial setup.
• 5. 2Y ? Does your Kingdom Hall use a program called OBS Studio?
• 6. 5Y ? Would you like to integrate M³ with OBS Studio to facilitate sharing media during hybrid meetings?
• 7. 6Y ? Make sure that the OBS Websocket plugin is configured with a password, and that the OBS Studio virtual camera is installed on this computer. When you're sure, click next.
• 8. 6Y ? Enter the port and password for OBS Studio.
• 9. 8Y ? Configure a scene in OBS Studio to show a stage wide shot. Once it is ready, select it here.
• 10. 9Y ? Configure a scene in OBS Studio that captures the external screen. Once it is ready, select it here.
• 11. 2Y ? Make sure that the setting in Zoom to use dual monitors is enabled from now on. That way, you'll be able to quickly show and hide Zoom participants on the TV screens when needed. Give it a try! Click this button to hide the yeartext. (Button)
• 12. 2Y ? That was easy! Once the Zoom part is over, you can show the yeartext again using the same button. Try it again!
• 13. 2Y ? Great! Look for this button in the sidebar. You'll always have quick access to it there.
• 14. 2Y ? The sidebar is where you'll also find the button to start and stop background music playback automatically.
• Congratulations! M³ is ready to be used. Feel free to browse around the other available options, or head right to the media calendar.

• (test OBS connection)
• When last required setting is complete, change two buttons, stay in settings or go to calendar.
• Disable "next" buttons if no choice made

Settings page

Done

• Re-categorize all settings items and display them in a more visually appealing way
• Fix alignment and look-and feel of elements on settings page
• Add "Cloud sync" to integrations with possibility of choosing the cloud sync folder
• Add "Ensure relevant settings are kept in sync" toggle; when enabled, append button to choose which settings will be synced using a json file in cloud sync folder
• Actually lock cloud sync enforced settings
• Add settings dependencies (both for dynamic show and to eliminate needless validation)
• Create an "attention required" banner which will appear only when one or more required fields are empty, or when a field contains an invalid value, with a toggle to show only (or scroll to) those fields
• Only show error fields when present, force subgroup open
• Add keyword filter in settings
• Make keyword filter work for children of parents
• Add "wipe everything" option in settings menu

• Add a button to enable recurring media in cloud sync (disabled by default on new installations; most congregations don't use this and don't need it); when enabled, append a button to manage recurring media (just opens the recurring media folder in system file manager)
• Implement/fix validation, both on change and on app load
• Test various required fields when they have no value
• Try to stop the media window flickering when going into settings
• Fix "no logo" not working with custom bg

Misc

Done

• Attempt to use downloaded font for app navigation headers Not in line with Vuetify design standards, and not worth it
• Refactor findAllStats to be async

[Chipperchap]

To be developed in the future
Allow for files greater than 512MB to be synced with a congregation, by converting to file streams rather than synchronously loading files in memory

This is interesting for me as last weekend we were "forced" to use a pre-recorded talk and the file was edited down to 551mb (removing song and chairman introduction), and I found out that it had to be sent over to the K-Hall PC via cloud rather than just sync from home M³. Not a big issue but I did wonder how often this may occur.

[sircharlo]

In light of the constant connectivity issues with various WebDAV providers, I was wondering if a different approach might be warranted to congregation syncing.

I was thinking of two potential scenarios going forward:

1. Users choose and configure the cloud-syncing solution they want. For example, they set up cloud sync on their computer using Dropbox, Google Drive, or some other software. They would then point M³ to the cloud-synced folder of their choosing on computer A. This folder would become the repository for M³'s congregation sync, where the 'Hidden', 'Recurring' and 'Congregation Media' folders would be saved. On computer B, the same cloud-syncing solution (again for example, Dropbox or Google Drive). Then, they would point M³ on computer B to the equivalent folder configured on computer A.
   This method would remove the need to implement and maintain authentication and cloud-syncing mechanisms in M³. Hiding and adding media would be done by local filesystem write/copy, and the user's cloud-syncing solution would handle uploading those changes to the cloud. Applying the synced changes (such as hiding media) would be done on the fly while syncing media by reading the contents of the cloud-synced folder.
2. We pick a cloud-syncing solution that has a well-supported SDK, and stick to that one. For example, Dropbox provides an official SDK. We implement this SDK and this becomes the only supported method for congregation syncing.

Any thoughts? @mtdvlpr

[mtdvlpr]

I agree! I do think we should provide a deprecation window where the users have x months (or until the next release) to migrate to the new system before we completely remove the WebDAV feature.

[sircharlo]

I agree! I do think we should provide a deprecation window where the users have x months (or until the next release) to migrate to the new system before we completely remove the WebDAV feature.

Wholeheartedly agree. A friendly popup notification to say "hey! this won't work soon; move to new method xyz as soon as possible."
This would need to be done once the 'new' method is ready of course.

[e-Feitosa]

? Bearing in mind that Dropbox has a free 2GB limitation, could that be a problem?

[Chipperchap]

Another factor with Dropbox is that the free version (Basic) is limited to three devices.

[sircharlo]

Considering the fact that the vast majority of congregations worldwide now conduct hybrid meetings, and that the direction outlined in the S-179 par. 10 is therefore no longer current for most, I believe that the "recurring media" feature of M³ should be removed. There is no provision for recurring images, slides, or announcements to be shown at the Kingdom Hall either before or after meetings.

Removing this feature would align us with current direction, and would also simplify M³'s development.

Thoughts? @mtdvlpr

[mtdvlpr]

I'm not sure. Yes, the vast majority will never have to use the feature, but the same goes for the "convert to mp4" feature. I think the support of fully remote meetings should remain (you never know what the future might bring). I would disable the recurring media feature by default and maybe group it with the other settings designed for fully remote meetings.

[sircharlo]

Agreed about disabling by default, Maybe the way to manage recurring media should be moved to the settings (similar to the button to change the background image).

[e-Feitosa]

I liked the idea of keeping the option without being default, it would be optional to activate this feature.

[alanfermtz]

a cool feature that I suggest, its add an full uninstallation checkbox when uninstalling to delete every personal preference applied (even more helpful if we are using alpha for testing)

Is there a new alpha version that I can help try?

[e-Feitosa]

@mtdvlpr, Is there a more updated beta version of the new version available to test?

[mtdvlpr]

hi @e-Feitosa, I've just released a new version and I'll have more time to work on it again, going forward :)

[e-Feitosa]

@mtdvlpr,
Is there a more updated version of the new version available to test?
📅

[sircharlo]

I'll be releasing a new version of MMM soon. I haven't yet decided the exact channel I'll use for this, as this new version is less an upgrade and more a new and reworked app. New and much-improved interface, simplified feature-set.
Stay tuned.

[e-Feitosa]

@sircharlo, We had a renovation in the building and this weekend I will be formatting the computer and reinstalling everything from scratch, if it was possible to make available, I was going to install and use this new application. But if not, I will be attentive when launching and if it is possible to post a note here, thank you very much. Thank you for your excellent work and also thank the support of volunteers in with all contributions in this new application MMM.

[sircharlo]

Hi everyone! Take a look at the new post here for some exciting news about a new version of M³!

[github-actions[bot]]

This discussion has automatically been closed due to inactivity.