#10 ✓resolved
Brad

Upcoming episodes module

Reported by Brad | November 1st, 2011 @ 10:25 PM | in v0.1 (closed)

Comments and changes to this ticket

  • gugahoi

    gugahoi December 11th, 2011 @ 11:30 AM

    I take it this can be marked as done?

  • Brad

    Brad December 11th, 2011 @ 12:43 PM

    • Tag changed from feature to feature
    • Assigned user cleared.

    If it's in prerelease then it should be set for milestone v0.1 and marked done once reviewed/tidied.

  • Brad

    Brad December 11th, 2011 @ 02:17 PM

    • Milestone set to v0.1
    • Tag changed from feature to feature
    • Milestone order changed from “9” to “0”
  • gugahoi

    gugahoi December 12th, 2011 @ 01:34 AM

    • Assigned user cleared.

    The upcoming episodes is actually much more than that. I have been slowly coding Sickbeard's API into it. I eventually want to be able to control just about every aspect of SB from it.

  • Brad

    Brad December 12th, 2011 @ 01:35 PM

    • Tag changed from feature, sickbeard to feature, sickbeard

    Just so I'm clear - this is an upcoming episodes module which gets the info from Sickbeard? But ultimately you want it to be a Sickbeard module?

    I would recommend focussing on making it an upcoming episodes module using Sickbeard for the time being (so that we can get v0.1 ASAP as I'm keen to get that large release out), and then let's discuss the pros and cons of making it an uber-Sickbeard module, or splitting into two modules. Both could be fine options but I feel that it warrants discussion.

  • Brad

    Brad December 12th, 2011 @ 01:37 PM

    Also, check out ticket 30 ("SB module") - is this ticket a duplicate of that? If so then please close it, thanks :)

  • Brad

    Brad December 15th, 2011 @ 09:30 AM

    • Assigned user set to “Brad”
  • gugahoi

    gugahoi December 16th, 2011 @ 03:00 AM

    Ye, it is the same module. A lot of the code is already there so if you want to focus on it being only a Upcoming Episodes module then it is ready for review. There are extra features already on it. Creating another module could be considered but for sake of saving space I strongly prefer using it the way it is now.

  • Brad

    Brad December 17th, 2011 @ 12:38 PM

    • Tag changed from feature, sickbeard to feature, sickbeard
    • State changed from “new” to “resolved”

    In that case let's close this ticket and use #30. Let's go with the more complete Sickbeard module as per your preference.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Open-source front-end for XBMC HTPCs

Shared Ticket Bins

People watching this ticket

Referenced by

Pages