DOCSLIB.ORG

¿Quién Escribe GNOME?

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
¿Quién Escribe GNOME? GNOME es un proyecto para disponer de un escritorio libre de alta calidad y usabilidad Prehistoria 1992 1995 Agosto, 1997 (cc) Pedro Villavicencio, 2008 Fundado por Miguel de Icaza y Federico Mena Marzo 3, 1999 GNOME 1.0 Primera versión “estable” 565 días 260.748 líneas de código C (93,8% del código de las bibliotecas) 171* colaboradores (núcleo oficial de las bibliotecas) Principales colaboradores* Desarrollador Añadidas Eliminadas Cambios Tim Janik 153,057 97,202 551 Owen Taylor 157,536 61,260 476 Elliot Lee 172,693 12,179 398 Arturo Espinosa 59,481 27,142 392 Raph Levien 61,988 5,054 150 Daniel Veillard 54,474 6,984 54 Federico Mena Quintero 46,086 17,315 329 Manish Singh 32,898 21,621 187 * En el desarrollo de lo que posteriormente llegó a ser GNOME Platform Octubre 12, 1999 GNOME 1.0.55 223 días después “October” GNOME Primera versión realmente estable 1999 Eazel y otras compañías Mayo 25, 2000 GNOME 1.2 226 días después 86* colaboradores Principales colaboradores* Desarrollador Añadidas Eliminadas Cambios Daniel Veillard 153,182153182 49,05249052 125 Owen Taylor 13,07913079 23,35723357 116 Martijn van Beers 231 32,68332683 2 James Henstridge 21,74121741 4,8644864 95 Tim Janik 11,55511555 3,6083608 101 Tony Gale 10,28010280 4,3184318 14 Elliot Lee 2825 8313 119 Elliot Lee 2,825 8,313 119 Manish Singh 8964 4076 21 Manish Singh 8,964 4,076 21 * En el desarrollo de lo que posteriormente llegó a ser GNOME Platform Agosto, 2000 GNOME Foundation Sun Microsystems adopta GNOME para SolarisOS HP adopta GNOME para HP/UX IBM contribuye con SashXB RAD para GNOME Sun comienza a portar OpenOffice* a GTK+ Sun comienza a portar OpenOffice* a GTK+ *Sun compró StarDivision en 1999 y liberó el código en junio de 2000 Septiembre, 2000 Sun anuncia Accesibility Lab para mejorar GNOME y pueda ser usado por personas con discapacidades Abril 2, 2001 GNOME 1.4 312 días después 173* colaboradores Principales colaboradores* Desarrollador Añadidas Eliminadas Cambios Havoc Pennington 136,481 76,166 313 Michael Meeks 99,166 57,101 721 John Sullivan 11,047 92,405 139 Seth Nickell 67,979 20,226 38 Elliot Lee 50,300 23,423 285 Nat Friedman 41,887 26,790 160 Ettore Perazzoli 50,267 7,542 171 Zach Frey 32,610 27,937 11 Arturo Espinosa 27,451 3,214 159 Miguel de Icaza 26,510 9,155 199 * En el desarrollo de lo que posteriormente llegó a ser GNOME Platform Enero 27, 2002 GNOME 2.0 Enero 27, 2002 GNOME 2.0 “Prepárate para desecharlo todo al menos una vez” — Frederick Brooks The Mythical Man-Month Mayor reescritura “Prepárate para desecharlo todo al menos una vez” — The Mythical Man-Month Frederick Brooks Simplificación de la interfaz de usuario Accessibilidad Unicode Tipografías con antialias 857.924 líneas de código C (96,72% del código de las bibliotecas) 29.089 líneas de código en shell, perl, python, yacc, awk, lex, lisp (3,28% del código de las bibliotecas) 300 días después 353* colaboradores (núcleo oficial de las bibliotecas) Principales colaboradores* Desarrollador Añadidas Eliminadas Cambios Owen Taylor 911,406 833,423 1,501 Daniel Veillard 945,438 292,143 1,486 Havoc Pennington 391,826 160,090 746 Tim Janik 235,915 221,155 323 Tor Lillqvist 215,843 104,231 504 Lauris Kaplinski 134,074 152,449 284 Martin Baulig 77,099 175,545 1,014 Michael Meeks 152,001 123,577 1,198 Jonathan Blandford 94,889 53,680 422 Anders Carlsson 97,623 56,874 288 Matthias Clasen 37,734 81,089 260 Padraig O.Briain 74,112 44,697 454 Jose Maria Celorio 61,374 28,696 332 Elliot Lee 55,323 9,035 226 Darin Adler 39,814 29,850 267 Bill Haneman 52,007 14,372 278 * En el desarrollo de lo que posteriormente llegó a ser GNOME Platform Febrero 6, 2003 GNOME 2.2 375 días después Se establece calendario de versiones El objetivo: Llegar a un ciclo de 6 meses entre versiones ... Septiembre 15, 2004 GNOME 2.8 Se cumple el objetivo de 6 meses entre versiones 168 días después de 2.6 Se estable una separación entre Escritorio y Plataforma Plataforma (de desarrollo) GNOME Evolución de la plataforma (de desarrollo) GNOME $ git log -M -C --numstat GLIB_1_2_2..GLIB_1_2_8 commit 3118e37ac8ae6708bf88239a43ba6f7421d4c41d Author: CDT 1999 Shawn T. Amundson <[email protected]> Date: Tue Apr 13 21:24:18 1999 +0000 Released GLib 1.2.2 Tue Apr 13 16:16:14 CDT 1999 Shawn T. Amundson <[email protected]> * Released GLib 1.2.2 4 0 ChangeLog 4 0 ChangeLog.pre-2-0 4 0 ChangeLog.pre-2-10 4 0 ChangeLog.pre-2-12 4 0 ChangeLog.pre-2-2 4 0 ChangeLog.pre-2-4 4 0 ChangeLog.pre-2-6 4 0 ChangeLog.pre-2-8 2 2 INSTALL 1 1 README commit 8611980b6bcdde2b33f13b1e8bce5e7765763b46 Author: Elliot Lee <[email protected]> ... Marzo 18, 2009 GNOME 2.26 Cambio de SCM Subversion → Git 175 días después 209* colaboradores (núcleo oficial de las bibliotecas) Datos generales Principales colaboradores* Desarrollador Añadidas Eliminadas Cambios Matthias Clasen 728,880 641,958 380 Behdad Esfahbod 21,004 27,838 420 Alexander Larsson 36,465 10,811 447 Jorge González 32,613 32,214 41 Miloš Popović 30,679 30,653 7 Daniel Nylander 18,881 20,731 18 Ignacio Casal Quinteiro 15,486 15,160 8 Chao-Hsiung Liao 14,664 14,789 7 Manoj Kumar Giri 13,854 13,959 27 Ivar Smolin 1,568 14,156 22 Maxim V. Dziumanenko 13,487 13,747 13 Dan Winship 12,300 592 31 Shankar Prasad 11,357 10,346 24 Inaki Larranaga Murgoitio 9,818 10,215 11 Kjartan Maraas 11,397 11,468 31 * En el desarrollo de lo que posteriormente llegó a ser GNOME Platform Principales compañías colaboradoras* Compañía Añadidas Eliminadas Cambios (Unknown) 12,112,587 7,902,571 43,405 Red Hat 9,109,308 7,288,662 14,311 Novell 1,004,544 621,368 7,263 Sun 288,762 138,824 2,216 Imendio AB 101,133 83,634 1,268 Code Factory 223,390 145,497 647 UNAM 76,671 33,746 631 Eazel 47,833 24,370 376 Mandriva 15,903 25,754 228 OpenShine 65,466 63,564 225 Funky 33,578 13,022 215 Stanford University 113,449 57,487 191 Async Open Source 11,090 1,987 79 University of Michigan 10,184 2,543 68 Wipro 2,642 604 65 * En el desarrollo de lo que posteriormente llegó a ser GNOME Platform .
Load more

Recommended publications
  • Projects on the Move
    :FDDLE@KP Free Software Projects 8elg$kf$[Xk\fm\im`\nf]]i\\jf]knXi\Xe[`kjdXb\ij GIFA<:KJFEK?<DFM< Finally there’s a free alternative to the proprietary Flash on the web. Unfortunately, it implements Microsoft technology whose software patents might render the free Moonlight license useless. BY CARSTEN SCHNOBER Microsoft and Novell formed an alliance Flash format as a global standard for problems to newcomers because you can with the aim of establishing a Flash al- complex, interactive web content. The download a prebuilt version of the pl- ternative for Linux. After one year of co- proprietary browser plugin by Adobe is ugin from the project website and click operation between developers from both like a red flag to a bull for many Linux to install (Figure 1). Thus far, Moonlight companies, a beta version of the Silve- users. Because the source code is not supports only Linux systems using Fire- light free implementation, Moonlight, is available, developers and users of the fox, although the makers claim that it now available. Many members of the free operating system have been forced will support OpenSolaris and the Kon- Linux community suspect that the to rely on Adobe providing updates. In queror and Opera browsers in the near Moonlight Linux implementation [1] is the past, Adobe has been reticent with future. being used to establish Microsoft's Sil- respect to timeliness and completeness. For licensing reasons, the binary pack- verlight [2] technology on a cross-plat- age leaves out all multimedia codecs, form basis, thereby infiltrating the soft- ;Xe^\ijXe[9\e\]`kj thus seriously limiting its own function- ware freedom fighters’ fortress.
    [Show full text]
  • Mono for Cross-Platform Control System Environment
    monomono forfor crosscross--platformplatform controlcontrol systemsystem environmentenvironment H.H. NishimuraNishimura andand C.C. TimossiTimossi,, LBNL,LBNL, Berkeley,Berkeley, CACA 94720,94720, U.S.AU.S.A Work supported by the U.S. Department of Energy under Contract No. DE-AC03-76SF00098 .NET.NET FrameworkFramework z MicrosoftMicrosoft ÄÄ ECMA/ISOECMA/ISO z 1.01.0 inin 20022002 z 1.11.1 inin 20032003 z 2.02.0 inin 20052005 z 3.03.0 inin 2006?2006? z WindowsWindows VistaVista isis .NET.NET--based.based. z C#C# andand manymany otherother languages.languages. .NET.NET missesmisses 22 pieces..pieces.. WhatWhat isis Mono?Mono? z AnAn independentindependent implementationimplementation ofof .NET.NET FrameworkFramework byby XimiaXimiann ÄÄNovell.Novell. z Linux,Linux, FreeBSD,FreeBSD, UNIX,UNIX, MacMac OSOS X,X, SolarisSolaris andand WindowsWindows z s390/s390x,s390/s390x, SPARC,SPARC, PowerPC,PowerPC, x86,x86, x86x86--64,64, IA64,IA64, ARMARM z DualDual LicensedLicensed byby NovellNovell HPHP atat www.mono-project.com SearchSearch MonoMono atat www.wikipedia.orgwww.wikipedia.org WhoWho mademade Mono?Mono? z MiguelMiguel dede IcazaIcaza z CreatedCreated GnomeGnome withwith FedericoFederico MenaMena inin 1997.1997. z CreatedCreated MonoMono inin 20012001 atat XimianXimian.. z ““MonoMono andand GNOME.GNOME. TheThe longlong replyreply”” z 0606 FebFeb 20022002 z http://mail.gnome.org/archives/gnomehttp://mail.gnome.org/archives/gnome-- hackers/2002hackers/2002--February/msg00031.htmlFebruary/msg00031.html z NowNow underunder Novell.Novell. IsIs MonoMono aa CrossCross--PlatformPlatform .NET?.NET? z DefinitelyDefinitely YES!YES! z AsAs .NET.NET RuntimeRuntime EnvironmentEnvironment z AsAs .NET.NET DevelopmentDevelopment EnvironmentEnvironment z AA fewfew yearsyears behindbehind thethe ““.NET.NET onon WindowsWindows””.. z NonNon--graphicalgraphical classesclasses areare basicallybasically OK.OK.
    [Show full text]
  • GIMP Toolkit: GTK+ V1.2
    'Construction d’IHM $ GIMP Toolkit: GTK+ v1.2 Alexis N´ed´elec Ecole Nationale d’Ing´enieursde Brest TechnopˆoleBrest-Iroise, Site de la Pointe du Diable CP 15 29608 BREST Cedex (FRANCE) e-mail : [email protected] & enib=li2 °c A.N. 1 % 'GTK+ v1.2 : GIMP Toolkit $ Table des Mati`eres Introduction 3 Premier Programme: Hello World 10 Signaux et R´eflexes 14 Description de Widget 22 Container de Widgets 32 Entr´eesde Texte 43 Les Listes multi-colonnes 76 Repr´esentation d’arborescence 89 Bibliographie 107 & enib=li2 °c A.N. 2 % 'GTK : GIMP Toolkit $ Introduction On peut d´efinirGTK comme: . une API “Orient´eObjet” . pour le d´eveloppement d’IHM graphiques (GUI) . sous Licence GNU (LGPL) Glossaire de Sigles: . GNU : GNU’s Not Unix ou “Vive le Logiciel Libre !”. GNOME : GNU Network Object Model Environment . GIMP : General Image Manipulation Program . GDK : GIMP Drawing Kit . GTK : GIMP ToolKit & enib=li2 °c A.N. 3 % 'GTK : GIMP Toolkit $ Introduction Le Projet GNOME: . 1997: Miguel de Icaza du “Mexican Autonomous National University” . objectifs : d´eveloppement de logiciels libres (open source) . inspir´edes d´eveloppements de KDE (Qt) GNOME est bas´esur un ensemble de librairies existantes . glib: utilitaire pour la cr´eationet manipulation de structures . GTK+: Boˆıte`aoutils pour le d´eveloppement d’IHM graphiques . ORBit: Le Broker GNOME (CORBA 2.2) pour la distribution d’objets . Imlib: pour la manipulation d’images sous X Window et GDK & enib=li2 °c A.N. 4 % 'GTK : GIMP Toolkit $ Introduction Librairies sp´ecifiquesdu projet GNOME . libgnome: utilitaires (non-GUI) de bases pour toute application GNOME .
    [Show full text]
  • The GNOME Desktop Environment
    The GNOME desktop environment Miguel de Icaza ([email protected]) Instituto de Ciencias Nucleares, UNAM Elliot Lee ([email protected]) Federico Mena ([email protected]) Instituto de Ciencias Nucleares, UNAM Tom Tromey ([email protected]) April 27, 1998 Abstract We present an overview of the free GNU Network Object Model Environment (GNOME). GNOME is a suite of X11 GUI applications that provides joy to users and hackers alike. It has been designed for extensibility and automation by using CORBA and scripting languages throughout the code. GNOME is licensed under the terms of the GNU GPL and the GNU LGPL and has been developed on the Internet by a loosely-coupled team of programmers. 1 Motivation Free operating systems1 are excellent at providing server-class services, and so are often the ideal choice for a server machine. However, the lack of a consistent user interface and of consumer-targeted applications has prevented free operating systems from reaching the vast majority of users — the desktop users. As such, the benefits of free software have only been enjoyed by the technically savvy computer user community. Most users are still locked into proprietary solutions for their desktop environments. By using GNOME, free operating systems will have a complete, user-friendly desktop which will provide users with powerful and easy-to-use graphical applications. Many people have suggested that the cause for the lack of free user-oriented appli- cations is that these do not provide enough excitement to hackers, as opposed to system- level programming. Since most of the GNOME code had to be written by hackers, we kept them happy: the magic recipe here is to design GNOME around an adrenaline response by trying to use exciting models and ideas in the applications.
    [Show full text]
  • The Glib/GTK+ Development Platform
    The GLib/GTK+ Development Platform A Getting Started Guide Version 0.8 Sébastien Wilmet March 29, 2019 Contents 1 Introduction 3 1.1 License . 3 1.2 Financial Support . 3 1.3 Todo List for this Book and a Quick 2019 Update . 4 1.4 What is GLib and GTK+? . 4 1.5 The GNOME Desktop . 5 1.6 Prerequisites . 6 1.7 Why and When Using the C Language? . 7 1.7.1 Separate the Backend from the Frontend . 7 1.7.2 Other Aspects to Keep in Mind . 8 1.8 Learning Path . 9 1.9 The Development Environment . 10 1.10 Acknowledgments . 10 I GLib, the Core Library 11 2 GLib, the Core Library 12 2.1 Basics . 13 2.1.1 Type Definitions . 13 2.1.2 Frequently Used Macros . 13 2.1.3 Debugging Macros . 14 2.1.4 Memory . 16 2.1.5 String Handling . 18 2.2 Data Structures . 20 2.2.1 Lists . 20 2.2.2 Trees . 24 2.2.3 Hash Tables . 29 2.3 The Main Event Loop . 31 2.4 Other Features . 33 II Object-Oriented Programming in C 35 3 Semi-Object-Oriented Programming in C 37 3.1 Header Example . 37 3.1.1 Project Namespace . 37 3.1.2 Class Namespace . 39 3.1.3 Lowercase, Uppercase or CamelCase? . 39 3.1.4 Include Guard . 39 3.1.5 C++ Support . 39 1 3.1.6 #include . 39 3.1.7 Type Definition . 40 3.1.8 Object Constructor . 40 3.1.9 Object Destructor .
    [Show full text]
  • Third Party Terms for Modular Messaging 3.0 (July 2005)
    Third Party Terms for Modular Messaging 3.0 (July 2005) Certain portions of the product ("Open Source Components") are licensed under open source license agreements that require Avaya to make the source code for such Open Source Components available in source code format to its licensees, or that require Avaya to disclose the license terms for such Open Source Components. If you are a licensee of this Product, and wish to receive information on how to access the source code for such Open Source Components, or the details of such licenses, you may contact Avaya at (408) 577-7666 for further information. The Open Source Components are provided “AS IS”. ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR THE CONTRIBUTORS OF THE OPEN SOURCE COMPONENTS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THE PRODUCT, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Avaya provides a limited warranty on the Product that incorporates the Open Source Components. Refer to your customer sales agreement to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language as well as information regarding support for the Product, while under warranty, is available through the following web site: http://www.avaya.com/support.
    [Show full text]
  • The Gnome Desktop Comes to Hp-Ux
    GNOME on HP-UX Stormy Peters Hewlett-Packard Company 970-898-7277 [email protected] THE GNOME DESKTOP COMES TO HP-UX by Stormy Peters, Jim Leth, and Aaron Weber At the Linux World Expo in San Jose last August, a consortium of companies, including Hewlett-Packard, inaugurated the GNOME Foundation to further the goals of the GNOME project. An organization of open-source software developers, the GNOME project is the major force behind the GNOME desktop: a powerful, open-source desktop environment with an intuitive user interface, a component-based architecture, and an outstanding set of applications for both developers and users. The GNOME Foundation will provide resources to coordinate releases, determine future project directions, and promote GNOME through communication and press releases. At the same conference in San Jose, Hewlett-Packard also announced that GNOME would become the default HP-UX desktop environment. This will enhance the user experience on HP-UX, providing a full feature set and access to new applications, and also will allow commonality of desktops across different vendors' implementations of UNIX and Linux. HP will provide transition tools for migrating users from CDE to GNOME, and support for GNOME will be available from HP. Those users who wish to remain with CDE will continue to be supported. Hewlett-Packard, working with Ximian, Inc. (formerly known as Helix Code), will be providing the GNOME desktop on HP-UX. Ximian is an open-source desktop company that currently employs many of the original and current developers of GNOME, including Miguel de Icaza. They have developed and contributed applications such as Evolution and Red Carpet to GNOME.
    [Show full text]
  • A Brief History of GNOME
    A Brief History of GNOME Jonathan Blandford <[email protected]> July 29, 2017 MANCHESTER, UK 2 A Brief History of GNOME 2 Setting the Stage 1984 - 1997 A Brief History of GNOME 3 Setting the stage ● 1984 — X Windows created at MIT ● ● 1985 — GNU Manifesto Early graphics system for ● 1991 — GNU General Public License v2.0 Unix systems ● 1991 — Initial Linux release ● Created by MIT ● 1991 — Era of big projects ● Focused on mechanism, ● 1993 — Distributions appear not policy ● 1995 — Windows 95 released ● Holy Moly! X11 is almost ● 1995 — The GIMP released 35 years old ● 1996 — KDE Announced A Brief History of GNOME 4 twm circa 1995 ● Network Transparency ● Window Managers ● Netscape Navigator ● Toolkits (aw, motif) ● Simple apps ● Virtual Desktops / Workspaces A Brief History of GNOME 5 Setting the stage ● 1984 — X Windows created at MIT ● 1985 — GNU Manifesto ● Founded by Richard Stallman ● ● 1991 — GNU General Public License v2.0 Our fundamental Freedoms: ○ Freedom to run ● 1991 — Initial Linux release ○ Freedom to study ● 1991 — Era of big projects ○ Freedom to redistribute ○ Freedom to modify and ● 1993 — Distributions appear improve ● 1995 — Windows 95 released ● Also, a set of compilers, ● 1995 — The GIMP released userspace tools, editors, etc. ● 1996 — KDE Announced This was an overtly political movement and act A Brief History of GNOME 6 Setting the stage ● 1984 — X Windows created at MIT “The licenses for most software are ● 1985 — GNU Manifesto designed to take away your freedom to ● 1991 — GNU General Public License share and change it. By contrast, the v2.0 GNU General Public License is intended to guarantee your freedom to share and ● 1991 — Initial Linux release change free software--to make sure the ● 1991 — Era of big projects software is free for all its users.
    [Show full text]
  • Free As in Freedom (2.0): Richard Stallman and the Free Software Revolution
    Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution Sam Williams Second edition revisions by Richard M. Stallman i This is Free as in Freedom 2.0: Richard Stallman and the Free Soft- ware Revolution, a revision of Free as in Freedom: Richard Stallman's Crusade for Free Software. Copyright c 2002, 2010 Sam Williams Copyright c 2010 Richard M. Stallman Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License." Published by the Free Software Foundation 51 Franklin St., Fifth Floor Boston, MA 02110-1335 USA ISBN: 9780983159216 The cover photograph of Richard Stallman is by Peter Hinely. The PDP-10 photograph in Chapter 7 is by Rodney Brooks. The photo- graph of St. IGNUcius in Chapter 8 is by Stian Eikeland. Contents Foreword by Richard M. Stallmanv Preface by Sam Williams vii 1 For Want of a Printer1 2 2001: A Hacker's Odyssey 13 3 A Portrait of the Hacker as a Young Man 25 4 Impeach God 37 5 Puddle of Freedom 59 6 The Emacs Commune 77 7 A Stark Moral Choice 89 8 St. Ignucius 109 9 The GNU General Public License 123 10 GNU/Linux 145 iii iv CONTENTS 11 Open Source 159 12 A Brief Journey through Hacker Hell 175 13 Continuing the Fight 181 Epilogue from Sam Williams: Crushing Loneliness 193 Appendix A { Hack, Hackers, and Hacking 209 Appendix B { GNU Free Documentation License 217 Foreword by Richard M.
    [Show full text]
  • Gconf: Manageable User Preferences
    GConf: Manageable User Preferences Havoc Pennington Red Hat, Inc. [email protected], http://pobox.com/˜hp Abstract liMirror and ACAP. Finally, it presents some initial ideas for a Phase Two version of GConf. GConf is a system for storing user prefer- Phase Two is very much a work-in-progress. ences, being deployed as part of the GNOME 2.0 desktop. This paper discusses the ben- 2 Motivation efits of the GConf system, the strengths and weaknesses of the current implementation, and plans for future enhancements. Several years ago it was becoming obvious that GNOME’s initial approach to storing prefer- ences (a simple API for writing key-value pairs 1 Introduction to files) had a lot of limitations: GConf started out very simply in late 1999, as • It did not work for preferences that af- my first project at Red Hat. It was a straightfor- fected or were manipulated by multiple ward response to concrete problems encoun- applications, because there was no way tered while creating the GNOME desktop, and for applications to know a setting had designed to be implementable in a few months changed. GNOME 1.x contains numerous by a programmer with limited experience (i.e., hacks to work around this, and apps have by me). Much of the current implementation to be restarted before certain preferences (let’s call it Phase One) was created at that take effect. time. • Administration features were missing, GConf saw some limited use as part of the such as applying different defaults to dif- GNOME 1.4 platform—specifically in Nau- ferent groups of users, or storing defaults tilus and Galeon—but it wasn’t widely adopted for many machines on one network server.
    [Show full text]
  • What's New in Gnome 2.10
    REVIEWS Gnome 2.10 What’s new in Gnome 2.10 LOOKING FOR TRACKS The new Gnome desktop adds a variety of applications and applets. Under the hood, Gnome 2.10 is more robust. BY CHRISTIAN MEYER ince version 2.0, Gnome has the Gnome panel. Whereas previous harvested both criticism and versions had two entries: Applications Sacclaim. Just two and a half and Actions, Gnome 2.10 introduces a years ago, nobody would have consid- completely new structure with three cat- ered it possible for a graphical desktop egories: Applications, Places, and with a six month release cycle to main- System. tain the high quality standards that The Application category still has the Gnome has maintained. full set of Gnome programs, but now Despite the integration of new func- contains the Run program… item, which tions, the basic libraries continue to be was previously assigned to the Actions downwardly compatible, and this is category. something that has convinced major IT Places takes you to frequently used players such as Red Hat, Novell, or Sun directories. These frequently used direc- to use Gnome as the basis for their prod- tories could include home directories, uct lines. bookmarks from the file browser dialog, The new Gnome Version 2.10 down- any removable media mounted right load became publicly available on 9th now, any network servers, and the last March. This article will be looking at the few documents you opened. You can most important changes introduced by connect to a server from here and search Gnome 2.10, many of which are not just for locally or remotely stored files.
    [Show full text]
  • Project Utopia
    Project Utopia http://0-delivery.acm.org.innopac.lib.ryerson.ca/10.1145/1100000/10901... Project Utopia Robert Love Abstract Users—what will they plug in next? Robert is making the computer make sense of hardware, so you don't have to. For the better part of a decade, Linux enthusiasts have waxed poetic on the inherent greatness and looming success of Desktop Linux. Our kernel is so robust! Our applications are infinitely configurable! This is the year of Desktop Linux! Who would ever use Microsoft Windows? These claims and similar—particularly when made back in the 20th century—seem, in retrospect, so trite. Not that I stand righteous—oh no, I laid the praise down as thick as anyone else did. I too was a convert. At least, I did until I realized that hardware support in Linux was awful. Like a deck of cards, my rosy view of Desktop Linux came crashing down, making an 180 degree turn from glowing to ghastly. Heartbroken, I cried myself to sleep every night and went on an inexplicable diet consisting only of cheese and pudding. But this did not last long. One day, the Linux community decided to do something about it. We outlined a plan not only to reach feature parity with the other desktop operating systems, but also to surpass them. Hardware support has come a long way in the last year and a half. This is the story of just how far. A Past Since Forgotten The steps for installing a new hardware peripheral on a Mac might go a bit like this: Step 1: plug hardware in to Mac.
    [Show full text]