jezbo;259946 Wrote: > Whole-heartedly disagree. > > I'm a developer myself, and our happiness is not the issue, a product > must be flexible enough to satisfy the majority of customers. Making > some rule rigid so that it only satisfies half the customers, even if > it makes things simpler, is not good practice. And the rule of thumb on > introducing a new option - make what it did before the default.
Making a rule more rigid so that it works better for 99% of the customers and keeps code more consistent is better, though. I doubt 50% of customers separate an albums tracks by genre. I doubt it is even 1%. A ton of customers Just Work with the dropping of Common Album Names and the must-be-same-album-if-in-same-directory code. Common Album Names sucked. > > As it is, I won't be using the SlimServer web interface since browsing > of albums is such a pain; I'm writing my own interface that builds it's > own database. I'll have to put up with duplicates in browsing via the > remote I suppose. It would be much easier to modify the scanner to do as you want. Then it would work consistently across the web and remote interfaces. -- snarlydwarf ------------------------------------------------------------------------ snarlydwarf's Profile: http://forums.slimdevices.com/member.php?userid=1179 View this thread: http://forums.slimdevices.com/showthread.php?t=42341 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
