After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 622544 - Port capplet to be a control center 3.0 panel
Port capplet to be a control center 3.0 panel
Status: RESOLVED WONTFIX
Product: vino
Classification: Applications
Component: Preferences Dialog
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Vino Maintainer(s)
Vino Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-06-23 22:48 UTC by Frederic Peters
Modified: 2011-03-04 19:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
port vino-prefrences to be a control center panel (18.50 KB, patch)
2010-06-23 22:49 UTC, Frederic Peters
none Details | Review

Description Frederic Peters 2010-06-23 22:48:56 UTC
The attached patch ports vino-preferences to be a control center 3.0 panel.
Comment 1 Frederic Peters 2010-06-23 22:49:29 UTC
Created attachment 164451 [details] [review]
port vino-prefrences to be a control center panel
Comment 2 Jonh Wendell 2010-06-25 23:49:49 UTC
I'm not sure about doing such change... What about distros that won't ship gnome 3 or gtk+ 3.0?

Is it already decided that all capplets will change to this format?

Perhaps the right thing to do would be to add an configure option, say, '--with-control-center' to build a control center module instead of a binary. Thus modern distributors will choose this option, while conservative ones would choose to stay with the binary.
Comment 3 William Jon McCann 2010-10-12 07:52:20 UTC
If vino is to be part of the GNOME 3 core we need to make this change.

We aren't designing the GNOME 3 core for distros to pick and choose which parts they'll use.
Comment 4 William Jon McCann 2011-03-04 17:18:58 UTC
Since my last comment we've revised the plan.  I think it makes sense to design this as part of the Privacy & Sharing panel that we're planning for 3.2.  So, this isn't a 3.0 blocker.  And in fact probably should be marked wontfix.
Comment 5 David King 2011-03-04 17:30:40 UTC
Thanks for your input Jon. Is there any reference for the Privacy and Sharing panel planning that you mentioned? I don't have any strong opinions, but I'd like to be kept in the loop about future changes.
Comment 6 William Jon McCann 2011-03-04 17:47:41 UTC
Hi David.  Sure, we didn't get close to finishing for 3.0 but some of the work is here: http://live.gnome.org/Design/SystemSettings/PrivacyAndSharing

Are you one of the vino maintainers we should be working with next cycle?  Thanks.
Comment 7 David King 2011-03-04 18:44:27 UTC
(In reply to comment #6)
> Hi David.  Sure, we didn't get close to finishing for 3.0 but some of the work
> is here: http://live.gnome.org/Design/SystemSettings/PrivacyAndSharing

Ah, seems useful, I look forward to seeing some progress once 3.0 is out the door. Bookmarked, thanks.

> Are you one of the vino maintainers we should be working with next cycle? 
> Thanks.

Yes, Jonh Wendell recently handed over maintainership of Vinagre and Vino to me. I have a few plans queued up for Vino 3.2, but nothing that should impact these UI changes, which are more important for users.
Comment 8 William Jon McCann 2011-03-04 19:03:47 UTC
Cool.  Will certainly be talking with you then.  BTW, you should teach bugzilla that you are a maintainer of this module :)  I think you can do that in the Admin options or something.  Or maybe Jonh has to...