Bluetooth GUI Discussion - Revision history

Vater: moved BlueTooth GUI Discussion to Bluetooth GUI Discussion

2012-07-29T22:54:21Z

moved BlueTooth GUI Discussion to Bluetooth GUI Discussion

Vater: categorize as :category:Bluetooth

2012-07-29T22:53:44Z

categorize as category:Bluetooth

Vater at 20:03, 12 July 2012

2012-07-12T20:03:24Z

Kenmoore: Add comments for current Bluetooth GUI status.

2012-02-03T14:14:34Z

Add comments for current Bluetooth GUI status.

Tigersharke: /* Other resources */

2012-02-02T22:11:22Z

‎Other resources

Tigersharke at 22:04, 2 February 2012

2012-02-02T22:04:33Z

Tigersharke: /* There is such things which need to be used: */

2012-01-28T05:38:01Z

‎There is such things which need to be used:

Tigersharke at 05:36, 28 January 2012

2012-01-28T05:36:51Z

Yerenkow at 11:16, 9 July 2009

2009-07-09T11:16:20Z

Yerenkow: New page: We have a decent network GUI. I think we should start thinking of BlueTooth GUI. There is such things which need to be used: hcsecd - control link keys and PIN codes for Bluetooth devices ...

2009-07-09T11:15:05Z

New page: We have a decent network GUI. I think we should start thinking of BlueTooth GUI. There is such things which need to be used: hcsecd - control link keys and PIN codes for Bluetooth devices ...

New page

We have a decent network GUI.
I think we should start thinking of BlueTooth GUI.
There is such things which need to be used:
hcsecd - control link keys and PIN codes for Bluetooth devices
sdpd - Bluetooth Service Discovery Protocol daemon
hccontrol - HCI configuration utility
obexapp - executable, OBEX protocol.

Here is a list of requirements to GUI, in no particular order:

Gui should ...

. show (indicate) that kernel module ng_ubt is loaded
. allow load (unload) ng_ubt;
. show (add/remove) ng_ubt_load in /boot/loader.conf
. show status (and start/stop/restart) hcsecd service;
. show (add/remove) hcsecd_enable in /etc/rc.conf
. have a tree with such structure: Devices--Device1(Service1, Service2...)
. have an ability to scan (search for devices), show which is known devices, which is new
. add device to /etc/hcsecd.conf, edit pin, name, etc;
. allow to add (edit/delete) ppp records, to use device as modem
. allow to connect/disconnect device to internet via rfcomm_ppp
. If device (mobile phone) have ability to FTRN, this service should expand to device's FS;
. Device's FS tree should support drag-n-drop, at least to other tree, which is for local FS (Ideally to any other external filemanager, like dolphin, or else)

← Older revision		Revision as of 22:53, 29 July 2012
Line 38:		Line 38:
	=== Other resources ===		=== Other resources ===
	* [http://www.freebsd.org/cgi/url.cgi?ports/comms/hcidump/pkg-descr hcidump] - similar in function to tcpdump but for bluetooth.		* [http://www.freebsd.org/cgi/url.cgi?ports/comms/hcidump/pkg-descr hcidump] - similar in function to tcpdump but for bluetooth.
		+
		+	[[category:Bluetooth]]

@@ Line 1: / Line 1: @@
 {{NavHome}}
 We have a decent network GUI.
 I think we should start thinking of BlueTooth GUI.
 === There is such things which need to be used: ===
 # hcsecd - control link keys and PIN codes for Bluetooth devices
 # sdpd - Bluetooth Service Discovery Protocol daemon
@@ Line 33: / Line 36: @@
 * Device's FS tree should support drag-n-drop, at least to other tree, which is for local FS (Ideally to any other external filemanager, like dolphin, or else)
-===Other resources===
+=== Other resources ===
-[http://www.freebsd.org/cgi/url.cgi?ports/comms/hcidump/pkg-descr hcidump] - similar in function to tcpdump but for bluetooth.
+* [http://www.freebsd.org/cgi/url.cgi?ports/comms/hcidump/pkg-descr hcidump] - similar in function to tcpdump but for bluetooth.

@@ Line 12: / Line 12: @@
 Gui should ...
 * show (indicate) that kernel module ng_ubt is loaded
 * allow load (unload) ng_ubt;
 * show (add/remove) ng_ubt_load in /boot/loader.conf
 * show status (and start/stop/restart) hcsecd service;
 * show (add/remove) hcsecd_enable in /etc/rc.conf
 * have a tree with such structure: Devices--Device1(Service1, Service2...)
 * have an ability to scan (search for devices), show which is known devices, which is new
 * add device to /etc/hcsecd.conf, edit pin, name, etc;
 * allow to add (edit/delete) ppp records, to use device as modem
 * allow to connect/disconnect device to internet via rfcomm_ppp

← Older revision		Revision as of 22:11, 2 February 2012
Line 26:		Line 26:

	===Other resources===		===Other resources===
−	[http://www.freebsd.org/cgi/url.cgi?ports/comms/hcidump/pkg-descr hcidump]	+	[http://www.freebsd.org/cgi/url.cgi?ports/comms/hcidump/pkg-descr hcidump] - similar in function to tcpdump but for bluetooth.

← Older revision		Revision as of 22:04, 2 February 2012
Line 24:		Line 24:
	* If device (mobile phone) have ability to FTRN, this service should expand to device's FS;		* If device (mobile phone) have ability to FTRN, this service should expand to device's FS;
	* Device's FS tree should support drag-n-drop, at least to other tree, which is for local FS (Ideally to any other external filemanager, like dolphin, or else)		* Device's FS tree should support drag-n-drop, at least to other tree, which is for local FS (Ideally to any other external filemanager, like dolphin, or else)
		+
		+	===Other resources===
		+	[http://www.freebsd.org/cgi/url.cgi?ports/comms/hcidump/pkg-descr hcidump]

← Older revision		Revision as of 05:36, 28 January 2012
Line 1:		Line 1:
		+	{{NavHome}}
	We have a decent network GUI.		We have a decent network GUI.
	I think we should start thinking of BlueTooth GUI.		I think we should start thinking of BlueTooth GUI.