foo_playlist_attributes, Assign relevant attributes to a playlist Options

[fbuser]

This component lets you assign various attributes to a playlist. The component also reimplements two options which are already provided by foo_removeplayed, to make them useable on a per playlist basis.

Download the latest version: here

This post has been edited by fbuser: Sep 16 2011, 22:52

[q-stankovic]

(As my point is not related to functionality of foo_playlist_playback_attributes and also could mention other components it may be makes sense to split that part)

Is it so hard to read my first answer to your question completely?

No, it isn't. That's why i already read and understood it since you gave me the link for the vista style guide. I know your reasons: consistency within the component and within the OS. Maybe i should have better asked: What is your desired consistency good for and why is it more important than consistency within fb2k?

He's being consistent with the OS.
It's really up to both the core and 3rd party components to follow the vista style guide conventions.

Since the relevant parts of the menu haven't been rewritten in forever in fb2k's menu, it's only natural they're still in XP style.

I didn't know that it would also be up to foobar2000 to follow the style conventions - thanks for the clarification. But however, the title-style capitalization is used since years and it doesn't seem that the menu items will be rewritten. Not only fb2k uses that style, all official components and the major part of 3rd-party use it. A rewriting would not encourage consistency within the program but increase a messy appearance of both styles. What is easier than taking the program and its official components as criterion for consistency foremost because the majority of components authors do that already?

I am very aware that many users don't care about such a topic, but in my eyes such points seperate a perfect component from a good one. To come back to the second post of my initial post: i still believe that the edit-submenu is a better place for assigning playback attributes of the active plalist. Now you have global playback options mixed with options related to active playlist in one submenu. Another point i didn't mention so far: can't commands that doesn't make sense in a certain context ("remove played tracks" in autoplaylists) be disabled by greying them out just to show the user that they are not available? As you see: each point is just a small point - but sum up all this points inside one component and multiply this sum with all components that don't care about such things. The result will be that quality of usability will decrease. The most sad thing about this is: this quality can be achieved so easily if devs and users just would care.