Idea: Port LogoManager into common library and use it inside MP2-Server plugin (1 Viewer)

[Hawkeye]

Can't you have a provider for the internal logo mamaher wjich hets its logos from tve?

Then you would have to install the TVE if you want logos for e.g. WebRadio - even if you won't wanna watch tv, wouldn't you?

 

[mm1352000]

And you don't accept other usage requirements like the mentioned WebRadio that also needs logos and processing?

Sure, I do. I just have a different opinion about who is responsible for providing/integrating the service.
If logo management is a necessary function for WebRadio then I'd expect the plugin to integrate it, just like TVE would have to. Yes, there could be a point where it would make sense for MP2 to integrate it directly - for example, if 50% of plugins needed the function (eg. fanart).

 

[mm1352000]

Then you would have to install the TVE if you want logos for e.g. WebRadio - even if you won't wanna watch tv, wouldn't you?

It cuts both ways. Integrating logos with TVE makes TVE integration with another frontend (eg. XBMC, Plex, Mediabrowser... whatever) easier. Further, the behaviour and configuration would be consistent across frontends that share the backend/server/engine.

To directly answer your question: no. WebRadio would integrate support for themselves. WebRadio and TVE are completely independent.

 

[Hawkeye]

To directly answer your question: no. WebRadio would integrate support for themselves. WebRadio and TVE are completely independent.

I was just referring to the post of @FreakyJ... In my opinion it would be ok if there is a general way of getting the logos (which would be this WebService, right?) and every plugin (TVE, WebRadio and so on) would access it on its needs. But there should probably be a common destination the logos are stored to, so you don't have to download/recreate them if they are already there from another plugin...

 

[offbyone]

The components are (correct if I am wrong):

• A Webservice/-site providing the logos (and upload + management) and it is hosted on a remote Server
• A processing library that can retrieve and modify a logo with certain image functions to make it fit better to a user'S skin and liking
  This is a shared component that can be used by any application that wants to have tv/radio logos and is in .net
• A plugin in the target application that knows about the UI and user's preferences so it can get logos styled accordingly
  This component must be written per application.

Now, I think we "want" component 3 inside a different part of the MP ecosystem and everyone has his goog reasons for that. IMHO this is not a conflicting choice, but rather a preference where the implementer feels most happy to code. So somebody started an MP1 client only plugin, morpheus went for an MP2 Server plugin, mm and FreakyJ want a TVServer plugin. I'd say to everyone: correct choice and good work, because all those components may have a plugin that knows about logos. The actualy implementation in the target aplpication is not that big in the end, (only depending on how much UI and options you wan to give the user).
So lets please not argue for the one right place to implement it, but rather where it is all possble to add it (and since we're all coders simply add it there ) and what are the required interfaces to all those places.

 

[Vasilich]

agree about shared component that can retrieve logos and do some processing. The destination and name of resulting image files can decide only the part calling this shared component, so TVServer can call it from tv config app, webradio - either from settings inside MP or from settings inside config app, etc. And all are happy

 

[bribbon]

This project has class. I.'m joying and I'm following this thread.

Let me know if I can help with my modest know, certainly more when it comes to logos


- a great and dear one is dead -
12.05.2014 - R.I.P. H.R. GIGER

 

[FreakyJ]

I have to agree with mm here where he answered the reply for me But I also like the proposal of chefkoch very much

 

[morpheus_xx]

I've created a new repo here: https://github.com/morpheusxx/MediaPortal-LogoManager and have added first users already (Vasilich, offbyone, mm135200)
@Edalex do you have a GitHub account already? there are 3 different similar names...
If more users like to be added, please let me know.

 

[breese]

I also have been following this thread and as a user and tester, I would prefer something common that all plugin's, TV, and Client Machines can draw from.
Having multiple applications / plugin's create more network time and bandwidth. Not to say the added space for multiple Logo's that if are in a single location all plugin's and applications can call from them.