oeps forgot to include list.
-------- Original Message --------
Subject: Re: [Musicpd-dev-team] Please pull
git://github.com/superjoe30/mpd.git patch-upstream
Date: Mon, 23 Jan 2012 13:08:04 +0100
From: Qball Cow <qb...@qballcow.nl>
To: Andy Kelley <superjo...@gmail.com>
This is allready possible with the current search? I don't see how this
extends the search functionality.
If you look at gmpc's advanced_search if you do:
any=this is my query.
it will search as described. (I think).
I think in mpd protocol is it something like:
search any "this" any "is" any "my" any "query"
you can make is specific by using artist|album|etc instead of any.
gmpc internally also allows you to | (or) brackets() to combine, etc.
On 01/23/2012 12:35 PM, Andy Kelley wrote:
Here's my proposed command:
smartsearch "this is my query"
It would be identical to how most audio players search - Amarok,
Rhythmbox, iTunes, Winamp, etc.
The query is broken into words ['this', 'is', 'my', 'query'] and each
word is independently matched against the artist, title, and album
concatenated together.
So if I have a song like this:
{
artist: "The Burning Awesome",
album: "Crunchy Beats and Techno Treats",
title: "The Castle"
}
These searches will match this song:
burn eat cas
cruNcHy treats
the aWE le
These searches will /not/ match this song:
burninggggg
the burning aweSUCK
castle crunchy beat treat ZZZZ
"smartsearch" is kind of a dumb name. I don't really care what the
command is named, I just want it to exist.
On Mon, Jan 23, 2012 at 3:24 AM, Max Kellermann <m...@duempel.org
<mailto:m...@duempel.org>> wrote:
On 2012/01/23 12:18, Andy Kelley <superjo...@gmail.com
<mailto:superjo...@gmail.com>> wrote:
> Hmm. I agree that it makes sense to put the dynamic playlist
functionality
> into a proxy daemon. Especially with the ability to add
arbitrary data to
> tracks.
Additional data can be managed in "stickers", which can be seen by
both your new daemon and then UI client.
> What about the search feature though? Should the daemon
continually poll
> and cache all of mpd's library in order to provide that search?
I think it
> makes sense to put that in mpd.
Sorry, I missed that part - and I don't understand it yet, can you
please explain it to me again?
In general, anything that improves MPD's search/find command is
obviously a good idea. New features should be optional, though;
i.e. we should have a new syntax for new features.
Max
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Musicpd-dev-team mailing list
Musicpd-dev-team@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Musicpd-dev-team mailing list
Musicpd-dev-team@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
