DOCSLIB.ORG

Communication Between Desktop and Web Applications

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Communication Between Desktop and Web Applications Communication between desktop and web applications Author: Manuel Rego Casasnovas Contact: [email protected] Date: 20/11/2009 Copyright: Some rights reserved. This document is distributed under the Creative Commons Attribution-ShareAlike 3.0 licence, available in http://creativecommons.org/licenses/by-sa/3.0/. Abstract: Nowadays, everybody uses web applications. Despite of their advantages, like being available at any place with Internet, they have some usability problems with regard to common desktop applications. This article tries to analyze the possible solutions in order to interconnect desktop and web applications, centered in the GNOME platform and using RTM-GLib as example and study case. Table of Contents Introduction 2 State of the art in the GNOME platform . .2 Goals .......................................7 The library: RTM-GLib 7 Dependencies . .7 Development . .8 License ......................................8 Roadmap . .8 Usage example . .9 Future ideas 9 Mojito.......................................9 Trackerminer................................... 10 EDSbackend................................... 11 Conclusion 11 1 Introduction There are a large amount of web services in the Internet. A general definition of web service said that it is a system which provides an interface to allow interaction between machines over a network. As time passes more and more web applications provide some kind of API in order to access their services. This number is growing and it seems that will keep growing for some time. Some examples of these applications: Flickr, Facebook, Twitter, etc. Web applications has some advantages compared with desktop applications: All the data is shared and in a centralized place. They do not need any special configuration or installation, just a simple web browser is enough. Access from anywhere. Talking about desktop applications it is worth to highlight some strengths: They are faster. Usually they have better and richer user interfaces. There are different trends nowadays, some focused on develop applications to run in a browser, and other related with the development of desktop or mobile applications that uses web services. In this article we will talk about the latter group. The main problem here is the connection between desktop applications and these web services. That is not solved yet in a common way for all desktop applications. In that moment, every desktop application develops its own solution to access to some of these remote web services. Having to fight again and again with the same issues related with the implementation. Usually these web applications provide some API kit (or libraries) to make more comfortable the access to these web services from the desktop (or other web applications). That helps to share some code, but it is not a final solution thinking in the whole integration between desktop and web. State of the art in the GNOME platform There are different GNOME projects trying to fix the issues related with access to remote web services, and trying to provide a common solution for all the desktop applications. In this point, we are going to briefly review three of these projects: Online Desktop, Conduit and Mojito. There is also a page at live.gnome.org (GNOME Integration with Online Services) that tries to aggregate all the information about the different technologies that allows to integrate desktop and web applications. The idea is to collect all the different libraries to define a common way to access web services in the future GNOME 3.0. When people expect a better communication of the whole desktop with the most used web services. 2 Online Desktop Online Desktop was an important initiative that tried to join the desktop applications and the web services. The main idea is use desktop applications to access the different web applications, instead of a just a simple web browser. Online Desktop architecture overview One important part is the a central web server, written in Java, which manages the access to the different web services. This main server would be in charge to interact with the web applications, implementing the needed interfaces to do this work. This main server also store some user data like web services accounts, configuration of desktop applications, etc. Even it could end up saving passwords of web applications. This is a great idea, because all the work needed to connect with any web application would be shared in the central server. Then, when some web application changes its API, ideally, just this server should be modified. Moreover, from the final user point of view, the most important feature is that he just need to authenticate one time (against the central server) and then all his data and services would be available. Thus, the user should not care about which computer is using, because of all the information will be stored in the main server. From the point of view of desktop applications, Online Desktop provides a daemon, which defines some D-Bus methods and signals, to be used by them in order to interact with the different web services. This daemon is connected to the main server using the 3 XMPP protocol, which means that there is a two-way communication between the dae- mon and the central server. This allow to the server send signals to desktop applications when some data has changed. Even, the main server could poll the different web services from time to time, and then send signals to desktop applications. Some advantages of this solution: It is really comfortable for desktop applications, because they just need to know a D-Bus interface to interact with web applications. The logic to interact with web service is just implemented once in the main server. Some drawbacks: The central server could become a bottleneck if there are a lot of users. Perhaps, some scalability problems could appear. Security issues that could appear because of a lot of user information is stored in the main server. The project is currently abandoned. Online desktop was started by the middle of 2007 and just lasted around one year. It was started by some important GNOME hackers (Havoc Pennington, Owen Taylor and Colin Walters) working in Red Hat in that time. By the middle of 2008 the project started to decrease its activity, and it is stopped since one year ago. Conduit Conduit is a generic synchronization application for GNOME. It is not just a bridge between desktop and web applications. For example, it allows you to synchronize: two folders on your system, your music library with your iPod, your contacts with your mobile phone, etc. Conduit allows to create different modules for each kind of synchronization. By the way, Conduit supports the SyncML protocol, a synchronization standard for mobile devices. That allows to share your contacts between your computer and your mobile phone. 4 Conduit modules overview (from the point of view of desktop and web communications) As it has a wider scope than just web services, it is a completely different approach. However, it adds a new idea to fix the problem related with web synchronization. In the case of synchronize applications and web services it uses the D-Bus interfaces provided by desktop applications, or just use the files stored by these applications to get the information. Which means that for every application it should know its D-Bus interface or how are formated the files it uses. So, if something changes in the application implementation, the Conduit module should be modified. Desktop applications do not know anything about Conduit, so they do not know if somebody is doing a synchronization with their data. This can be an important source of problems, moreover the functionality that Conduit could provide is not the as powerful as if the proper applications directly access to web services. If we talk about desktop and web synchronization the main advantages: There are already some source code to access to web services APIs in different modules. Among the disadvantages: It is not thought for this specific purpose of connecting desktop and web applications. Depends on D-Bus interfaces or file formats of desktop applications, that could change in any moment. Desktop applications do not manage the interaction with the web services. 5 Mojito Mojito is a project that tries to bring social networks to the desktop. It is new project and is part of the Moblin project developed by Intel. Mojito structure overview For the moment it is just a social network aggregator, that pulls in content from some web services. Mojtio provides a D-Bus interface that desktop applications can use to get data from these web applications. Moreover, it also provide a method to update your status on web services that supports it. That is something similar to the Online Desktop approach. To sum up, you can say that it is a centralized place to manage all the interaction of the desktop with different web applications. All the logic needed to connect to these web services is implemented in Mojito. Furthermore, it polls the different web service time to time, and send D-Bus signals when something changes. Advantages: From the point of view of desktop applications that wants to interact with some web service, it is quite similar to the Online Desktop approach. All the logic related with web services is implemented in the same appli- cation, so some common code to access the web could be easily shared. Disadvantages: 6 For the moment it just support a few functionalities, and it is not sure that this will expand its current scope. It is still in an early stage and it is not part of the GNOME project yet. Goals After review the current situation related with this topic, the idea is to create a GNOME based library in order to provide access to the Remember The Milk web application.
Load more

Recommended publications
  • Ubuntu Kung Fu
    Prepared exclusively for Alison Tyler Download at Boykma.Com What readers are saying about Ubuntu Kung Fu Ubuntu Kung Fu is excellent. The tips are fun and the hope of discov- ering hidden gems makes it a worthwhile task. John Southern Former editor of Linux Magazine I enjoyed Ubuntu Kung Fu and learned some new things. I would rec- ommend this book—nice tips and a lot of fun to be had. Carthik Sharma Creator of the Ubuntu Blog (http://ubuntu.wordpress.com) Wow! There are some great tips here! I have used Ubuntu since April 2005, starting with version 5.04. I found much in this book to inspire me and to teach me, and it answered lingering questions I didn’t know I had. The book is a good resource that I will gladly recommend to both newcomers and veteran users. Matthew Helmke Administrator, Ubuntu Forums Ubuntu Kung Fu is a fantastic compendium of useful, uncommon Ubuntu knowledge. Eric Hewitt Consultant, LiveLogic, LLC Prepared exclusively for Alison Tyler Download at Boykma.Com Ubuntu Kung Fu Tips, Tricks, Hints, and Hacks Keir Thomas The Pragmatic Bookshelf Raleigh, North Carolina Dallas, Texas Prepared exclusively for Alison Tyler Download at Boykma.Com Many of the designations used by manufacturers and sellers to distinguish their prod- ucts are claimed as trademarks. Where those designations appear in this book, and The Pragmatic Programmers, LLC was aware of a trademark claim, the designations have been printed in initial capital letters or in all capitals. The Pragmatic Starter Kit, The Pragmatic Programmer, Pragmatic Programming, Pragmatic Bookshelf and the linking g device are trademarks of The Pragmatic Programmers, LLC.
    [Show full text]
  • The GNOME Census: Who Writes GNOME?
    The GNOME Census: Who writes GNOME? Dave Neary & Vanessa David, Neary Consulting © Neary Consulting 2010: Some rights reserved Table of Contents Introduction.........................................................................................3 What is GNOME?.............................................................................3 Project governance...........................................................................3 Why survey GNOME?.......................................................................4 Scope and methodology...................................................................5 Tools and Observations on Data Quality..........................................7 Results and analysis...........................................................................10 GNOME Project size.......................................................................10 The Long Tail..................................................................................11 Effects of commercialisation..........................................................14 Who does the work?.......................................................................15 Who maintains GNOME?................................................................17 Conclusions........................................................................................22 References.........................................................................................24 Appendix 1: Modules included in survey...........................................25 2 Introduction What
    [Show full text]
  • Fedora 16 System Administrator's Guide
    Fedora 16 System Administrator's Guide Deployment, Configuration, and Administration of Fedora 16 Jaromír Hradílek Douglas Silas Martin Prpič Eva Kopalová Eliška Slobodová Tomáš Čapek Petr Kovář Miroslav Svoboda System Administrator's Guide John Ha David O'Brien Michael Hideo Don Domingo Fedora 16 System Administrator's Guide Deployment, Configuration, and Administration of Fedora 16 Edition 1 Author Jaromír Hradílek [email protected] Author Douglas Silas [email protected] Author Martin Prpič [email protected] Author Eva Kopalová [email protected] Author Eliška Slobodová [email protected] Author Tomáš Čapek [email protected] Author Petr Kovář [email protected] Author Miroslav Svoboda [email protected] Author John Ha Author David O'Brien Author Michael Hideo Author Don Domingo Copyright © 2011 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
    [Show full text]
  • Memory Debugging
    Arm Forge User Guide Version 20.0.2 Arm Forge 20.0.2 Non-Confidential Proprietary Notice This document is protected by copyright and other related rights and the practice or implementation of the information contained in this document may be protected by one or more patents or pending patent applications. No part of this document may be reproduced in any form by any means without the express prior written permission of Arm. No license, express or implied, by estoppel or otherwise to any intellectual property rights is granted by this document unless specifically stated. Your access to the information in this document is conditional upon your acceptance that you will not use or permit others to use the information for the purposes of determining whether implementations infringe any third party patents. THIS DOCUMENT IS PROVIDED “AS IS”. ARM PROVIDES NO REPRESENTATIONS AND NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, SATISFACTORY QUALITY, NONIN- FRINGEMENT OR FITNESS FOR A PARTICULAR PURPOSE WITH RESPECT TO THE DOCU- MENT. For the avoidance of doubt, Arm makes no representation with respect to, and has undertaken no analysis to identify or understand the scope and content of, third party patents, copyrights, trade secrets, or other rights. This document may include technical inaccuracies or typographical errors. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL ARM BE LIABLE FOR ANY DAMAGES, INCLUDING WITHOUT LIMITATION ANY DIRECT, INDIRECT, SPECIAL, INCI- DENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND REGARD- LESS OF THE THEORY OF LIABILITY, ARISING OUT OF ANY USE OF THIS DOCUMENT, EVEN IF ARM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Manuel Utilisateur Inkscape 1 / 174
    Manuel Utilisateur Inkscape 1 / 174 Manuel Utilisateur Inkscape Ed. Manuel Utilisateur Inskcape Ed. Manuel Utilisateur Inskcape Manuel Utilisateur Inkscape 2 / 174 Copyright © 2004-2007 Inkscape Team Permission to use, copy, modify and distribute under the terms of the General Public License. Ed. Manuel Utilisateur Inskcape Manuel Utilisateur Inkscape 3 / 174 COLLABORATORS TITLE : REFERENCE : Manuel Utilisateur Inkscape ACTION NAME DATE SIGNATURE WRITTEN BY Cedric Gemy, Kevin August 11, 2007 Wixson, and Elisa de Castro Guerra REVISION HISTORY NUMBER DATE DESCRIPTION NAME Ed. Manuel Utilisateur Inskcape Manuel Utilisateur Inkscape 4 / 174 Contents 1 Présentation d’Inkscape 27 1.1 Qu’est-ce qu’Inkscape ? . 27 1.1.1 I........................................................ 27 1.2 LeSVG........................................................ 27 1.2.1 Scalable Vector Graphics . 27 1.2.2 Objectifs du SVG . 28 1.3 Interface . 29 1.3.1 La fenêtre Inkscape . 29 1.3.2 Le menu . 30 1.3.3 La barre de commande . 30 1.3.4 Les outils . 31 1.3.5 La barre de contrôle des outils ou les options des outils . 31 1.3.6 Le canevas . 32 1.3.7 La palette . 32 1.3.8 La barre d’état et d’information . 32 1.3.9 Infos additionnelles . 32 1.3.10 Lire aussi . 33 1.4 Contextualité . 33 1.4.1 Contextualité . 33 1.5 Dialogues . 33 1.5.1 ........................................................ 33 1.5.2 Infos additionnelles . 33 1.6 Canevas . 34 1.6.1 Déplacement dans la fenêtre . 35 1.7 Règles . 35 1.7.1 Infos additionnelles . 35 1.8 Repères . 36 1.8.1 Apercu .
    [Show full text]
  • COURSE TITLE TEXT ACCG100 Practical Accounting Non-Major
    2010-11 Course Descriptions COURSE TITLE TEXT Students will learn the bookkeeping procedures necessary for preparation of financial statements and payroll. (F,Sp,Su). ACCG100 Practical Accounting Non-Major Prerequisite: None. Students will learn to interpret financial statements and use this information for analysis, budgeting, and decision-making. (F,Sp). ACCG101 Accounting Info for Management Prerequisite: None. This course explores current issues, knowledge, and skills relevant to the accounting profession. Specific topics vary by semester. Check the semester schedule book. (F,Sp,Su). Prerequisite: ACCG102 Special Topics in Accounting Determined by Section. Students will complete individual income tax returns and supporting schedules according to the Internal Revenue Code. The focus is on the completion of forms rather than the theoretical aspects of the tax law. (F). ACCG140 Income Tax Preparation Prerequisite: None. This course covers laws affecting payroll, calculation of payroll and payroll taxes using both manual and computer payroll systems, preparation of tax forms for payroll taxes, sales and use taxes, and personal property taxes. (F,Sp,Su). ACCG160 Payroll Systems and Taxes Prerequisite: None. Recommended: ACCG 100 or equivalent work experience. Students will have hands-on experience in setting up an accounting system for a new or existing company using the QuickBooks general ledger accounting software. Students also will learn how to perform numerous types of accounting procedures using QuickBooks. (F,Sp,Su). ACCG161 Accounting with Quickbooks Prerequisite: Math Level 4. Recommended: ACCG 100 or equivalent course coursework or equivalent work experience. Principles of Accounting I is the first class of a two-semester sequence focusing on financial accounting.
    [Show full text]
  • Libghc-Pool-Conduit-Prof Libghc-Resource-Pool-Prof 0. Haskell
    nkf libisc83 python-ball libswitch-perl python-async libcogl-pango0 libthai0 0. gcj-4.7-jre-lib 0. 0. 1.96078431373 libbind9-80 kde-workspace-data 0. 0. 0.925925925926 0. 0. 0. libisnativec-java 0. 0. 0. cmigemo ttf-unifont 0.0645994832041 0. ballview 0. 1.91082802548 libdca-dev libclutter-1.0-0 gcj-4.7-jdk libeet-dev 0. paw libgdkcutter-pixbuf-dev librasqal3 0. libmodplug-dev 0. 0.925925925926 kget 0. 0. gforge-common 0. 0. libclass-isa-perl 0. perl 0. libisccc80 python-gitdb python-git 0. 0. libthai-data 0.345796412362 libdatrie1 0. 0. 0.388349514563 0. 3.92156862745 0. multiarch-support 0. kde-workspace-bin 0. 0. 0. root-plugin-graf2d-asimage 0. 0. libisfreetype-java librasqal3-dev 0. 2.23300970874 libcollections15-java 0. 3.84615384615 libsane-common libsane acl python-ballview r-cran-spatial r-recommended r-cran-class gcc-avr cmigemo-common libcogl9 libgcj13-dev libreact-ocaml liblwt-ocaml libtext-ocaml 0. 0. 2.85714285714 0. 0. 3.84615384615 0.345796412362 0. 0. 0. 2.22222222222 0. 0. 0. 0. kxterm 0. 0. libpcp-gui2 libdatetime-event-recurrence-perl unifont jfbterm 0.41063323968 libdns81 0. fp-units-multimedia-2.6.0 0. 0. libc6 0. cutter-gtk-support libraptor2-0 libmhash2 libecore-dev 0. libeina-dev 0. 0. 0. 0.390243902439 0. 0. libphp-simplepie libjas-java 0. 0. libparrot4.0.0 libparrot-dev 0. 0. 0. 0. paw-common 0. kbattleshipkigo sendmail-cf 0.00308632449616 0. lskat kpat libisrt-java 0. libpango1.0-0 perl-modules python-smmap konquest 0. libunicode-maputf8-perl oxygencursors 0.
    [Show full text]
  • Debian and Ubuntu
    Debian and Ubuntu Lucas Nussbaum lucas@{debian.org,ubuntu.com} lucas@{debian.org,ubuntu.com} Debian and Ubuntu 1 / 28 Why I am qualified to give this talk Debian Developer and Ubuntu Developer since 2006 Involved in improving collaboration between both projects Developed/Initiated : Multidistrotools, ubuntu usertag on the BTS, improvements to the merge process, Ubuntu box on the PTS, Ubuntu column on DDPO, . Attended Debconf and UDS Friends in both communities lucas@{debian.org,ubuntu.com} Debian and Ubuntu 2 / 28 What’s in this talk ? Ubuntu development process, and how it relates to Debian Discussion of the current state of affairs "OK, what should we do now ?" lucas@{debian.org,ubuntu.com} Debian and Ubuntu 3 / 28 The Ubuntu Development Process lucas@{debian.org,ubuntu.com} Debian and Ubuntu 4 / 28 Linux distributions 101 Take software developed by upstream projects Linux, X.org, GNOME, KDE, . Put it all nicely together Standardization / Integration Quality Assurance Support Get all the fame Ubuntu has one special upstream : Debian lucas@{debian.org,ubuntu.com} Debian and Ubuntu 5 / 28 Ubuntu’s upstreams Not that simple : changes required, sometimes Toolchain changes Bugfixes Integration (Launchpad) Newer releases Often not possible to do work in Debian first lucas@{debian.org,ubuntu.com} Debian and Ubuntu 6 / 28 Ubuntu Packages Workflow lucas@{debian.org,ubuntu.com} Debian and Ubuntu 7 / 28 Ubuntu Packages Workflow Ubuntu Karmic Excluding specific packages language-(support|pack)-*, kde-l10n-*, *ubuntu*, *launchpad* Missing 4% : Newer upstream
    [Show full text]
  • Technical Notes All Changes in Fedora 13
    Fedora 13 Technical Notes All changes in Fedora 13 Edited by The Fedora Docs Team Copyright © 2010 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https:// fedoraproject.org/wiki/Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. All other trademarks are the property of their respective owners. Abstract This document lists all changed packages between Fedora 12 and Fedora 13.
    [Show full text]
  • Secure Programming for Linux and Unix HOWTO
    Secure Programming for Linux and Unix HOWTO David A. Wheeler v3.010 Edition Copyright © 1999, 2000, 2001, 2002, 2003 David A. Wheeler v3.010, 3 March 2003 This book provides a set of design and implementation guidelines for writing secure programs for Linux and Unix systems. Such programs include application programs used as viewers of remote data, web applications (including CGI scripts), network servers, and setuid/setgid programs. Specific guidelines for C, C++, Java, Perl, PHP, Python, Tcl, and Ada95 are included. For a current version of the book, see http://www.dwheeler.com/secure−programs This book is Copyright (C) 1999−2003 David A. Wheeler. Permission is granted to copy, distribute and/or modify this book under the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any later version published by the Free Software Foundation; with the invariant sections being ``About the Author'', with no Front−Cover Texts, and no Back−Cover texts. A copy of the license is included in the section entitled "GNU Free Documentation License". This book is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Secure Programming for Linux and Unix HOWTO Table of Contents Chapter 1. Introduction......................................................................................................................................1 Chapter 2. Background......................................................................................................................................4
    [Show full text]
  • Course Descriptions the Following List of Courses Is Arranged in Alphabetical Order by Course Prefix and in Numerical Order Under the Program of Study
    COURSE DESCRIPTIONS The following list of courses is arranged in alphabetical order by course prefix and in numerical order under the program of study. Following the title are numbers representing lecture, lab, clinical or work experience, and credit. When classes have pre- or co-requisite requirements, those are listed as well. These are noted as either State (S) or Local (L) requirements. Courses below the 100 level are considered developmental education courses and serve as prerequisites to curriculum study. Grades in all courses below the 100 level will not count as hours/credits earned and will not be used to calculate grade point averages. Courses below the 100 level are counted as hours attempted for financial aid and term course load purposes. Courses without clinical or work experience hours have three numbers listed, as in Example 1 below. Courses with clinical or work experience hours have four numbers listed, as in Example 2 below. The final sentence in some course descriptions indicates the potential transferability of the course, as in Example 3 below. EXAMPLE 1 Lecture Lab Credit PSY 118 Interpersonal Psychology 3 0 3 This course introduces the basic principles of psychology as they relate to personal and professional development. Emphasis is placed on personality traits, communication/leadership styles, effective problem solving, and cultural diversity as they apply to personal and work environments. Upon completion, students should be able to demonstrate an understanding of these principles of psychology as they apply to personal and professional development. S11025 EXAMPLE 2 Lecture Lab Clin/Wrk Credit COE 111 Co-op Work Experience I 0 0 10 1 This course provides work experience with a college-approved employer in an area related to the student’s program of study.
    [Show full text]
  • Project Gnome Eddy County, New Mexico by LEONARD M
    C1vity pmdutmd by the Gnome explofi~n*rrd 8abmQusnt e4hp. Note Bgum rigbtoantsr of rukbk for m8k. myL 70 feet high and more than 150 feet across, Phomph by Lrwrenca Radiation Laborstory. Geologic Studies Project Gnome Eddy County, New Mexico By LEONARD M. GARD; JR. - - - Prepared on behay of the - - U.S. Atomic Energy Commission -@b UNITED STATES GOVERNMENT PRINTING OFFICE, WASHINGTON : 1968 UNITED STATES DEPARTMENT OF THE INTERIOR STEWART- L. UDALL, Secfetary GEOLOGICAL SURVEY William T. Pecora, Director Librnry of Congress cntalog-cord KO.GS 6s-1S6 For sale by the Superintendent of Documents, U.S. Government Printing Office Washington, D.C. 20402 CONTENTS Page a stract------------------------------------------- Gnome area-Continued troduction..----.--------------------------------- Properties of the rocks-Continued Purpose of Project Gnome ....................... Minor elements in Salado Formation in the 9 Historical summary of the project- -- ------------- Gnome drift- -- - - -- - - - -- -- - - - -- - - - - - - - - - - Participation by the U.S. Geological Survey ------- Mineralogy and petrography of the Salado For- Purpose of this report- -- .. -- - - --- --- -------- .. --- - mation near the device ohamber -----------. Acknowledgments- - - - - - - - ---- - - - - - - - - - - - - - - - - - - - Halite-----------------------------..--- 7 Methods of study ------- ------------------------ Polyhalite- - - - - - - - - - - - - - - - - - - - - - - - - - - - - lyseology- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [Show full text]