My blog has moved!

Visit
http://nloko.ca
and update your bookmarks.

GSoC: Week 3

http://nloko.ca/?p=13

12 comments:

Ramón | June 16, 2009 at 10:17 AM

This is really really impressive work! Congratulations from a 'normal' GNOME user who reads Planet GNOME just to know what's going on there! :P Keep on your work!

P.S.: I'm sorry about my bad English!

Anonymous | June 16, 2009 at 11:15 AM

What exactly does this project try to do?
Why is there a context pane taking space when it's not used? For that matter what's it for anyway?

Cheers.

nloko | June 16, 2009 at 11:28 AM

@Ramon, Thanks! P.S. Your English is great!

@Anonymous, Check the "BIG News" post for what this does. And, the context pane is bleeding edge new stuff available in Banshee git master.

Tretle | June 16, 2009 at 11:51 AM

Niiiiiiiiiiiiiiiiiiiiiiiiccccccccccccccccceeeeeeeeeeeeeee :)

Dread Knight | June 16, 2009 at 12:17 PM

Impressive!

Jakub Rusinek | June 16, 2009 at 12:56 PM

I've got a simple offtopic question. What's your desktop font?

nloko | June 16, 2009 at 1:01 PM

@Livio, URW Gothic L Book. I don't really see anything "gothic" about it, though. :)

ComaWhite | June 16, 2009 at 3:37 PM

Too bad it's not as good looking at Amarok :(

Sandy | June 17, 2009 at 6:48 AM

@ComaWhite I agree completely. Looking at Amarok is not nearly as good as looking at Banshee. ;-)

Alban Crequy | June 20, 2009 at 5:04 AM

Sharing music with contacts is great! Who is the initiator of the tube? Is it the one who requests an access to a contact's music library or it it the one who shares its music library? In the first case, I wonder how you do it, as the initiator of a tube can listen on a tcp connection but not initiates tcp connections.

nloko | June 20, 2009 at 9:12 AM
This comment has been removed by the author.
nloko | June 20, 2009 at 9:35 AM

@Alban, the initiator is the one who wishes to browse the other's library. So, in my example, contact A wants to browse contact B's library. I'm using DBusTubes to export the library asynchronously. It gets delivered in arbitrary chunk sizes (currently 400 tracks at a time) and the display updates as it downloads. Contact A does a CreateChannel for the tube, contact A gets a NewChannels signal and offers it. contact B gets a NewChannels signal and accepts it. Contact B gets a TubeStateChanged signal, when open, it exports the dbus object(s). Contact A gets the same signal and uses the exported object(s). I'm sure you already knew all that. :) But, just clarifying how it works.

Post a Comment

Comments are posted without moderation. However, spam and anything off-topic may be deleted without notice.