isa/gnome-shell
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
gnome-3-34
gnome-shell/.gitignore

84 lines
1.8 KiB
Plaintext
Raw Permalink Normal View History

Add .gitignore
2009-02-09 13:04:31 -05:00
*.la
*.lo
*.o
.deps
.libs
.gitignore: update for glib-gettext replacement
2011-05-27 10:58:18 -04:00
ABOUT-NLS
Add .gitignore
2009-02-09 13:04:31 -05:00
ChangeLog
INSTALL
aclocal.m4
autom4te.cache
data: Add README and supporting script to update keyboard layouts from CLDR The README describes the steps in detail, but most of it is abstracted away by the update-osk-layouts.sh script.
2017-11-10 09:26:48 -05:00
data/.osk-layout-workbench
data: merge gnome-shell.desktop and gnome-shell-wayland.desktop into one file We can autodetect what to do based on the user's session, so drop the separate desktop files. This, along with some future changes, will enable us to be bus activatable. https://bugzilla.gnome.org/show_bug.cgi?id=741666
2014-12-17 12:31:38 -05:00
data/org.gnome.Shell.desktop
data/org.gnome.Shell.desktop.in
Add a new tool, 'gnome-shell-extension-prefs', which can configure extensions A new tool, 'gnome-shell-extension-prefs' can load a new entry point from extensions, 'prefs.js', which has an entry point to return a GTK+ widget. This allows extensions to have their own preferences dialog, without each extension needing to ship its own Python script and .desktop file. https://bugzilla.gnome.org/show_bug.cgi?id=668429
2012-01-18 21:21:56 -05:00
data/gnome-shell-extension-prefs.desktop
data/gnome-shell-extension-prefs.desktop.in
theme: make a GResource Now that we have all the infrastructure ready, port the theme to a GResource. https://bugzilla.gnome.org/show_bug.cgi?id=736936
2014-09-18 22:24:46 -04:00
data/gnome-shell-theme.gresource
Migrate to GSettings Use GSettings for all Shell configuration. GConf is kept to read configuration from external programs (Metacity, Nautilus and Magnifier), but ShellGConf is removed because it's mostly useless for the few calls we still have. Also get rid of unused GConf code in ShellAppSystem. A basic GConf schema is still used to override Metacity defaults and configure Magnifier in a system-wide fashion. GConf is also used as GSettings backend via the GSETTINGS_BACKEND environment variable. All of this will be removed when these programs have been ported to GSettings and able to use dconf. GLib 2.25.9 is required. Schemas are converted to the new XML format, and compiled at build time in data/ so that the Shell can be run from the source tree. This also requires setting the GSETTINGS_SCHEMA_DIR environment variable both when running installed or from source tree, in src/gnome-shell.in and src/gnome-shell-clock-preferences.in. https://bugzilla.gnome.org/show_bug.cgi?id=617917
2010-05-05 17:05:42 -04:00
data/gschemas.compiled
Add a special background to use for performance testing Performance testing was producing inconsistent values at different times in the day since the GNOME default background is animated and sometimes has a single layer, and sometimes two blended layers. So we have consistent numbers, install a simple animated background with GNOME Shell that has 40-year long transition ending in 2030,a and set an environment variable in gnome-shell-perf-tool so that the background is override with that background. (The background depends on files installed by gnome-backgrounds; we assume that the person running performance tests is doing so within the scope of a full GNOME install.) https://bugzilla.gnome.org/show_bug.cgi?id=734610
2014-08-11 08:35:52 -04:00
data/perf-background.xml
Migrate to GSettings Use GSettings for all Shell configuration. GConf is kept to read configuration from external programs (Metacity, Nautilus and Magnifier), but ShellGConf is removed because it's mostly useless for the few calls we still have. Also get rid of unused GConf code in ShellAppSystem. A basic GConf schema is still used to override Metacity defaults and configure Magnifier in a system-wide fashion. GConf is also used as GSettings backend via the GSETTINGS_BACKEND environment variable. All of this will be removed when these programs have been ported to GSettings and able to use dconf. GLib 2.25.9 is required. Schemas are converted to the new XML format, and compiled at build time in data/ so that the Shell can be run from the source tree. This also requires setting the GSETTINGS_SCHEMA_DIR environment variable both when running installed or from source tree, in src/gnome-shell.in and src/gnome-shell-clock-preferences.in. https://bugzilla.gnome.org/show_bug.cgi?id=617917
2010-05-05 17:05:42 -04:00
data/org.gnome.shell.gschema.xml
data/org.gnome.shell.gschema.valid
gitignore: Add portal helper generated files
2014-07-08 10:13:01 -04:00
data/org.gnome.Shell.PortalHelper.desktop
data/org.gnome.Shell.PortalHelper.service
Update .gitignore
2015-02-20 20:37:59 -05:00
data/theme/.sass-cache
docs: Allow building API documentation As extensions.gnome.org starts to shape up, we should allow to build the API documentation for St/Shell. https://bugzilla.gnome.org/show_bug.cgi?id=661045
2011-09-07 14:23:28 -04:00
docs/reference/*/*.args
docs/reference/*/*.bak
docs/reference/*/*.hierarchy
docs/reference/*/*.interfaces
docs/reference/*/*.prerequisites
docs/reference/*/*.sgml
docs/reference/*/*.signals
docs/reference/*/*.stamp
docs/reference/*/*.txt
docs/reference/*/*.types
docs/reference/*/html/
docs/reference/*/xml/
remote-search: properly document the DBus interface Use real annotations in the XML, and use gdbus-codegen to extract those into docbook. We then include it in the Shell's gtk-doc. https://bugzilla.gnome.org/show_bug.cgi?id=689735
2012-12-05 14:37:57 -05:00
docs/reference/shell/doc-gen-*
Bluetooth status indicator Introduce the new Bluetooth indicator in the System Status area. It is written in JS with St and uses the new GnomeBluetoothApplet library. https://bugzilla.gnome.org/show_bug.cgi?id=618312
2010-07-24 07:57:53 -04:00
js/misc/config.js
Load JS from GResource Since gjs can now load JS from a GResource, compile it in the gnome-shell binary. This should be a bit faster, and make life easier with JHBuild.
2013-07-02 02:54:53 -04:00
js/js-resources.c
js/js-resources.h
.gitignore: Update to ignore the generated manpage
2012-11-07 08:38:32 -05:00
man/gnome-shell.1
Update .gitignore for i18n files
2009-08-18 18:19:16 -04:00
omf.make
po/*.gmo
.gitignore: add po/gnome-shell.pot
2010-02-15 08:34:33 -05:00
po/gnome-shell.pot
.gitignore: update for glib-gettext replacement
2011-05-27 10:58:18 -04:00
po/*.header
po/*.sed
po/*.sin
.gitignore: Update
2012-07-13 18:07:32 -04:00
po/.intltool-merge-cache
.gitignore: update for glib-gettext replacement
2011-05-27 10:58:18 -04:00
po/Makevars.template
Update .gitignore for i18n files
2009-08-18 18:19:16 -04:00
po/POTFILES
.gitignore: update for glib-gettext replacement
2011-05-27 10:58:18 -04:00
po/Rules-quot
Update .gitignore for i18n files
2009-08-18 18:19:16 -04:00
po/stamp-it
Add .gitignore
2009-02-09 13:04:31 -05:00
scripts/launcher.pyc
src/*.gir
src/*.typelib
src/*-enum-types.[ch]
src/*-marshal.[ch]
calendar-server: Add .desktop file for evolution calendar When selecting "Open Calendar" in the date menu, the configured application is launched via command line, so we don't get any startup notification. In order to fix the issue at least for our default calendar, add a hidden .desktop file for evolution's calendar component. https://bugzilla.gnome.org/show_bug.cgi?id=677907
2012-07-03 17:48:57 -04:00
src/calendar-server/evolution-calendar.desktop
.gitignore: update for calendar stuff
2011-03-01 10:09:56 -05:00
src/calendar-server/org.gnome.Shell.CalendarServer.service
Don't try to respawn metacity and the panel if we didn't kill them. Also, don't crash out of the python script if metacity-clutter crashes
2009-02-26 13:08:42 -05:00
src/gnome-shell
.gitignore: update for calendar stuff
2011-03-01 10:09:56 -05:00
src/gnome-shell-calendar-server
Add a new tool, 'gnome-shell-extension-prefs', which can configure extensions A new tool, 'gnome-shell-extension-prefs' can load a new entry point from extensions, 'prefs.js', which has an entry point to return a GTK+ widget. This allows extensions to have their own preferences dialog, without each extension needing to ship its own Python script and .desktop file. https://bugzilla.gnome.org/show_bug.cgi?id=668429
2012-01-18 21:21:56 -05:00
src/gnome-shell-extension-prefs
Update .gitignore
2013-09-12 17:28:23 -04:00
src/gnome-shell-extension-tool
trivial: update .gitignore
2011-07-13 14:59:22 -04:00
src/gnome-shell-hotplug-sniffer
.gitignore: add gnome-shell-perf-helper
2011-03-15 08:27:04 -04:00
src/gnome-shell-perf-helper
jhbuild wrapper: move performance measurement to a separate tool Introduce a new gnome-shell-perf-tool, which can be used instead of the old gnome-shell-jhbuild wrapper to gather data about gnome-shell performance and submit to shell-perf.gnome.org. This runs the shell with no extra setup beyond the WM_CLASS filter, so it can be used for a jhbuild setup or for an installed shell.
2012-04-12 13:43:08 -04:00
src/gnome-shell-perf-tool
gitignore: Add portal helper generated files
2014-07-08 10:13:01 -04:00
src/gnome-shell-portal-helper
trivial: update .gitignore
2011-07-13 14:59:22 -04:00
src/hotplug-sniffer/org.gnome.Shell.HotplugSniffer.service
Update .gitignore
2014-11-27 15:00:36 -05:00
src/org-gtk-application.[ch]
Add run-js-test executable to run tests ST makes use of GTK+ for input methods and for icon themes; therefore we have need to initialize GTK+ in order to test these parts of Clutter. Instead of LD_PRELOADING our module, use a separately compiled executable that links to the UI components in GNOME Shell, initializes Clutter and GTK+ and hooks them together. Getting all the symbols from St and the GUI components exported for use via GJS requires a bit of contortion: we need to actually link the St convenience library into a shared library and link the executable to that since there is no way with libtool to take a convenience library and put all its symbols into an executable --whole-archive style. https://bugzilla.gnome.org/show_bug.cgi?id=633657
2010-10-31 15:28:06 -04:00
src/run-js-test
Add a built-in screencast recording facility For development and demonstration purposes, it's neat to be able to record a screencast of gnome-shell without any external setup. Built-in recording can also give much better quality than is possible with a generic desktop recording, since we hook right into the paint loop. src/shell-recorder.[ch]: A general-purposes object to record a Clutter stage to a GStreamer stream. src/shell-recorder-src.[ch]: A simple GStreamer source element (similar to appsrc in the most recent versions of GStreamer) for injecting captured data into a GStreamer pipeline. src/test-recorder.c: Test program that records a simple animation. configure.ac src/Makefile.am: Add machinery to conditionally build ShellRecorder. tools/build/gnome-shell-build-setup.sh: Add gstreamer packages to the list of required packages for Fedora. js/ui/main.js: Hook up the recorder to a MetaScreen ::toggle-recording keybinding. http://bugzilla.gnome.org/show_bug.cgi?id=575290
2009-03-13 17:14:31 -04:00
src/test-recorder
src/test-recorder.ogg
Import stylesheet code from hippo-canvas Import: HippoCanvasTheme => StTheme HippoCanvasThemeImage => StThemeImage HippoCanvasStyle => StThemeNode StThemeContext is a new class managing the theme for a stage and global properties like resolution. test-theme.c is a newly written test program to do verification of the style matching and property handling rules. Various changes are made in the import: - Comprehensive reindentation - guint32 pixels replaced with ClutterColor - General pseudo-class support added - Old-fashioned (non-bordered) background image support added, though with no support for repeat, etc. - Bug fixes for problems revealed by test program https://bugzilla.gnome.org/show_bug.cgi?id=595990
2009-09-19 20:43:49 -04:00
src/test-theme
Don't generate st.h in a subdir For srcdir != builddir, in the builddir, the st/ subdirectory doesn't exist, so we can't generate st.h there. Just switch to building st.h directly in the current directory. (The other option would be to create a st/ subdirectory in the builddir if necessary; might be a little cleaner, but this works for now and gets things distchecking.)
2010-02-22 19:35:03 -05:00
src/st.h
Build: stop updating timestamp of st.h when not needed Use the same approach as other generated headers (a temporary file, compare to the existing, then copy), to avoid touching st.h, so that other dependent objects are not rebuilt, if not needed. It should speed up building when switching git branches, as often config.status or automake are run, causing Makefiles to be recreated. https://bugzilla.gnome.org/show_bug.cgi?id=638453
2011-01-01 10:20:34 -05:00
src/stamp-st.h
src/stamp-st.h.tmp
scroll-view-fade: Put the shader in another file This doesn't make any changes to the shader outside of adding a header; it simply makes changes in the future easier to edit. https://bugzilla.gnome.org/show_bug.cgi?id=689249
2012-11-28 16:07:25 -05:00
src/st-scroll-view-fade-generated.c
src/stamp-st-scroll-view-fade-generated.c
Add .gitignore
2009-02-09 13:04:31 -05:00
stamp-h1
Add some structure for interactive tests of UI components js/ui/environment.js: Split out initial UI setup (Tweener initialization, ClutterContainer monkey-patching) into a separate file we can import from tests. tests/: Directory for various types of tests tests/run-test.sh: Shell script that to run tests with an appropriate environment set up. tests/testcommon/: Common modules and data for tests tests/interactive/: Interactive tests tests/interactive/box-layout.js: A sample test of StLayout https://bugzilla.gnome.org/show_bug.cgi?id=595987
2009-09-18 15:51:15 -04:00
tests/run-test.sh
[.gitignore] Add *~, .patch
2009-10-15 21:44:13 -04:00
*~
*.patch
gitignore: ignore *.sw? files
2011-02-07 09:40:35 -05:00
*.sw?
Ignore '.vscode' folder for users of that editor https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/476
2019-04-02 13:37:31 -04:00
.vscode
Reference in New Issue Copy Permalink