From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] [RESEND] make bluez GNOME UIs singletons
Date: Mon, 03 Dec 2007 17:59:41 +0100 [thread overview]
Message-ID: <1196701181.12292.128.camel@violet> (raw)
In-Reply-To: <5f84803c0712030850k5810ee43na4a13f5e74657388@mail.gmail.com>
Hi Chris,
>
> I meant to look into it, but never got around it. Some small
> comments
> about it. Don't make the applet a singleton. That is totally
> unneeded
> since the applet will be loaded at login.
>
> I still think it should be a singleton. You wouldn't ever want two
> applets running unless you're testing, and we have the singleton flags
> for that. I don't think this hurts anything.
I am okay with that. Please abstract everything into common/. And don't
forget to document it in the manual pages.
> For the "Present" method. Don't use the D-Bus low-level calls.
> It should
> be all dbus-glib. Which means we have to abstract that into an
> object. I
> don't know if there is a well defined way for this. If it is,
> it might
> be good to use that. If not, then propose something for
> freedesktop.org.
>
> I thought about doing this, but it seems like overkill to define a
> GObject to just expose one method. GObject isn't exactly terse
> either.
In a simple way you can use GObject for it. It is better than using the
low-level D-Bus calls.
> And we should probably have some generic methods inside
> common/ instead
> of doing it again in every program.
>
> Please follow the kernel coding style. I know it is odd for a
> GTK
> application, but it makes it a lot easier for me.
>
> Which parts of the patch violate the kernel coding style? The
> function parameter spacing?
Mainly the spacing.
Regards
Marcel
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-12-03 16:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 15:33 [Bluez-devel] [PATCH] [RESEND] make bluez GNOME UIs singletons Chris Rivera
2007-12-03 16:25 ` Marcel Holtmann
2007-12-03 16:50 ` Chris Rivera
2007-12-03 16:59 ` Marcel Holtmann [this message]
2007-12-06 17:59 ` Chris Rivera
2007-12-17 3:08 ` Chris Rivera
2007-12-17 5:47 ` Marcel Holtmann
2007-12-17 15:54 ` Chris Rivera
2007-12-17 18:53 ` Marcel Holtmann
2007-12-17 19:29 ` Chris Rivera
2007-12-17 20:17 ` Marcel Holtmann
2007-12-17 20:47 ` Chris Rivera
2007-12-17 21:01 ` Marcel Holtmann
2007-12-18 18:37 ` Chris Rivera
2007-12-18 19:10 ` Marcel Holtmann
2007-12-18 19:51 ` Chris Rivera
2007-12-18 19:58 ` Marcel Holtmann
2007-12-18 20:52 ` Bastien Nocera
2007-12-18 21:00 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1196701181.12292.128.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox