Re: [Banshee-List] 2 feature suggestions: syncing to playlist / autosync

[Christopher Friedt <cfriedt visible-assets com>]

Josiah Ritchie wrote:
> On 2/12/07, Christopher Friedt <cfriedt visible-assets com> wrote:
> > Josiah Ritchie wrote:
> > > #2: Are you saying that you want a manual sync that would work like
> > > the full library sync, but only with a playlist instead of the full
> > > library?

It shouldn't be too hard to implement this at all actually.

Doesn't banshee remember the 'unique id' of a device anyway? I can't say 
for sure because I've never seen the structure of 'banshee.db'

From HAL -

Device Info:
...
Serial Number:    4J446T8NPS9
...
Manufacturer ID:  4J

because then it can be just stored in a table with 2 columns so

'unique player hash id' | 'name of associated playlist'
=======================================================
asd98ysdgpuhasd | (null)
087aouhw4'p9u8ase | "General"
0o8wruhas7yasdf | "Nano"
sa9f8yas9df8yas | ""

Then there would obviously be a couple of exceptions

1) if the playlist was renamed on the pc, it would have to update the 
name here as well - otherwise exception 4 would be generated

2) if a device has a (null) - or effectively its 'unique id' doesn't 
exist on the left side then no playlist is associated (obviously) but 
this could be a que for banshee to ask the user if they would like to 
associate device "asd98ysdgpuhasd" with a playlist (and then record both 
the 'player id' and the "name of the associated playlist" selected)

3) if a playlist is is deleted, then banshee should also remember to 
delete it from this table. otherwise exception 4 would be generated

4) there is a playlist associated with this device but the playlist does 
not exist.

Just out of curiousity, which does the 'banshee.db' look like ?

> I wonder if playlists associated with devices should be called queues
> instead to avoid confusion with other playlists. Then there would be
> some options on how to create the device queue, whether through a
> SmartPlaylist style or a normal playlist style. I wonder how this
> would complicate working with the device.

I would only associate a device with a 'generic playlist' type at the 
moment. Re: complications, see above.

> Either way, some new language should probably be put together to
> better describe how the DAPs interact with banshee. That's been talked
> about in the IRC channel before.

Making a new scripting language for Banshee is an interesting idea ... 
like 'boo' for instance (wasn't that what it was being called?) ...

you could check out the logs, change global variables of any kind, query 
modules, etc, etc ... but then you could also make a global event queue 
and allow 'commands' in the language to hook into events and initiate 
things based on that.

I'd like to learn a bit more about this, but i wasn't on the IRC 
channel. Can anyone inform me? I think that making a 'shell' of sorts 
can be an excellent way to extend an application. Lex / Yacc are great 
tools for this sort of thing, and i've worked with them in the past.

I'm just curious though - what sort of functonality would you want to 
have in the language ?

Regards,

~/Chris