Return-Path: From: Marcel Holtmann To: BlueZ development In-Reply-To: References: <1150540024.17539.20.camel@aeonflux.holtmann.net> Date: Sun, 18 Jun 2006 11:30:32 +0200 Message-Id: <1150623032.8816.7.camel@localhost> Mime-Version: 1.0 Subject: Re: [Bluez-devel] how to get service name and how to connect through it Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net Hi Jan, > i've already written that but I must reiterate that the main > reason people keep asking is that there's quite a big lack of > documentation. Even if you just want to write a small utility, you > have to study quite a lot of source code. Seems to me like some kind > of sport or what under linux (I'm more of a Windows guy). Or that's my > point of view at least. I know you try, to me writing a BlueZ app > seemed much like building a new car from parts where my only reference > is an already completed car. You can peak inside, see how they did it, > but in the end, you have to do a lot of tweaking and trying of > different combinations to make it work. And for example, I never got > an answer to why the HCI scanning routine (and the hctitool utility => > BlueZ) ignores my timeout value...also, there's lots of error codes > and nobody tells me what went wrong or why. for this reason we spent quite some time to design the the BlueZ D-Bus API. It makes it easy to do the basic tasks without knowing any details about the BlueZ internals or Bluetooth internals like HCI. And you can use it with C, C++, Python, Java, Mono etc. Regards Marcel _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel