-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
base: master
Are you sure you want to change the base?
Conversation
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 |
Thank you very much, I don't have access to the app on tizen, just desktop or web, then every screenshot is welcome |
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 Here are the routes for foreground and background images: |
Add guide for Language Options
Screenshots are taken using a web browser using the [demo instance](https://demo.jellyfin.org/stable). They should look more or less the same as on the tv.
Add missing 2015 logo and screenshots to App Information
Added Remote Control mappings
Update README.md
Mark Remoto Control Keys as marked
Update README.md - added gslides for colab
Update README.md - colab for slides
I have added about 30 flows and described screenshots that should be sufficient - happy to add more is needed |
@dmitrylyzo and @anthonylavado - I have created the new screenshots in the TV ui - I am just unclear how to provide them based on the discssion above and dont want to keep re-creating documentation. I looked at the main jellyfin project and they have If we use the wiki feature of github we will still need an images directory hosted somewhere to be able to show the screenshots in the wiki via url in any case. I am happy to help and contribute in the way you would like me to, but would like a solid direction to go in before I spend the time to do it. |
updated screenshots and readme linking
Hi @anthonylavado - i have made updates a couple of weeks ago - are you able to review? is the application submitted? thanks! |
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) |
As per suggestions, moved to meta repo to keep app repo clear ref; jellyfin/jellyfin-tizen#307 (comment)
PR to visualize and organize the documentation of the process for Samsung TV Seller Office