3rd party plugins and 8.0 ?

[dolodobendan]

> (I saw the latest commit regarding audiobooks. Nice! Any chance there
> will be something like series next to authors?)

Can you elaborate? What would a series be? How would it be "next to
authors"?

--

Michael

A series would be "Drei Fragezeichen". Different authors, but they belong together. I omit the actual author and use the series' name because I couldn't come up with something better. I tagged them "Audiobook;Hörspielreihen". They do not show up under "Authors" and vice versa.

For "regular" audiobooks I use ARTIST as the author. Series don't show up in there. I don't need TKKG next to Tolkien.

I made this with Custom Browse:



The home menu entry is "Hörspiele", these are the subfolders. That's what I meant with "next to". This menu shows audiobooks only (Multi Library: Genre = Audiobook). It's kind of a library view, maybe? I never understood those.

"Autoren" show authors only. I excluded "GENRE=Hörspielreihen" using CB's Filtered Artists template.

"Filtered Artists" is a Custom Browse template, I think that's what I used to separate Authors and Series by limiting to GENRE. Just a test menu.

"Reihen" shows all series, GENRE=Höspielreihen only. Also a CB's template.

"Artists" shows all artists in this Multi Library (GENRE = Audiobooks). I never use this.

"Alben" just shows all albums in this Multi Library (GENRE = Audiobooks).

"Neue Alben" shows all new albums in this Multi Library (GENRE = Audiobooks).

[mherger]

> A series would be "Drei Fragezeichen".

What tag would that piece of information be stored in?

> Different authors, but they
> belong together. I omit the actual author and use the series' name
> because I couldn't come up with something better. I tagged them
> "Audiobook;Hörspielreihen". They do not show up under "Authors" and vice
> versa.

I only know those series from Spotify - where we don't get to see the
authors...

--

Michael

[dolodobendan]

> A series would be "Drei Fragezeichen".

What tag would that piece of information be stored in?

ARTIST. I use GENRE to separate ARTIST=Author and ARTIST=series.

Sorry, I rewrote my post and that part got lost.

[mherger]

> ARTIST. I use GENRE to separate ARTIST=Author and ARTIST=series.

Using one of Erland's plugins? This sounds like too much of an edge case
to me to be generalized. Already the selection of default genre strings
is difficult to impossible to get right. Changing behaviour based on one
of the would become even harder.

--

Michael

[dolodobendan]

> ARTIST. I use GENRE to separate ARTIST=Author and ARTIST=series.

Using one of Erland's plugins?

"Filtered Artists" is a Custom Browse template, I think that's what I used to separate Authors and Series by limiting to GENRE. Just a test menu.

(Yes.)

This sounds like too much of an edge case
to me to be generalized. Already the selection of default genre strings
is difficult to impossible to get right. Changing behaviour based on one
of the would become even harder.

--

Michael

Of course. There are too many edge cases to consider. What about a more dynamic approach: Cover the basics but make it easier to customize (some xml-file per menu, maybe)?

[mherger]

> Cover the basics but make it easier to customize (some
> xml-file per menu, maybe)?

Anything involving editing XML isn't easy by definition :-D.

I believe this feature is well suited for a third party plugin.

--

Michael

[dolodobendan]

> Cover the basics but make it easier to customize (some
> xml-file per menu, maybe)?

Anything involving editing XML isn't easy by definition :-D.

I believe this feature is well suited for a third party plugin.

--

Michael

Considering an end-user I'd wager she'd rather be editing an XML file than writing a plugin.

[mherger]

>>> Cover the basics but make it easier to customize (some
>>> xml-file per menu, maybe)?
>>
>> Anything involving editing XML isn't easy by definition :-D.
>>
>> I believe this feature is well suited for a third party plugin.
>
> Considering an end-user I'd wager she'd rather be editing an XML file
> than writing a plugin.

I'm asking _you_ to write the plugin for her and them all.

--

Michael

[dolodobendan]

>>> Cover the basics but make it easier to customize (some
>>> xml-file per menu, maybe)?
>>
>> Anything involving editing XML isn't easy by definition :-D.
>>
>> I believe this feature is well suited for a third party plugin.
>
> Considering an end-user I'd wager she'd rather be editing an XML file
> than writing a plugin.

I'm asking _you_ to write the plugin for her and them all.

--

Michael

So you think it's a good idea after all. Great!

[dolodobendan]

I'm already on page 81 on "Learning Perl".