2013-12-09, 13:03
(2013-12-09, 10:13)`Black Wrote: But what if I just want to use library path without an extra add-on? Is it not possible to add art stuff to those lists?
+1
(2013-12-09, 10:13)`Black Wrote: But what if I just want to use library path without an extra add-on? Is it not possible to add art stuff to those lists?
(2013-12-11, 09:49)`Black Wrote: Is it possible to temporarily cache the content somehow? With en extra service addon maybe? Otherwise core needs an update because doing several json rpc requests on window open will take way too much time. At least I wouldn't want to wait 20s or more on (every!) window open until everything is loaded with skin widgets. It needs to be there instantly after it is loaded once.
(2013-12-11, 11:16)pecinko Wrote:(2013-12-11, 09:49)`Black Wrote: Is it possible to temporarily cache the content somehow? With en extra service addon maybe? Otherwise core needs an update because doing several json rpc requests on window open will take way too much time. At least I wouldn't want to wait 20s or more on (every!) window open until everything is loaded with skin widgets. It needs to be there instantly after it is loaded once.
Better way would probably be for XBMC to generate XML or some such after library update. Script would then parse it instead or doing DB query every time. XML should then be updated after library scan, playback or watched status change. Kind of a core watchdog with XML dump.
(2013-12-13, 01:58)BigNoid Wrote: Till the artwork stuff is handled internal, this plugin maybe useful:
https://github.com/BigNoid/plugin.library.data.provider
(2013-12-13, 10:20)BigNoid Wrote: Yeah, it was much much faster coding a widget then with all the window properties
Seriously though, its faster then service.skin.widgets, but since it re-loads every time on window load it does need that time everytime, whereas window properties stay in memory and dont necessarily change on window load.