From: "Chris Rivera" <crivera@novell.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] [RESEND] make bluez GNOME UIs singletons
Date: Sun, 16 Dec 2007 22:08:52 -0500 [thread overview]
Message-ID: <5f84803c0712161908l4816cf93y7eebeed73064d0ed@mail.gmail.com> (raw)
In-Reply-To: <5f84803c0712060959n6db58e78y4adfa1b4a212df71@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2004 bytes --]
Anyone? Anyone?
On Dec 6, 2007 12:59 PM, Chris Rivera <chrismrivera@gmail.com> wrote:
> Attached is an updated patch with the changes that we talked about.
>
> Chris
>
>
> On Dec 3, 2007 11:59 AM, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> > 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.
> >
> >
>
[-- Attachment #1.2: Type: text/html, Size: 3187 bytes --]
[-- Attachment #2: Type: text/plain, Size: 308 bytes --]
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
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-17 3:08 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
2007-12-06 17:59 ` Chris Rivera
2007-12-17 3:08 ` Chris Rivera [this message]
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=5f84803c0712161908l4816cf93y7eebeed73064d0ed@mail.gmail.com \
--to=crivera@novell.com \
--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