[RELEASE] RecentlyAdded Script (RecentlyAdded.py) Recently Added for Skins / Skinners

  Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Post Reply
pecinko Offline
Member+
Posts: 3,017
Joined: Dec 2008
Reputation: 27
Location: Prague / Belgrade
Post: #191
Way too many posts about skin/script compatibilities that confuse even experienced users.

My sugestion is to imprement something like min and (optional) max xbmc version to skin's/script's addon.xml so eden skins/scripts can be disabled when upgraded to frodo. Similarily, to prevent pre-frodo skins from install in eden.

Very confusing is the need to use diferent skin names to avoid this, which leads to user using quartz-svn with nightly xbmc builds but have to "change" skin to quartz when stable is released.

Just my two cents.

My skins:

Quartz
Amber
find quote
vikjon0 Offline
---
Posts: 2,429
Joined: Apr 2009
Reputation: 7
Location: Sweden
Post: #192
or add the XBMC version to the add-on version. 10.1.yyyy 11.0.yyyy. I never liked the idea to use a version gap to separate dharma version from eden version.

EDIT: I realize this is also a version gap....but with some logic to it.
find quote
kadeschs Offline
Senior Member
Posts: 164
Joined: Dec 2011
Reputation: 1
Post: #193
Fixed it. By the way, for anyone that doesn't mind tweaking under the hood, just renaming
/Users/frontrow/Library/Application Support/XBMC/addons/script.recentlyadded/RecentlyAdded.py will get everything working for right now until updates are made.
find quote
Hitcher Offline
Skilled Skinner
Posts: 9,935
Joined: Aug 2007
Reputation: 67
Location: Eastleigh, UK
Post: #194
kadeschs Wrote:This is what I was beginning to think to. It's as if the skins haven't been updated yet to work with the new version. I like the Recently Added feature and was hoping to at least manually correct the problem to get it working again. If nothing else, to keep the constant error notifications from popping up everytime I go to the home screen.

The skin's name is Rapier. However, the same thing seems to also be happening in Aeon MQ 2 so I assume the problem lied in the py script by which the skins called on.

What happens if you refresh one of those episodes?

There might not be any image because, at the time of scraping, there wasn't an image available on the tvdb.

[Image: sig_zps3af3b48e.jpg]
find quote
Big_Noid Online
Skilled Skinner
Posts: 2,627
Joined: Jul 2010
Reputation: 68
Location: Below sea level
Post: #195
pecinko Wrote:Way too many posts about skin/script compatibilities that confuse even experienced users.

My sugestion is to imprement something like min and (optional) max xbmc version to skin's/script's addon.xml so eden skins/scripts can be disabled when upgraded to frodo. Similarily, to prevent pre-frodo skins from install in eden.

Very confusing is the need to use diferent skin names to avoid this, which leads to user using quartz-svn with nightly xbmc builds but have to "change" skin to quartz when stable is released.

Just my two cents.


i don't think XBMC version numbers have to do anything with this. it's all about which api or xbmc.gui is used. The recent added script is really an exception to the rule because the functionality has been moved to core.
find quote
kadeschs Offline
Senior Member
Posts: 164
Joined: Dec 2011
Reputation: 1
Post: #196
Hitcher Wrote:What happens if you refresh one of those episodes?

There might not be any image because, at the time of scraping, there wasn't an image available on the tvdb.

Nothing. It wasn't a matter of tvdb not having the images as those images were present under Dharma. The existing images disappeared after upgrading to Eden. However, the images and everything returned once I renamed the RecentlyAdded.py file to something else. It was like the core functionality and script file were conflicting with each other since they both were trying to accomplish the same thing at the same time.
(This post was last modified: 2012-01-09 17:50 by kadeschs.)
find quote
Post Reply