desko27 / mediaportal

🎞 🖥 Cast media files into a portal

✨ desko.dev ✨

Hey there. I'm Ismael.
I enjoy coding and ramen.

         



  GitHub        Twitter        Linked In

mediaportal's Issues

Language switcher

Add a simple way to update

Update breaking-changes packages

• react-dropzone@12
• react-router-dom@6
• husky@7

Multiple portals

Better management for events

We need a clearer contract for the events, especially when dealing with them in the renderer process.

• Create enums for each event
• Maybe use this
• Consider building a class for events management, so an instance is "exposed to the main world" and can be used like an API client for events (a bag of known methods)
• Improve preload.js (and add types, although if the previous one is done it will be typed already because of the class)
• Move from window.electron to window.whatever, since the name electron is confusing because it's not actually electron but a custom API that is exposed in window from preload.js
• Add specific types in electron.d.ts for window.whatever (rename to whatever.d.ts too), importing specific event types (from original events file, or from @types) so event listeners provide intellisense in the renderer code (again, if a class instance is registered in preload.js we will only need to load that one to get the right typings)

Lint only staged

Add PostCSS

Migrate to react-i18next

Better directory structure for main and renderer

Action "next" messes up checks when previous uncheckings happened

Dropzone filetype blacklist

Zoom integration

• https://github.com/zoom/videosdk-web
• https://marketplace.zoom.us/docs/sdk/video/web/build/integrate/

Add TypeScript

Update Electron to latest version

A new image under same path+name keeps displaying the old one

This is a browser cache issue. Placing a random hash as a query parameter every time an image set is loaded will solve the issue.

Default background

Reorganize react component directories

The following directories currently contain components:

• components
• routes

Which was fine when the project started. But as the list grows most of them keep being consumed by a single route.

So having a single directory with a structure that resembles the actual react tree would be more understandable.

Except for reusable components like MediaDisplayer which is used in both the portal and controls preview.

Additional portal for a secondary screen

• https://github.com/kristian/displays
• https://github.com/nosolosoftware/win-control
• https://github.com/sentialx/node-window-manager

Use Vite

Specific commands for debugging