•   
  • 1
  • 3
  • 4
  • 5(current)
  • 6
  • 7
  • 25
  •   
Release script.embuary.helper - a skin helper service / widgets alternative
#61
(2019-08-02, 20:37)sualfred Wrote: Big thanks for @jurialmunkey
His recently work on the plugin tmdb data approach made me finally starting to work on something what was on my list since a few months.

Since Phil is missing in action and ExtendedInfo is unmaintained and in a very bad shape:
Embuary Helper will get its rich actor and video info feature. The basics, the queries, the window custructor etc. is already working. Now I only have to deal with all properties and their stored information.

Current WIP stage:
Looks great!

Does this use skinnable script windows like extendedinfo? If so, I'm wondering if those lists will be optional?

One of my big gripes with extendedinfo (and main reason I started working on my plugin) is that you need to include *ALL* the list IDs to get it to work. It really limits the flexibility of the layout etc. It's possible to hide them as hidden empty lists but it's annoying knowing that the script is still grabbing all the data.

Also, is it possible to split this one off into a separate script/plugin?
Reply
#62
It basically follows the same logic like ExtendedInfo does.
The lists will be optional but the IDs are going to be reserved. And there are not much lists I'm going to add. Mostly only related movies/tvshows, cast, images. And since you are going to be built a "plugin based TMDB catalog" I wont' add more, but I'll keep the TMDB id of items everywhere stored so skinners can extend this windows on their own with your plugin.

So, yeah, it is and will always be a very very lightwight "little bro" of ExtendInfo. Atm it's integrated into my helper to save time, but it won't be a big deal to split it to a own once it's done.
Embuary | Skin | Helper | Info | Repo | GitHub
Reply
#63
(2019-08-04, 00:38)sualfred Wrote: It basically follows the same logic like ExtendedInfo does.
The lists will be optional but the IDs are going to be reserved. And there are not much lists I'm going to add. Mostly only related movies/tvshows, cast, images. And since you are going to be built a "plugin based TMDB catalog" I wont' add more, but I'll keep the TMDB id of items everywhere stored so skinners can extend this windows on their own with your plugin.

So, yeah, it is and will always be a very very lightwight "little bro" of ExtendInfo. Atm it's integrated into my helper to save time, but it won't be a big deal to split it to a own once it's done.
This sounds fantastic! And will be the perfect compliment to my tmdb helper (which I'm currently rewriting with classes and better code structure now that I've got the basic concept working).

Also saves me having to write a window manager, which I really didn't want to do.
Reply
#64
The only downside is, that all clicks on custom containers will close the dialog and open the target of your items. The window history is all fake, because usually a script is running once and then stops. I just keep everything alive and running in something like a loop as long as some kind of information exist. But I think we could solve it if you would add 2 listitem properties to your output.
Embuary | Skin | Helper | Info | Repo | GitHub
Reply
#65
(2019-08-02, 20:37)sualfred Wrote: Big thanks for @jurialmunkey
His recently work on the plugin tmdb data approach made me finally starting to work on something what was on my list since a few months.

Since Phil is missing in action and ExtendedInfo is unmaintained and in a very bad shape:
Embuary Helper will get its rich actor and video info feature. The basics, the queries, the window custructor etc. is already working. Now I only have to deal with all properties and their stored information.

Current WIP stage:

Look forward to trying it out.
Reply
#66
Nearly ready. All that is left is ripping it out of Embuary Helper to get a standalone addon and create some setting options. And off course cleanup, but everything seems to work.
Just give me 1-2 days and I'll give you folks a test build.

Features:
- Support for changing to a own default language and use en-US as fallback if important informations are missing or no result was returned at all
- Super fast dialog history handling. Closing a dialog will go to the previous one if available
- Search for person/TV show/movie
- Select dialog for multiple search results
- TV shows / movies starring current actor
- Similar movies/shows
- Cast listing
- Images + fullscreen image dialog
- YouTube results incl. check if they are still online and playable
- Option to directly go to show or play movie if it's part of the local database

Embuary | Skin | Helper | Info | Repo | GitHub
Reply
#67
Looking great @sualfred ! Will you also provide an indicator of which movies/tv shows are in the local library like extendedinfo does?

Regards,

Bart
Reply
#68
Yes.
Embuary | Skin | Helper | Info | Repo | GitHub
Reply
#69
@sualfred 

Is this working for every ratings/votes InfoLabel available in Kodi?

ListItem.Ratings(imdb)
ListItem.Votes(imdb)
ListItem.Ratings(themoviedb)
ListItem.Votes(themoviedb)
ListItem.Ratings(metacritic)
ListItem.Votes(metacritic)
ListItem.Ratings(tomatometerallcritics)
ListItem.Votes(tomatometerallcritics)
ListItem.Ratings(tomatometerallaudience)
ListItem.Votes(tomatometerallaudience)
ListItem.Ratings(anidb)
ListItem.Votes(anidb)
Reply
#70
As long the info is in the database.
Embuary | Skin | Helper | Info | Repo | GitHub
Reply
#71
(2019-07-27, 09:14)sualfred Wrote: ..
Important: Kodi only supports floats up to 10.0. Since Rotten is using 0-100 I'm going to convert the values. Example -> "56" = "5.6"
..
 
First HUGE THANKS again for the script. It'll become a must have . ALSO YOUR WIKI IS GREAT WRITTEN

But I seem to get issue to get the formatted rating string.

Did you already implement this?
$INFO[Container(my-hidden-container-id).listitem.Rating(rottentomatoes)] - it remains empty


Those are fine

$INFO[Container(5055).ListItem.Rating(default)]
$INFO[Container(5055).ListItem.Rating(imdb)]
$INFO[Container(5055).ListItem.Rating(themoviedb)]
$INFO[Container(5055).ListItem.Rating(tomatometerallaudience)]
$INFO[Container(5055).ListItem.Rating(tomatometeravgaudience)]
$INFO[Container(5055).ListItem.Rating(metacritic)]

Image

Image

can you guide me to the correct label usage ?
or should i better handle it with variable usage?
Skins                                                                                        
Reply
#72
Works well on my end. I use the key value that is stored in the database. If you can provide me your myvideos116.db I can look for a possible issue. A PM is fine.
Embuary | Skin | Helper | Info | Repo | GitHub
Reply
#73
(2019-08-06, 06:41)mardukL Wrote: Did you already implement this?
$INFO[Container(my-hidden-container-id).listitem.Rating(rottentomatoes)] - it remains empty
That's not a valid info label. These are the values Universal Scraper uses -


Listitem.Rating(tomatometerallcritics)
Listitem.Rating(tomatometeravgcritics)
Listitem.Rating(tomatometerallaudience)
Listitem.Rating(tomatometeravgaudience)
Reply
#74
Thanks. Could you also tell me which one of these is the main tomatometer? I mean the one with the rotten/fresh icon. I'm confused so I better ask twice.
Embuary | Skin | Helper | Info | Repo | GitHub
Reply
#75
(2019-08-06, 16:44)sualfred Wrote: Thanks. Could you also tell me which one of these is the main tomatometer? I mean the one with the rotten/fresh icon. I'm confused so I better ask twice.
@sualfred, the critics one is the main tomatometer.

Regards,

Bart
Reply
  •   
  • 1
  • 3
  • 4
  • 5(current)
  • 6
  • 7
  • 25
  •   



Logout Mark Read Team Forum Stats Members Help
script.embuary.helper - a skin helper service / widgets alternative3
This forum uses Lukasz Tkacz MyBB addons.