(2015-06-13, 13:48)Razze Wrote:

(2015-06-13, 12:52)bromix Wrote:

(2015-06-13, 12:13)sphere Wrote: The resolving part is easy. But this needs to be integrated into the repository-system. A plugin needs to register its regular expressions in addon.xml and these expressions need to be in the repositories addons.xml so that it really gets a benefit.

I agree totally with the last part (I think that's what you already posted in your thread of wishes) - love to see that. But I can't quite follow what you mean by 'repository-system'?

What can I do to push this further?

He's saying the repository needs to be aware of it so you/we can show something like "Kodi has received a call from addon X and can't handle this, to resolve this please install one of these addons: [List of Addons that can handel this]"

(2015-06-13, 12:54)Tolriq Wrote: As a reminder lot's of things are not in Kodi or XBMC because solution proposed where not perfect and no one have better solution but nothing was chosen over something that works and fill a need.

As long as the addon system permit this (and it's the case), I do not see why this should not be pushed because maybe one day someone in 3 years will do something at core level.

This.

(2015-06-13, 14:38)sphere Wrote: ...

Exactly.
In addon.xml a plugin should be able to register itself for an url pattern. An add-on repository, like the official one is, is just (more or less) one big .xml which contains all known addon.xml.

If I attend this years devcon, I will try my best to find someone who is able to code this (or someone who explains me what needs to be done and do it myself). Just keep on posting ideas how it can be solved in the best way.

EDIT:

My current best idea is this:

Code:

<addon id="my.cool.addon">
<extension point="xbmc.python.stream_resolver" library="resolver.py">
  <regex>http://www.youtube.com\?v=.*</regex>
</extension>
</addon>

So another extension point with an "library" property to get the script plus one or multiple "regex" nodes containing regular expressions for any kind of urls.

(2015-06-14, 00:19)bromix Wrote: Do we discuss this topic in this thread or should we move?

(2015-06-13, 14:38)sphere Wrote:

(2015-06-13, 13:48)Razze Wrote:

(2015-06-13, 12:52)bromix Wrote: I agree totally with the last part (I think that's what you already posted in your thread of wishes) - love to see that. But I can't quite follow what you mean by 'repository-system'?

What can I do to push this further?

He's saying the repository needs to be aware of it so you/we can show something like "Kodi has received a call from addon X and can't handle this, to resolve this please install one of these addons: [List of Addons that can handel this]"

(2015-06-13, 12:54)Tolriq Wrote: As a reminder lot's of things are not in Kodi or XBMC because solution proposed where not perfect and no one have better solution but nothing was chosen over something that works and fill a need.

As long as the addon system permit this (and it's the case), I do not see why this should not be pushed because maybe one day someone in 3 years will do something at core level.

This.

Exactly.
In addon.xml a plugin should be able to register itself for an url pattern. An add-on repository, like the official one is, is just (more or less) one big .xml which contains all known addon.xml.

If I attend this years devcon, I will try my best to find someone who is able to code this (or someone who explains me what needs to be done and do it myself). Just keep on posting ideas how it can be solved in the best way.

EDIT:

My current best idea is this:

Code:

<addon id="my.cool.addon">
<extension point="xbmc.python.stream_resolver" library="resolver.py">
  <regex>http://www.youtube.com\?v=.*</regex>
</extension>
</addon>

So another extension point with an "library" property to get the script plus one or multiple "regex" nodes containing regular expressions for any kind of urls.

(2015-06-14, 03:09)natethomas Wrote: I think the only reason to make it core would be for speed purposes, which, if that's really a concern or becomes a concern, I think this would make a nice candidate for one of the early binary addons eventually that actually ship with Kodi, since it definitely seems like something that may need a fair amount of updating over time.

edit: With that said, whatever it ends up being, it definitely seems like something that ought to ship with Kodi.

(2015-06-14, 10:07)takoi Wrote: The problem is more that because it itself is a plugin, it has to load every other addon from the file system every time it's opened. That's not something a binary addon would solve. In core you can be kept a routing table in memory so it's not an issue.

Important

(2015-06-14, 12:45)Razze Wrote: On the other hand the resolving of an url to display supported addons might really cause trouble.
You would essentially need to ask the repo for all regexes of every addon and test them against the link we got.

The only way to get around this would be that the sending addons have to declare which format of URLs they are sending. Then we could build up an index when a repo change was done.

But this also removes some of the magic from it

(2015-06-14, 15:36)takoi Wrote:

(2015-06-14, 12:45)Razze Wrote: On the other hand the resolving of an url to display supported addons might really cause trouble.
You would essentially need to ask the repo for all regexes of every addon and test them against the link we got.

The only way to get around this would be that the sending addons have to declare which format of URLs they are sending. Then we could build up an index when a repo change was done.

But this also removes some of the magic from it

We already store addon metadata in a database. Just do the same for the expressions. Checking ~800 addons in memory is nothing

(2015-06-14, 15:36)takoi Wrote:

(2015-06-14, 12:45)Razze Wrote: On the other hand the resolving of an url to display supported addons might really cause trouble.
You would essentially need to ask the repo for all regexes of every addon and test them against the link we got.

The only way to get around this would be that the sending addons have to declare which format of URLs they are sending. Then we could build up an index when a repo change was done.

But this also removes some of the magic from it

We already store addon metadata in a database. Just do the same for the expressions. Checking ~800 addons in memory is nothing

(2015-06-14, 20:06)Razze Wrote: Yes, but that would mean one of two things:
1. You have to download the whole metadata of the whole repo into the clients memory. Keep small machines in mind and also it's likely it will never need 50% of these so we downloaded them just to throw them away.
2. You can do it on the server. Then it's nothing as you said, but if you do the check again and again for every kodi user that asks the repo it adds up to quiet some time of computing wasted.