> I do agree that there are way too many web clients out there with no clear > choices at all, and providing a single one is a great goal. Most of the > differences you suggest between clients I think should eventually be simply > multiple configurations of a single client - single sites can have > mobile/normal versions, simple and power interface, etc. Collecting > together into a single repo and ultimately merging is probably a reasonable > approach - as long as it's clear that's the intent, not simply to manage > many different clients in one place.
I tried a bunch of web-clients and my choice was basically determined by: - resource usage (all the ajax-based clients I tried seemed better maintained and spiffier, but my web-and-mpd-server has only 64MB and 266MHz to do its work, and those clients feel sluggish on such hardware). - of the remaining clients (non-ajax), only one of them (one of the phpMp ones) turned out to survive a simple usability test without burping all over the place. So, what I'd like to see is a "phpMp-consolidated" which would provide lightweight and reliable operation, while including a bit more features than the phpMp I'm using now (the one I'm using can't be browsed by artist or genre or album, but only via the directory hierarchy or via the `search' field). Stefan PS: Can't remember if I mentioned it already, but my MPC.el Emacs-based client will be included in the upcoming Emacs-23.2. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team