martinezpl / owlie-yt-addon

Your wise, big-eyed Youtube assistant.

Hiho 👋

• 🔭 Solution Architect at Audiostack
• ⚡ Creator of Owlie
• 📫 How to reach me: LinkedIn

owlie-yt-addon's Issues

improve popup style

Open for discussion.

Recently, on #25, we removed the kofi iframe.

However the new popup feels lacking to me. I would do it a bit more visual with thes changes:

• add copy functionality: when user clicks on the code, or clicks on a copy id button, that is aligned left opposite to the regenerate code. I am not sure if this needs clipboard permissions, it is a point to take into account.
• add tutorial for kofi donations: this could consist on an image with an arrow pointing to the field where the user needs to paste their code into. I would put a button to copy code and another to go to kofi taking up as muych horizontal space as possible.
• remove lock. User should never be able to edit the field. Maybe if they click it, we can also copy it.
• add indicator after the user has copied the field. smt like a popup that lives for a couple seconds

"mockup":

separate server code

After the svelte refactoring, I think it is time to separate the server code to a different repo.

I propose to use Typescript when separating. as it will help us with sticking to a shared interface with the UI.

Thoughts on this?

contributing guidelines

I would love to see a community here :)

However, when contributors start coming, they won't have much onboarding to follow.

I suggest to fill these documents:
https://github.com/martinezpl/owlie-yt-addon/community

Additionally, I would separate the current README.md in two:

• README.md -> explains/showcases the product. Does not go into anything technical in detail. Maybe we can have a 'future ideas'/'current issues' part, but no build instructions
• I would move the rest (dev instructions) to CONTRIBUTING.md

What do you think?

migrate to svelte

I believe this codebase is growing more complex quiclky. I am proposing a refactor of the client-side of the application as soon as possible to mitigate the pain of a later migration.

I propose the use of svelte for two reasons. first, it is getting consistently more popular and loved (see stackoverflow's 2022 survey) and second i just love it personally.

I would start by creating an empty project and try to follow the structure of gitmoji extension

This will allow us to have a global app state (which is useful for things like settings/preferences) and separating the app's functionality into components.

We will also have easier access to the dom properties with svelte syntax sugar

A caveat i can see is targeting youtube's elements. I think it can be done but not much different than the way it is done now