Re: [Fwd: Re: Another 1.2.3 candidate bug - #1838]

Hello Dmitriy,

Tuesday, February 13, 2007, 8:35:45 AM, you wrote:

> Rene, Erik,
> Let me try to explain the situation:
> Bluetooth Manager (noncore/net/opietooth/manager), accompanied by
> noncore/net/opietooth/lib is the application that is a configuration
> tool that allows you to edit /etc/bluetooth/hcid.conf and
> /etc/bluetooth/rfcomm.conf with the proper GUI. It also allows you to
> scan and discover BT devices.
> Now the provided patch adds another configuration file:
> /etc/sysconfig/bluetooth.

  Nope, it doesn't add it. It already exists as system config.

> My oppinion: if we have one more conf file, we
> need to provide a tool that allows us, (not us, we know how to do this
> -- a user) to configure it.

  Patches welcome ;-).

>  This means that we need another dialog box
> in the BT manager.
> This is my idea.

  Yes, but it puts too big requirements on BT manager maintainer ;-).
I offer simple organizational solution for such kind of problems:
user-level configs better be edited in GUI, system-level - highly
optionally.



  Anyway, now that we spoke of Bluetooth at all, Dmitriy, is there
somewhere list of 3rd party requirements for OPIE Bluetooth support?
Like, what versions of bluez, different obex tools, etc., it expects?
I didn't find such info from http://opie.handhelds.org/cgi-bin/moin.cgi/OpieBluetooth
(but surprisingly I found that BT applet "Takes configuration for BT
device from /etc/sysconfig/bluetooth")



> Regards,

> Dmitriy


[]

-- 
Best regards,
 Paul                            mailto:[email protected]

_______________________________________________

http://opie.handhelds.org/cgi-bin/moin.cgi/DeveloperWikiIndex

Opie-devel mailing list
[email protected]
https://handhelds.org/mailman/listinfo/opie-devel