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

Documentation of Application Process for Samsung TV Seller Office #307

Draft
wants to merge 74 commits into
base: master
Choose a base branch
from

Conversation

UgaitzEtxebarria
Copy link

PR to visualize and organize the documentation of the process for Samsung TV Seller Office

@JasperJuergensen
Copy link

Got some time on my hands and was trying out the Tizen Studio Emulator. Created a Pull Request with some content for the language options section (felt like the easiest place to start): UgaitzEtxebarria#1

@UgaitzEtxebarria
Copy link
Author

Thank you very much, I don't have access to the app on tizen, just desktop or web, then every screenshot is welcome

@uxdesignerhector
Copy link

Official Jellifyn Icons and backgrounds for Tizen can be found on this repo https://github.com/jellyfin/jellyfin-ux under the next path https://github.com/jellyfin/jellyfin-ux/tree/master/branding/tizen. I have been looking to it and they are generating them with Inkscape and command line tools so we don't need to recreate them.

They seem to be following rules specified at Samsung's Guide for App icons the only thing we must take into account is that the naming should be logo_jellfyfin_fg.png and logo_jellyfin_bg.png as per official Samsung rules ( see here ), right now those images are named logo_fg.png and logo_bg.png

Here are the routes for foreground and background images:

@J-C-B
Copy link

J-C-B commented Nov 12, 2024

I have added about 30 flows and described screenshots that should be sufficient - happy to add more is needed

@J-C-B
Copy link

J-C-B commented Dec 19, 2024

Hi @anthonylavado - i have made updates a couple of weeks ago - are you able to review? is the application submitted? thanks!

@anthonylavado
Copy link
Member

I'd like to thank everyone involved for their work on this. I am going to push the files to a separate repository to avoid clogging up this one with anything that would need to be ignored/excluded from any development processes.

IMO - it's not a bad idea to move it to a repository like our Jellyfin-meta, as it really is higher level administrative stuff, and only rarely applies. My other projects (work and personal) have slowed down for now, and some work for improving our publishing flows are now complete.

@J-C-B
Copy link

J-C-B commented Jan 1, 2025

I'd like to thank everyone involved for their work on this. I am going to push the files to a separate repository to avoid clogging up this one with anything that would need to be ignored/excluded from any development processes.

IMO - it's not a bad idea to move it to a repository like our Jellyfin-meta, as it really is higher level administrative stuff, and only rarely applies. My other projects (work and personal) have slowed down for now, and some work for improving our publishing flows are now complete.

OK awesome. Appreciate the time you put in too!

I have moved all to docs over the the meta repo - pull request here - jellyfin/jellyfin-meta#84

This pull request can be closed as moved (I dont have perms)

J-C-B added a commit to J-C-B/jellyfin-meta that referenced this pull request Jan 2, 2025
As per suggestions, moved to meta repo to keep app repo clear

ref;
jellyfin/jellyfin-tizen#307 (comment)
@UgaitzEtxebarria
Copy link
Author

@anthonylavado do you make some progress on this?
I think that all the files are migrated to new repo, If you give me your confirmation I will close the PR

@J-C-B
Copy link

J-C-B commented Jan 25, 2025

@anthonylavado do you make some progress on this? I think that all the files are migrated to new repo, If you give me your confirmation I will close the PR

yes its all moved over so this PR can be closed from that perspective - so unless this is handy for tracking i think we can close this one

@Nightcro
Copy link

Nightcro commented Feb 7, 2025

@anthonylavado any update on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants