2015-08-17, 03:29
(2015-08-17, 02:32)Milhouse Wrote:(2015-08-17, 02:11)raspberry_pd Wrote: Thanks so much for this tool MilHouse. It's become the most useful way to interact with Kodi for me. Have you considered expanding/rebranding texturecache to become *the* defacto Kodi command line control program?
Certainly no plans to rebrand despite the current name having become increasingly inaccurate as more functionality is added. Wish I'd thought ahead on that one!
Yeah bit tricky I guess.
Milhouse Wrote:It probably already is the most complete command line control program for Kodi, but if you have any ideas for new features, let me know...
Yeah I wasn't suggesting it's not already but hmmm, you might regret offering to accept new feature requests, LOL.
Actually that reminds me ... not necessarily a new feature request, but when doing cleans like vclean, can the video title be output along with the id? Hopefully this doesn't require much code or slow things down.
(2015-08-17, 02:11)raspberry_pd Wrote: More specific question ... if running OpenELEC 5.0.8 with the latest YouTube plugin installed, should I be able to use texturecache's play option to load a YouTube clip with a syntax as simple as this:
Code:$ ./texturecache.py play https://www.youtube.com/watch?v=qT4e91vR4Qo
Edit: I'm guessing the https might be the first stumbling block?
Thanks!
rPD
Milhouse Wrote:No, but the following will work:
Code:./texturecache.py play plugin://plugin.video.youtube/play/?video_id=qT4e91vR4Qo
Indeed it does! Thanks. So this highlights my thinking about kinda re-jigging the tool's erm, image / orientation, something like that. Despite your great ---help inline documentation, there appears to be so much that can be done with texturecache / the JSON-RPC API, that is unknown unless people read this thread and reading threads this long is quite a task
I wonder if there's a more focused and simpler way to document handy tasks that can be completed with texturecache? Some sort of how-to or whatnot? Wish I had a more specific idea but without wanting to criticize existing efforts, I do think this great tool could do with more/simpler/different documentation in some sort of tips and tricks format. Maybe I should start a blog? Nah, doesn't seem right. Some pages in your GitHub repo? Maybe?!!
