Hi Eric,
Well, if you could release the source for IOBluetoothUIUserLib, that
would go a long way to understanding how to use the stack and SDK
libraries - or do these library routines call nonpublic APIs like the
Inquiry code?
We have not released any public API to do inquiries. When we release public APIs we are forced to support them forever. We could not get this API finished in time with the needed polish to be able to support it now and forever. We figured 99% of the cases out there would be happy with the panels we provide, and so far this has been found to be true. Also, I'm not really sure giving you the source to that file would go far in helping you understand the stack, and would only make it worse for us because we could not change the underpinnings without worrying about breaking some code that you wrote based on assumptions made by reading the code. Finally, the panels really only return you a Bluetooth device or service representation, so even if you could look at that code, it isn't going to tell you how to use the stack with those objects, which is really what you are trying to do. You'd still need to read the headerdoc and look at the samples to see how those objects are used to communicate over Bluetooth. If you have specific questions about how to get started using one of these objects, etc. please let us know and we'll try and help as much as possible. It also would help to know a little about what you are trying to accomplish in your project and what protocol you intend to use (OBEX, RFCOMM, L2CAP, etc.).
I guess I was wondering if I wanted to write an app without a GUI, how
I would find devices without using the various service and device
selector panels? But what you're saying is that "Apple have create GUI
based utilities for inquiring about remote devices."
You are correct - you could not do it. You will need to display a panel at some point for the user to select a device/service. Unless you wanted to use the raw device address, which is less than optimal. We do hope to release an API to do this. If the lack of this API this is absolutely prohibitive to what you are trying to do, let us know and we'll escalate its importance on the to-do list.
By cover functions do you mean that the C API can be used instead of
the objc API or are the C routines needed in addition to the objc API?
On the other hand can I stay entirely in the objc API for the most part?
What he meant was that we have written pretty much everything in objc, and that we have put a C convenience wrapper around it. So, you should be able to do everything with the Bluetooth stack in pure C or objc, and never have to mix the two. If you find this is not the case, please let us know so we can fill the gap. I hope that helps clarify a few things, Jason bubba@apple.com
On Wednesday, November 13, 2002, at 06:23 AM, Eric Kolotyluk wrote:
I've been spending the last couple of days trying to follow the
RFCOMMClientSample applications in the Bluetooth Examples directory,
but cannot find the source for IOBluetoothUIUserLib. In particular,
the
examples are incomplete without access to the source of procedures
like
IOBluetoothServiceBrowserControllerCreate.
Is the source for IOBluetoothUIUserLib buried somewhere in the SKD, or
can it be made available for study? This would help in trying to
understand the SDK.
Those are all library routines for which we do not supply source. Its
the same as say NSOpenPanel.
Also, are there any plans to release some more comprehensive design or
architectural documentation on the SDK, perhaps a developers guide?
That is definitely in the plans. For now, the best source of
information is the headerdoc. Especially the objc class descriptions.
There should be quite a bit of information about the individual
classes in there. For the most part, the C API provides cover
functions for the objc objects and methods.
Finally, there do not seem to be any services for directly invoking an
Inquiry of remote devices. Can I assume that this is a function of the
underlying O/S? It's not clear how I actually discover what other
remote devices are out there - is it via the local discovery services?
That's that's why it would be nice to see the source code for
IOBluetoothUIUserLib.
Currently, there is no public API for performing inquiries. Do you
need functionality beyond what is in the various service and device
selector panels?
_______________________________________________ bluetooth-dev mailing list | bluetooth-dev@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.