_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Bastien,
> > I am a sensior software engineer of a Bluetooth Chip company in
> > Taiwan, ISSC. In our business plain of this year, we will like to
> > support Linux platform. Of course, bluez had completed most important
> > functions for users. However, for an end-user, the key issue to use a
> > bluetooth device in Linux is GUI interface. Today, Bluetooth's GUI
> > interface for end user is not friendly enough. We think it would be a
> > key problem to block our business. Hence, we think the first step for
> > our project will help bluez to complete the GUI interface.
> >
> > But with 2 weeks survey, I could not find out the TODO list in
> > bluez-gnome. I think the best way to complete the GUI interface is to
> > complete the TODO list in gnome-bluez, not write another software for
> > our company. Could anyone tell me where I could get a copy or
> > marcel/hadess could write a draft for us. Then, we could put our
> > resources in the right way.
>
> There's the opened bugs at:
> http://bugzilla.gnome.org/browse.cgi?product=bluez-gnome
>
> This is bugs filed by users as well as my personal TODO list. Most of
> those haven't been vouched by Marcel because he doesn't like Bugzilla
> and/or bugmail ;)
>
> My plan is to finish cleaning up the widgets, so that they're good
> enough to be exported, and I can kill gnome-bluetooth.
>
> I'm sure Marcel would be able to add some details to this.
short answer is that I want these GTK Bluetooth widgets and I want them
in their own library, but not at all costs. I must be happy with the API
before putting them in their own library.
Mihs, feel free to help Bastien. Every extra developer coding on this is
highly appreciated.
> > I think the first step is to complete the bluetooth-wizard since it's
> > important to add a device into bluez without console. Any plain for
> > this wizard?
>
> This would be a good thing to work on, but I'm not sure what Marcel's
> plans are for this yet.
I stopped with bluetooth-wizard, because we first need a good Passkey
Agent abstraction that we can use inside the applet and the wizard. This
however means that we have to clean the applet first. Remember that I
wrote the applet when everybody was screaming for a UI for the 3.x
series since I removed all unsecure hacks from hcid. This was basically
me using GTK+ after haven't touched any kind of UI code for over 6 years
or so.
The second thing is that we wanna have a generic Remote Device setup
inside the D-Bus API of hcid. This is works in progress and ultimately
leads to BlueZ 4.x. This will include a big D-Bus API change and a lot
of simplification. When we did the D-Bus API for BlueZ we were young and
inexperienced. That is not fully true. Johan and I played a lot with
D-Bus before and had a lot experience, but during the ongoing 3.x time,
we also realized that some stable parts of our current API are way to
complex.
Problem is however that we can't break the API of 3.x right now. We have
to go for a new major version. So that is works in progress and we are
talking two month here at most. Not longer. For most of the parts, I
know how I want them, but some minor things need to be discussed. Also
we have to write the additional code to make the new API actually do
something useful.
Hope that helps a little.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
On Tue, 2008-02-05 at 12:58 +0800, Ming-I Hsieh wrote:
> Hi, all
>
> I am a sensior software engineer of a Bluetooth Chip company in
> Taiwan, ISSC. In our business plain of this year, we will like to
> support Linux platform. Of course, bluez had completed most important
> functions for users. However, for an end-user, the key issue to use a
> bluetooth device in Linux is GUI interface. Today, Bluetooth's GUI
> interface for end user is not friendly enough. We think it would be a
> key problem to block our business. Hence, we think the first step for
> our project will help bluez to complete the GUI interface.
>
> But with 2 weeks survey, I could not find out the TODO list in
> bluez-gnome. I think the best way to complete the GUI interface is to
> complete the TODO list in gnome-bluez, not write another software for
> our company. Could anyone tell me where I could get a copy or
> marcel/hadess could write a draft for us. Then, we could put our
> resources in the right way.
There's the opened bugs at:
http://bugzilla.gnome.org/browse.cgi?product=bluez-gnome
This is bugs filed by users as well as my personal TODO list. Most of
those haven't been vouched by Marcel because he doesn't like Bugzilla
and/or bugmail ;)
My plan is to finish cleaning up the widgets, so that they're good
enough to be exported, and I can kill gnome-bluetooth.
I'm sure Marcel would be able to add some details to this.
> I think the first step is to complete the bluetooth-wizard since it's
> important to add a device into bluez without console. Any plain for
> this wizard?
This would be a good thing to work on, but I'm not sure what Marcel's
plans are for this yet.
Cheers
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel