Re: [Musicpd-dev-team] webclient phpMp
Hi, As you can clearely see I am new to git and its use :-). Yes thats true there were the original tars in it first so the repo exploded to 48mb. As soon as I figured out how to bann them from the history the repo will be a couple of kbs. @stefan there are heaps of mpd-webclients out there. I downloaded most of them and tried each to figure out which one suits to my needs. mostly there were no changes since years on some clients. I thought it would be nice to simply download a package of webclients where I could simply switch to any client -- this is going to be phpMpReloaded. best -tswaehn Max Kellermann wrote: On 2010/02/26 10:36, Sven Ginka sven.gi...@gmail.com wrote: additionally i also pulled the following versions and will maintain them - phpMp2 0.11.0 - phpMp+ 0.2.3 Great news to see somebody revive an old MPD client! Since the project is abandoned, you could continue the original project, without a rename. I cloned your repository, but I was baffled that git downloaded 46 MB of changesets. You didn't preserve the old change history, but created a whole new repository, and you committed several large tarballs into it, only to remove them with the next commit. Why did you import 4 versions of phpmp? Which one of these are you going to work on? Why not clone the original git repository, and work on that? We could give you write access to git.musicpd.org. Oh, and please fix your git configuration: Author: tswaehn tswa...@homer.(none) Author: root r...@homer.(none) Max -- Download Intel#174; 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
Re: [Musicpd-dev-team] webclient phpMp
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. On Sun, Feb 28, 2010 at 11:54 AM, Sven Ginka sven.gi...@gmail.com wrote: Thanks for the infos regarding git. I'll try to clone from the original phpMp instead of starting with the tar. That makes sense. I'll figure that out Regarding the multiple client thing. I agree that having multiple clients in one repos is not the usual way. But: (1) different hardware clients may need different web clients (mobiles, pda, netbook, ... speaking of javascript, frames, ...) (2) there are different clients out there suiting most needs (small and easy ones, stylish ones, ... ) sometimes hard to find (3) most of them are quite old and need only little care to get them working on a current system due to deprecated functions/changed interface (4) new users to mpd might be disappointed when accidently picking a non working small and basic client and might be disappointed instead of choosing out of a rich collection (5) the code itself is very little and changes are nearly static so putting them toghether in one repo is a good start (instead of leaving them spread over the internet) (6) i talked to the ben who made the mpd-class which is used by various clients and will also be included in phpMpReloaded (for future clients) (7) having different clients also suggests to pull the best out of each to finally create a perfect client (8) this could also be a platform where people talk about mpd webclients instead of creating an own page and publishing a self written client without known what actually allready exists out there -- say community It is meant to be a good collection of clients and to come in touch with mpd webclients and/or develop based on given source the perfect client. @jeffrey I didnt talk too much about it in the first place because I thought its no big deal, just putting all toghether mostly for myself and second for others having some little changes/impovements whatever. But your question put me to more thinking about it. Thanks. Best -tswaehn Jeffrey Middleton wrote: Those tars weren't in the original phpMp repository, were they? As Max said, it'd be best to start from that (preserve the history). If they really were in the original one, you could use git filter-branch to alter the history (but this is scary!). As for the multiple clients thing... it doesn't make much sense to me to have multiple projects in a single repository. If there's something to be gained from each of these clients, the right approach would be to add the features from all the rest to phpMp (if they're mutually exclusive, allow configuration). We don't want a handful of choices which between them provide all the features, we want one single great web client. Jeffrey On Sun, Feb 28, 2010 at 9:18 AM, Sven Ginka sven.gi...@gmail.com mailto:sven.gi...@gmail.com wrote: Hi, As you can clearely see I am new to git and its use :-). Yes thats true there were the original tars in it first so the repo exploded to 48mb. As soon as I figured out how to bann them from the history the repo will be a couple of kbs. @stefan there are heaps of mpd-webclients out there. I downloaded most of them and tried each to figure out which one suits to my needs. mostly there were no changes since years on some clients. I thought it would be nice to simply download a package of webclients where I could simply switch to any client -- this is going to be phpMpReloaded. best -tswaehn Max Kellermann wrote: On 2010/02/26 10:36, Sven Ginka sven.gi...@gmail.com mailto:sven.gi...@gmail.com wrote: additionally i also pulled the following versions and will maintain them - phpMp2 0.11.0 - phpMp+ 0.2.3 Great news to see somebody revive an old MPD client! Since the project is abandoned, you could continue the original project, without a rename. I cloned your repository, but I was baffled that git downloaded 46 MB of changesets. You didn't preserve the old change history, but created a whole new repository, and you committed several large tarballs into it, only to remove them with the next commit. Why did you import 4 versions of phpmp? Which one of these are you going to work
Re: [Musicpd-dev-team] webclient phpMp
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#174; 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
Re: [Musicpd-dev-team] webclient phpMp
On 2010/02/26 10:36, Sven Ginka sven.gi...@gmail.com wrote: additionally i also pulled the following versions and will maintain them - phpMp2 0.11.0 - phpMp+ 0.2.3 Great news to see somebody revive an old MPD client! Since the project is abandoned, you could continue the original project, without a rename. I cloned your repository, but I was baffled that git downloaded 46 MB of changesets. You didn't preserve the old change history, but created a whole new repository, and you committed several large tarballs into it, only to remove them with the next commit. Why did you import 4 versions of phpmp? Which one of these are you going to work on? Why not clone the original git repository, and work on that? We could give you write access to git.musicpd.org. Oh, and please fix your git configuration: Author: tswaehn tswa...@homer.(none) Author: root r...@homer.(none) Max -- Download Intel#174; 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
Re: [Musicpd-dev-team] webclient phpMp
there are some smaller issues in the webclient. however i am going to maintain it, if nobody cares. i pulled the source as of version ver 0.11.0 (2004/6/18) to http://sourceforge.net/projects/phpmpreloaded/ the issues itself: - there is a deprecated function split in it. it could be substituted by explode in any cases. - the variable $mcount is uninitialized; so i added $mcount = array(); - there seems to be a change in communication so $mcount needs to be set to zero although count($lsinfo[music]) is non zero i fixed the issues on |git://phpmpreloaded.git.sourceforge.net/gitroot/phpmpreloaded/phpmpreloaded additionally i also pulled the following versions and will maintain them - phpMp2 0.11.0 - phpMp+ 0.2.3 As a (long time) user of one of them (not sure which, now), that sounds very good. But could you clarify how your phpmpreloaded relates to phpmp, phpmp+, phpmp3, phpmp3, ...? E.g. Is it a superset of all of them? Stefan -- Download Intel#174; 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
