Page 1 of 1

I'm having a little trouble with SDs.

Posted: 06 Aug 2012 23:51
by NoMoreNicksLeft
I've managed to figure out how to do playlist parsers, and have added support for a video website that no one seems to have bothered with. In addition to playing the video at any specific url, it also will load all the videos off the front page (or search results page) along with the "next page" url, such that when it finishes playing the first page of videos, it will subsequently load page two and play those.

But rather than type in the URL with query string every time you want to do that, I was hoping to turn it into an SD. And I've run into several issues.

Whereas with the playlist window it replaces the url of the video page with the url/title of the video, in an SD it uses that tree view mode, and the video url appears below the page url, which appears below the front/search page url, which appears below the root node. It's ugly. And when it gets to the last link which is "next page", it nests those inside/under "next page". So after running through 3 or 4 pages of videos, the tree view crawls rightward. Eventually you can't read the titles. How do I put the SD into flat mode like the playlist?

I can set the title of the SD, but I'd like to set the icon appearing to its left. Is this possible?

For the search SD it would be nice if, when clicked on, I could put up a simple dialog to ask for the keywords. Is there no way to enable that for SDs? This doesn't make much sense as an extension (I'm not even sure what extensions are supposed to be for, to be quite honest).

[edit] Finally figured out how to use vlc.stream() to open urls and extract metadata and so forth. So it's uncluttered the tree view a little bit. But I don't dare replace the video webpage URL with the actual video file URL, for this site they make the direct links temporary, you've got less than a half hour to use them. But if I just use the webpage URL and let the playlist.lua turn that it into the correct video file link when it comes time to play, then it adds a child node underneath the original entry. Not ideal, aesthetically speaking.