A fork of Gnome-control-center with some tweaks
Find a file
Georges Basile Stavracas Neto b64c605e69 network: Update Proxy section widgets
According to the lastest mockups [1], the Proxy section is now
composed of a row with the state of the proxy, and a settings
button that leads to a dialog where one can configure the different
proxy settings.

This commit ports the current code to do that, and various changes
took place to made this happen. Namely:

 * A new ProxyMode enum was added to improve readability and
   improve the semantic of the code. No more random numbers
   are present.

 * The current widgets for editing proxy settings were repacked
   into a GtkStack (so that we keep an homogeneous sizing), and
   the GtkStack itself was moved into a new dialog. With that,
   we can just set the stack page, rather than controlling the
   visibility of all individual widgets.

 * Many unused widgets were removed.

 * The combo box was replaced by 3 radio buttons. Now, there's
   no need to deal with GtkTreeIters anymore. Another refactoring
   of the code that led to more readable and smaller code.

Overall, these changes made the code be more readable, smaller
codebase with a smaller surface for mistakes.

https://bugzilla.gnome.org/show_bug.cgi?id=785581
2017-08-09 19:32:43 +02:00
libgd@752f65e91e datetime: 12h time format is now always available 2017-04-03 11:32:43 +02:00
m4 info: Get renderer from gnome-session under Wayland 2016-10-18 16:11:30 +02:00
man man: Drop obsolete region arguments 2013-02-19 17:58:33 +01:00
panels network: Update Proxy section widgets 2017-08-09 19:32:43 +02:00
po Update Indonesian translation 2017-08-09 09:31:43 +00:00
search-provider build: create another executable for the new layout 2016-06-03 12:32:36 -03:00
shell project: Switch to the new shell 2017-08-09 19:31:41 +02:00
.gitmodules build: Drop EggListBox 2013-07-02 16:19:09 +01:00
AUTHORS New and better than ever in a new home 1998-12-08 20:47:55 +00:00
autogen.sh build: Remove PKG_NAME from autogen.sh 2015-10-19 11:19:17 +02:00
ChangeLog Automatically create the ChangeLog file from VCS history 2009-11-14 15:17:28 +00:00
configure.ac build: Require gnome-settings-daemon 3.25.90 2017-08-09 19:28:08 +02:00
COPYING build: Update COPYING with new mailing address 2012-08-22 15:33:18 +01:00
git.mk Update .gitignore and libgd 2013-10-17 15:01:38 -04:00
gnome-control-center.doap doap: add <programming-language> 2014-07-31 18:56:39 +02:00
MAINTAINERS MAINTAINERS: Point to doap file instead 2017-05-18 17:43:04 +02:00
Makefile.am Makefile: Move to AM_DISTCHECK_CONFIGURE_FLAGS 2016-04-04 21:47:27 -07:00
Makefile.decl build: Add GTest Makefile snippet 2016-06-10 15:04:44 +02:00
NEWS 3.25.4 2017-07-18 22:56:26 +02:00
README README: Update link to how-to submit patches wiki page 2017-02-08 18:33:56 +01:00
update-from-gsd.sh wacom: Move update-from-gsd.sh to root 2012-04-19 12:01:14 +01:00

GNOME Control Center  
====================

About -

The control center is GNOME's main interface for configuration of various
aspects of your desktop.

Installation -

See the file 'INSTALL'

How to report bugs -

Bugs should be reported to the GNOME bug tracking system under the product
gnome-control-center. It is available at http://bugzilla.gnome.org.

In the report please include the following information -

	Operating system and version
	For Linux, version of the C library
	How to reproduce the bug if possible
	If the bug was a crash, include the exact text that was printed out
	A stacktrace where possible [see below]

How to get a stack trace -

If the crash is reproducible, it is possible to get a stack trace and 
attach it to the bug report. The following steps are used to obtain a 
stack trace -
	
	Run the program in gdb [the GNU debugger] or any other debugger
		ie. gdb gnome-keyboard-properties
	Start the program
		ie. (gdb) run
	Reproduce the crash and the program will exit to the gdb prompt
	Get the back trace
		ie. (gdb) bt full

Once you have the backtrace, copy and paste this either into the 
'Comments' field or attach a file with it included.


Patches -

Patches should be submitted to bugzilla.gnome.org or emailed to the 
gnomecc-list@gnome.org list. If using bugzilla, attach
the patch to a new bug report [or preferably, check to see if there is
already a bug report that corresponds to your patch]. Bug reports 
containing patches should include the 'PATCH' keyword.

See https://wiki.gnome.org/Newcomers/CodeContributionWorkflow for how to
create patches.