Translations are actually a downgrade, imho. Not a good point to list :)
I'll see if I can help out in the GtkBuilder part though. (when gnome bugzilla loads, that is)
28 February 2009 at 17:58
After careful consideration, and a lot of discussions, bluez-gnome has its own fork in the shape of a revived gnome-bluetooth.
If you ever used bluez-gnome (and you probably have if you ever used Bluetooth on Linux), you'll be familiar with the solutions offered. Let me tell you about a few differences between bluez-gnome and gnome-bluetooth: No analyzers (or analysers) in gnome-bluetooth. Not really an end-user tool.We has widgets! We have a BluetoothChooser, and a BluetoothChooserButton exported in libgnome-bluetooth. Use libgnome-bluetooth-1.0.pc in your apps, and you're half-way to setting up Bluetooth in your app. We are stetic! UI problem? File a bug in the GNOME Bugzilla. You have GtkBuilder-fu? Help us move away from hard-coded widgets.Translators! Help! bluez-gnome was translated using Launchpad's Rosetta. While it was good for getting translations in the first place, it doesn't quite have the same level of community support the GNOME translations team(s) have.Integration! bluez-gnome had to cater for people that didn't want to use GNOME, or people that didn't like our approaches. Hopefully no silly options, or duplicated functionality in gnome-bluetooth.We still have a bit of work to be done before the first release, but it won't be too far off.
"We have a fork"
2 Comments -
Looking forward to having a rockin' experience of Bluetooth on GNOME
Can you also move the mailing list to GNOME infrastructure
28 February 2009 at 17:54
Translations are actually a downgrade, imho. Not a good point to list :)
I'll see if I can help out in the GtkBuilder part though. (when gnome bugzilla loads, that is)
28 February 2009 at 17:58