_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Marcel Holtmann wrote:
> Hi Fabien,
>
>> I have a (kind of) formal request to ask to the Bluez project.
>>
>> I'm basically trying to use the Bluez API to design a user friendly
>> device that will have bluetooth functionnality.
>> Speeking of a user friendly device, i'm thinking of two things i wanna have:
>> - the end user bluetooth feature should work most of the time, which
>> means it will have to be robust and not throw errors most of the time.
>> - When something goes wrong, the end user should only be presented
>> with error messages he can understand and actually act upon. If the
>> message is too cryptic, then a generic placeholder would be use instead
>> of a low level message. One of the first non cryptic messages i think of
>> would be a "Device unreachable : please check your bluetooth device is
>> powered on" message :-)
>
> feel free to improve the error messages. We haven't spend enough time
> with them yet. There were other issues that needed to be addressed
> first. Also the error support should made generic and reside in common/.
> So if you wanna work on it, send patches.
Hi Marcel,
I didn't though error handling was that bad. :-(
And... yes i volunteer to work on this, so i'm gonna start to work on
generic error support in common/. :-)
Cheers,
Fabien
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Fabien,
> I have a (kind of) formal request to ask to the Bluez project.
>
> I'm basically trying to use the Bluez API to design a user friendly
> device that will have bluetooth functionnality.
> Speeking of a user friendly device, i'm thinking of two things i wanna have:
> - the end user bluetooth feature should work most of the time, which
> means it will have to be robust and not throw errors most of the time.
> - When something goes wrong, the end user should only be presented
> with error messages he can understand and actually act upon. If the
> message is too cryptic, then a generic placeholder would be use instead
> of a low level message. One of the first non cryptic messages i think of
> would be a "Device unreachable : please check your bluetooth device is
> powered on" message :-)
feel free to improve the error messages. We haven't spend enough time
with them yet. There were other issues that needed to be addressed
first. Also the error support should made generic and reside in common/.
So if you wanna work on it, send patches.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel