by t3chnomanc3r » Thu Apr 29, 2010 2:40 pm
Well, this came in just as I was about to respond to the last post.
Keeping in mind there are many podcasts the add valued content to their feeds in addition the "multimedia" content, this is all the compromise *I* would be looking for (assume same for others) and had such an option existed never would I have been heard from. Default off makes sense as with any advanced feature, lack of configuration *is* the issue here not devs default limited choices. Personally I'm not a slave to a single app or GUI supporting every filetype I have. Obviously I see no issue with one app downloading all my feeds to a common folder tree and then manually utilizing that content from many apps. In the end it's not like the request is to be able to tag, catalog, or play unsupported filetypes in MM but if podcast adds a PDF for show notes, etc... I do want it downloaded!
Random fact: MM already does some touching of files it does not support when rename moves everything from a folder it offers to move unsupported content as well so it's not unheard of to touch files the user can't see in MM interface.
Lowlander wrote:I think the compromise solution would be an option to download unsupported formats that is disabled by default. Even better yet would be the ability to allow the user to select all enclosed files or let the user choose which file extension should be downloaded (I envision a textbox with ; delimited file extension entry).
This would allow power users to configure what get's downloaded, but not overwhelm new users as to why their PC is all of a sudden full.
I do still feel uneasy about it as it's strange a software is downloading files it can't handle at all, this means the user would need to hunt the downloaded files down using another software. This means that such user would be better served by a program that can both download and manage (as in make available to the user in the software itself, not necessarily do things like tagging or even opening the files) those files.
Well, this came in just as I was about to respond to the last post.
Keeping in mind there are many podcasts the add valued content to their feeds in addition the "multimedia" content, this is all the compromise *I* would be looking for (assume same for others) and had such an option existed never would I have been heard from. Default off makes sense as with any advanced feature, lack of configuration *is* the issue here not devs default limited choices. Personally I'm not a slave to a single app or GUI supporting every filetype I have. Obviously I see no issue with one app downloading all my feeds to a common folder tree and then manually utilizing that content from many apps. In the end it's not like the request is to be able to tag, catalog, or play unsupported filetypes in MM but if podcast adds a PDF for show notes, etc... I do want it downloaded!
Random fact: MM already does some touching of files it does not support when rename moves everything from a folder it offers to move unsupported content as well so it's not unheard of to touch files the user can't see in MM interface.
[quote="Lowlander"]I think the compromise solution would be an option to download unsupported formats that is disabled by default. Even better yet would be the ability to allow the user to select all enclosed files or let the user choose which file extension should be downloaded (I envision a textbox with ; delimited file extension entry).
This would allow power users to configure what get's downloaded, but not overwhelm new users as to why their PC is all of a sudden full.
I do still feel uneasy about it as it's strange a software is downloading files it can't handle at all, this means the user would need to hunt the downloaded files down using another software. This means that such user would be better served by a program that can both download and manage (as in make available to the user in the software itself, not necessarily do things like tagging or even opening the files) those files.[/quote]