Sorry to necropost, but it seemed like a good time to bring this back to light. It's many years later, but this is still relevant. With the expansion of infolabels and skin overhauls that have been happening lately thanks to @
phil65 and others, this would be super nice. In my case, I have
TV Shows / Nakamori / Tags / Comedy / Sgt Frog / Season 1
for example. Because that is so long, I would probably need to trim it, or the infolabel would need to take a list starting after the plugin, so
python:
infolabels = { 'breadcrumbs' : [ 'Tags', 'Comedy', 'Sgt Frog', 'Season 1' ] }
Then it would be up to the skinner to decide how that is displayed, whether
TV Shows / Nakamori / .. / Sgt Frog / Season 1
, a scrolling effect of some kind, or whatever. Kodi usually doesn't make decisions like how something should look, and I don't have a graphics or UI design background.
An interesting thing, because we are dealing with breadcrumbs, is we could make it allow InfoLabels as parameters. Season 1 and Sgt Frog are obviously things that would be in InfoLabels. Skins often have custom ways to display such things, and custom coloring, shortening, etc would be available by knowing what the tag is.
python:
infolabels = { 'breadcrumbs' : [ 'Tags', 'Comedy', '$INFO(ListItem.TvShowTitle)', '$INFO(ListItem.Season)' ] }
could be one way to define it. Because the skinning system lacks a nice way to handle complex logic trees, the true issue with the above is determining how a skin might access that info and apply special formatting. I'm not an advanced skinner, so I don't know if it even has a nice way to feed a list or modified list for the /../ format, either.
Well, that's some food for thought, at least.
Before, I was using a combination of hacky methods like xbmcplugin.setPluginCategory() and Window.setHeading() to achieve something similar. I naturally ran into the issue with the back and home button not reverting such a change if the window is cached.