-
Notifications
You must be signed in to change notification settings - Fork 455
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
[plugin.video.invidious] 0.2.2+nexus.0 #4363
[plugin.video.invidious] 0.2.2+nexus.0 #4363
Conversation
5e43115
to
fcd559c
Compare
@petterreinholdtsen there is a typo in the PR title |
fcd559c
to
edcb4c5
Compare
[Ramiro Morales]
@petterreinholdtsen there is a typo in the PR title `invidoius` ->
`invidious`
Thanks. Fixed there and in the commit.
…--
Happy hacking
Petter Reinholdtsen
|
edcb4c5
to
0f59f89
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your submission, please address the issues and we can proceed.
@@ -0,0 +1,4 @@ | |||
# Update translations when the english master changes | |||
|
|||
update-po: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove this file from the PR request.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No problem. Why do you want to hide the recipe on how to update the translations, build a distribution zip and make releases?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you want to hide the recipe on how to update the translations, build a distribution zip and make releases?
I guess they have their own way to do releases.
I always branch out and create PRs from the branch, and keep my own potential none desired custom scripts to my own master branch.
(Btw, I was the origin for the Makefile. I use it for maintaning addon releases in my own kodi repo.)
fc0e9fb
to
9210762
Compare
Thank you for trying to help me here. :)
[Lunatixz]
Google is your friend :) Please resize to 1080p.
https://i0.wp.com/datahorde.org/wp-content/uploads/2020/09/Invidious-Logo.png
What do you mean? It is already 1080 pixels wide:
% file resources/fanart.png
resources/fanart.png: PNG image data, 1080 x 540, 8-bit/color RGB, non-interlaced
%
If you don't understand the new API there are topics on the Kodi
forums to help; ie. your lack of understanding != broken API.
Good. Is how to use the new API documented outside comments and
fragments in the forum, ie some consistent instructions by someone who
know the new API? I have trawled the forum trying to figure out how to
use it without any luck so far. I only find code fragments that do not
work when I test it, and have no idea if it is because something changed
within Kodi or the forum posts are just wrong.
The wrapper is there to offer backward/forward compatibility... in
your case since you are only familiar with setinfo, its a bridge to
the new API. If you don't understand the new API there are topics on
the Kodi forums to help; ie. your lack of understanding != broken
API. The wrapper is there to offer backward/forward compatibility...
in your case since you are only familiar with setinfo, its a bridge to
the new API.
I am not really familiar with any of them, so it is no loss for me to
switch to a newer API, if I can find a howto or explanation on how to
use it.
The readme attached to the infotagger project has excellent examples.
As you can see from my comment earlier, the excellent infotagger
examples did not work for me, and I fail to understand why. The
addon.xml dependency statement to depend on infotagger just made my
addon uninstallable. I expected a repository including infotagger to be
available in the default kodi setup for kodi 20. Is this wrong?
…--
Happy hacking,
Petter Reinholdtsen
|
@petterreinholdtsen Lets start with your addon.xml... below is how it should appear on your end.... Make sure you have the dependency installed to Kodi (its available in the official repository).
add below to invidious_plugin.py at lines below change
|
[Lunatixz]
@petterreinholdtsen Lets start with your addon.xml... below is how it
should appear on your end.... Make sure you have the dependency
installed to Kodi (its available in the official repository).
Thank you. I gave this a go using version 0.0.5, but the dependency was
not installed by Kodi when I tried to install the addon zip file using
the 'Instal from zip file' menu option in the add-on browser menu. Kodi
refused to install my new addon version because its dependency are
missing. What do you mean by 'make sure you have the dependency
installed'? For other addons the required dependency have been
installed automatically by Kodi, as far as I remember. Is this not the
case for infotagger? Am I missing some official repository in my
LibreELEC installation?
add below to invidious_plugin.py
Seem to be correct to me. My edition is still available from
<URL: https://github.com/petterreinholdtsen/kodi-invidious-plugin/tree/obsolete-setInfo >
…--
Happy hacking
Petter Reinholdtsen
|
I'm not sure why the dependency isn't installing... its live in the repo: http://mirrors.kodi.tv/stats?downloadstats&filter=script.module.infotagger I would manually download infotaggers zip and install it... |
9210762
to
063620c
Compare
[Lunatixz]
I would manually download infotaggers zip and install it...
Thank you for your patience. This brought me along a path where I
finally got it working. In the end it was an embarrasing
misconfiguration on my part. Do not ask. :)
A new release without the obsolete setInfo() calls are now available for
your review. :)
…--
Happy hacking
Petter Reinholdtsen
|
@petterreinholdtsen Great, glad you worked it out... only one issue remaining. The fanart is not 1920x1080, |
[Lunatixz]
@petterreinholdtsen Great, glad you worked it out... only one issue
remaining. The fanart is not 1080x1920,
I am on it. I assume 1080x1920 is a typo, and you ment 1920x1080.
`ERROR: fanart should have either 1280x720 or 1920x1080 or 3840x2160
but it has 1080x540`
Can the fanart be SVG, or must it be a PNG bitmap?
…--
Happy hacking
Petter Reinholdtsen
|
png or jpg. |
A privacy-friendly way of watching YouTube content. Uses the great Invidious web service's API to do the heavy lifting. Nexus repository release from new repository.
063620c
to
b66ba17
Compare
I mocked up a fanart.png in inkscape. Hope it is acceptable. I did not
include the original .svg, assuming it is as unwelcome as the makefiles
and will only keep it in the upstream git repo for how.
…--
Happy hacking
Petter Reinholdtsen
|
Is there anything more for me to do to get this into wider distribution? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
A privacy-friendly way of watching YouTube content. Uses the great Invidious web service's API to do the heavy lifting.
Third nexus repository release from new repository.
Checklist: