Search facility in Hijack webserver

How about a search field in the playlist page served up by Hijack? How difficult would this be for Mark to implement? Would anyone else like to have this? I envisage typing in a track name or part of a track name and Hijack returns a list of tracks that match the criteria. In fact the list could be returned as a playlist with a link to play all the tracks returned as well as each track being a link so that you could just pick the one track you were interested in. The search fields could be extended to include artist name, year etc. Would this add unecessary bloat to the kernel?

That feature already exists. It's called EMPLODE 2.0.

But that means I'd have to install Emplode on the guys PCs at work. I don't like the idea of that much for obvious reasons .

I think it would add bloat plus it would be extremely slow without access to the database (which Mark mentioned he's not using).

If you're going to search individual documents you'd want to generate some type of index to really speed up the search. And that seems a little redundant considering we already have the database (again, which isn't being used by hijack right now).

Hey, maybe someone wants to install HT://dig on their player and then see if they can get it to play nice with Hijack. Then you can get your results ranked for relevance as well.

Mark mentioned in another thread that if someone wanted to figure out the specifics on the database format that he would consider supporting it for much increased playlist generation speeds.

Bruno

As others have said, this would be a VERY SLOW operation, too slow to be useable.

I need somebody to figure out the "database" file format for me..

-ml

In reply to:

---

As others have said, this would be a VERY SLOW ...

---

I thought it probably would be slow for this very reason. But then again I'm no expert programmer so I thought I'd suggest it anyway. It's no big deal if it's not a practical proposition.

Database format ...

Whoa, that's a challenge if I ever saw one

It's not that hard.. I've figured out a little bit already.. IF anyone has a bunch of time, the easiest way to figure it out is to put in some dummy tracks/playlists and fill out all of the fields with their field names.. then just look at the database and see where they get stored..