search

mrkipling / maraschino

A front-end for HTPCs
MIT License
424 stars 125 forks source link

Showing SABnzbd history #287

Open spirro opened 11 years ago

spirro commented 11 years ago

Any chance of a button on the SABnzbd widget to show the download history, in addition to the current download status?

Thanks

gugahoi commented 11 years ago

We have tried this in the past however the module refreshes very frequently to keep the information up to date. Maybe over the holidays ill have some time to take another look at this. If you have suggestions on how this could be implemented they would be welcome too.

Morphy99 commented 10 years ago

+1 for the history this it's much needed imo.

gugahoi commented 10 years ago

I definitely get the need for this but still dont have an idea on how to implement it. Sugestions are welcome!

Morphy99 commented 10 years ago

Not sure myself as I'm no programmer but the sabnnzbd add on for xbmc shows it and I've got an android app on my phone called foshow which shows it too so must be possible. Maybe get in touch with one of those devs to point you in the right direction?

gugahoi commented 10 years ago

Sorry thats not what I meant. I had implemented it already at one point in time and know how to get such information however the way the sabznbd module works is such that it refreshes periodically which makes common implementation a bit harder. I will have to think about this a bit more but there must be a nice way to implement it.

N3MIS15 commented 10 years ago

if you moved the refresh code to the template you could make the module only update when that template is loaded, meaning when viewing queue/history (im thinking the same way sickbeard has upcomming and history) the module would not need to refresh all the time. Not sure if you would want to change the way the module looks/feels tho..

N3MIS15 commented 10 years ago

@gugahoi. https://github.com/N3MIS15/maraschino/tree/sab_his I had this a while back, maybe you can do something with it.

I think a better approach would be to trigger queue/history to show and hide individually rather that at the same time tho.