From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [Bluez-devel] Big rename for the D-Bus API From: Marcel Holtmann To: bluez-devel@lists.sourceforge.net In-Reply-To: <20060227073835.GA16640@localhost.localdomain> References: <1141022379.823.2.camel@localhost> <20060227073835.GA16640@localhost.localdomain> Content-Type: text/plain Message-Id: <1141030661.823.17.camel@localhost> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 27 Feb 2006 09:57:41 +0100 Hi Johan, > > I just came to the conclusion that using org.bluez.Device for the local > > attached Bluetooth dongles etc. is not a good name. I would prefer to > > use org.bluez.Adapter and start renaming everything before the next > > release. Any comments? > > I'm fine with that. The current naming is because of the "let's imitate > hald interface" decision. However, if you change "Device" to "Adapter", > then I think that the methods and signals in the Manager path should > also change to using Adapter instead of Device (currently we have > ListDevices, DefaultDevice, DeviceAdded and DeviceRemoved). it's done now. The only leftover thing is to rename dbus-device.c into dbus-adapter.c and then proceed. And we maybe need to update some function names, but that's totally internal. Regards Marcel ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel