Re: [Bluez-devel] [gbluezconf] D-Bus client prototype

[Marcel Holtmann <marcel@holtmann.org>]

Hi Claudio,

> > For the device icons you should contact the Tango team or the Gnome Art
> > team. Maybe they will come up with some.
> >
> > The program should start even if no Bluetooth adapter would be found. In
> > this case only "About" and "Quit" should be visible.
> 
> I think it's better disable the options instead of remove the menu
> item from the popup menu.

I would prefer to switch the visibility off, but you might check the
Gnome HIG guidelines for this.

> > For the configuration dialog and multiple adapters we should maybe use
> > the proposal from the bluetool screenshot (attached). I think it should
> > include a page for default/common settings for all devices. And then
> > some device specific parts that should have an extra check-box to
> > activate their settings or use the common ones.
> 
> Ok I will analize the bluetool approach. Multiple adapter is not a
> common scenario. Therefore we need avoid display unnecessary infos. I
> try re-design the "Configuration" dialog to make it more
> user-friendly.

I think that I gave this comment already. Having multiple adapters is
the normal situation. The special case is only one adapter. You can't
view it other way around.

> > Don't forget to make the device name and class of device configurable.
> 
> Device name changes is already possible. However change the device
> class is not possible at the momment. We can extend the D-Bus services
> soon.

We should extend, but only major and minor class. Not the services
classes, because they will depend on the registered services. Feel free
to send me a patch for it.

> > The search dialog shouldn't always start with zero devices if a previous
> > inquiry has already taken place. However I think for this we need to
> > implement a device cache inside hcid that could be requested up-front.
> 
> When the kernel/userspace communication interface becomes available we
> can improve this dialog. The remote name needs be improved too, we can
> use the textfile_get function to  retrieve cached remote names.

We can do already now if we know what is needed. Getting access to the
cached devices names must go also through D-Bus and actually I prefer to
make the name part of the device information. Proposals are welcome.

> > Besides the inactivity of the icon if no adapter is attached or if no
> > adapter is up, we maybe should change the icon if we have an active ACL
> > link. We can also use a different icon or animation if the device is
> > running an inquiry.
> 
> I try suggest new icons for address these cases next year.

Anyone from the Tango or Gnome Art team reading this mailing list?

> > What do you think about creating an own CVS repository for it.
> 
> Do you mean create a new CVS root in BlueZ CVS repository? If yes, go ahead.
> Currently, I am storing in my internal subversion server, but it's
> better provide a public access.

I will try to setup a repository for it next week, but be aware of that
the directory layout would be changed a lot ;)

> I will be on vacation until jan/15th. For D-Bus issues you can contact Eduardo.
> For GBluezConf, I will return the activities in the next year only.

Happy vacation.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel