This sounds good.
I have already spend some thoughts about an easy-to-build, easy-to-use solution. If we devide this in some pieces, we can use little steps to reach this goal.
First, we need drivers for the Bluetooth-hardware. Most BT-hardware are built by USB-devices, some as serial attached devices (mostly older hardware or PCcard/ compactFlash-Hardware). We should concentrate on USB-Devices - even BT-hardware thats build in laptops is accessed by USB (Thinkpads etc). An USB-driver for the HCI-interface, that doesn't distinguish between the different USB-Vendor or Model-numbers ist what we need first. Most BT-USB-Dongles outthere are based on CSR-chips Bluecore 2-5 or at ISSC-chips.
We need also a ported bluez-stack (http://www.bluez.org
). So we can use an established and testet BT-stack.
We also need dummy-drivers to projecting our BT-device and its BT-profiles in the legacy hardware. Such as Com-ports, LAN-ports, audioports.
on top of this, we need a simple GUI to manage our BT-devices, the BT-Profiles, the BT-connections with PINs ... something like USBcfg ..
I think, thats the fasted and easiest way to an Bluetooth-solution.
And with it completed, we have access to hardware like keyboards, mices, sound In/ouput, LAN-connections, Modems, mobile phones, serial ports, printers, ... sounds like a huge blast for the hardware compatibility list.
Unfortunately, my programming skills are near zero, my last program was written in Clipper (an dbase3+compiler). But I can help with BT-Hardware.
Maybe we should open a bounty?