Re: Opie bluetooth applet.

Dne čtvrtek 22 červen 2006 14:22 Dmitriy Korovkin napsal(a):
> Erik Hovland wrote:
> >On Wed, Jun 21, 2006 at 10:55:33PM +0400, Dmitriy Korovkin wrote:
> >>1. Why text file - not configuration file?
> >
> >The h2200 handheld can ship with 2 different bt chips. One requires
> > one type of config, one requires another.
> >
> >Slavek submitted a previous patch which determined the bt chip type by
> >directly reading the MTD device.
> >
> >That was unsatisfactory for familiar distros. So I asked Slavek to
> >submit a patch which read a common text file instead.
>
> I don't see a rason why.
>
Text file, because blueprobe from package blueproge generate this text 
file. I'm beginner in QT/Opie programming. I don't know, if is possible 
to use QSettings for reading from this configuration file?

> >>2. What to do with this file? How the user will configure it?
> >
> >Hopefully the distro will populate it (familiar does).
> >
> >If you know of another way to figure out this info, let me and Slavek
> >know.
>
> Yes, I know, I've implemented this in the Bluetooth Manager.
>
In Bluetooth Manager? Device "detection" is now in Bluetooth Applet. You 
move it into Manager? Where we can see your solution?

> >>Don't make O[pie] useless and let all "Linux coolest boys" say that
> >>Linux on handhelds is just a toy - not a functional system like
> >> WinCE. Thanks for understanding,
> >
> >These are very strong words to someone who is only trying to help and
> >has been quite responsive. If you missed the previous thread on this,
> >please go look for it in the archives. But Slavek is only trying to
> > help and he is doing something I asked him to do.
>
> Yes, but it's the reality. I've spent a lot of time to fix many
> problems.
>
> >If it is unsatisfactory, please propose other options.
> >
> >E
>
> Ok, (If you wish to listen, of course). The best way to do something -
> to get a clear understanding what are we going to do, next - make a
> plan of actions, then do implementations, and again and again and
> again. This is a practice I'm trying to follow by discussing my
> solutions with community members.
> What I currently see in BT system - a lot of "patch and fix". Bt obex
> that doesn't seem to receive, Manager that did (now it does something)
> nothing.
> This is the only way to make a good software.
> Otherwise OPIE will be "just a toy for babies".
> Dmitriy.

When I found, that I cannot enable BT by applet, I try to find, how I can 
help. I find, that BT detection is in Bluetooth Applet. Next I create 
patch, that add support for H2200 - this not need planning, this is 
simple patch, that add support for newer device and corresponding with 
other implementations.

My next question has been "for planning": "Why applet not try to use 
informations from /etc/sysconfig/bluetooth?" Answers: "Actually that is a 
good idea." and "May be this is a good idea." Then I was create patch, 
that implement this and submit it for discussion about this solution. It 
is wrong way?

Note: I never have been using PDA with WinCE. WinCE is not "functional" 
system - PDA with WinCE is only toy for playing. This is not for me. I 
use PDAs only with Opie (and sometimes try to use GPE).

Slavek
_______________________________________________

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

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