From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Beautify about dialog
Date: Wed, 19 Dec 2007 00:22:17 +0100 [thread overview]
Message-ID: <1198020137.8050.203.camel@aeonflux> (raw)
In-Reply-To: <8a8adccc0712181352u1d802bfava194bf372cb5f232@mail.gmail.com>
Hi Jaap,
> > > > > > > > Attached patch does the following
> > > > > > > >
> > > > > > > > * about dialog code is simpler
> > > > > > >
> > > > > > > you can't use gtk_dialog_run for the applet's about dialog. It will
> > > > > > > block and thus block all PIN requests. The current code is this way for
> > > > > > > a reason.
> > > > > >
> > > > > > Didn't know that. I now use g_object_set which also reduces the amount
> > > > > > of code considerably.
> > > > >
> > > > > You can still use gtk_show_about_dialog(). It removes the close
> > > > > callback, and makes sure that only one dialogue shows up, and removes a
> > > > > lot of boiler-plate code (it doesn't use a separate main loop like
> > > > > gtk_dialog_run does). The gtk_dialog_run avoidance in the callbacks is
> > > > > still needed.
> > > >
> > > > not sure why I haven't done it that way. Maybe it was not available when
> > > > I wrote the initial version. However now the requirements are GTK 2.10
> > > > or later. So if we can simplify code, I am all for it.
> > > >
> > > Attached two patches
> > >
> > > One uses gtk-show-about-dialog
> >
> > fix the coding style for this one. I can already see that it messes up
> > the whitespaces. We use tabs and no whitespace in front of the ( in
> > function declarations.
>
> Attached patch with coding style fixup attached
I don't see the advantage of this patch. Especially with this ugly ifdef
for the program-name bug, I decided to not apply it. Especially the
license crap is not worth doing it. There is no need that the UI shows
the license in the about dialog.
You can still fill in the code for the URL and email hooks to make the
actually work. I didn't bother so far, because the default screen thing
seem to be wrong. You should use the screen where the actual about
dialog is present. However I am not so deep into GDK to tell what is the
correct way here.
Regards
Marcel
-------------------------------------------------------------------------
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
_______________________________________________
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-18 23:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 21:09 [Bluez-devel] [PATCH] Beautify about dialog Jaap A. Haitsma
2007-12-16 21:47 ` Marcel Holtmann
2007-12-16 22:43 ` Jaap A. Haitsma
2007-12-16 23:24 ` Bastien Nocera
2007-12-17 1:03 ` Marcel Holtmann
2007-12-17 7:15 ` Jaap A. Haitsma
2007-12-17 7:54 ` Jaap A. Haitsma
2007-12-17 10:43 ` Bastien Nocera
2007-12-17 19:04 ` Marcel Holtmann
2007-12-18 21:52 ` Jaap A. Haitsma
2007-12-18 23:22 ` Marcel Holtmann [this message]
2007-12-20 22:24 ` Jaap A. Haitsma
2007-12-17 0:58 ` 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=1198020137.8050.203.camel@aeonflux \
--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