DOCSLIB.ORG

Sistema De Información Orientado a La Web Para El Seguimiento Y Control Del Capital Vital De La Fundación Colombia Somos Todos

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Sistema De Información Orientado a La Web Para El Seguimiento Y Control Del Capital Vital De La Fundación Colombia Somos Todos SISTEMA DE INFORMACIÓN ORIENTADO A LA WEB PARA EL SEGUIMIENTO Y CONTROL DEL CAPITAL VITAL DE LA FUNDACIÓN COLOMBIA SOMOS TODOS HERMES SAMIT CASTAÑO CARDOZO FELIPE ALONSO GALINDO LOZANO ALONSO OYOLA TRUJILLO UNIVERSIDAD COOPERATIVA DE COLOMBIA FACULTAD DE INGENIERÍA DE SISTEMAS IBAGUÉ, TOLIMA 2018 Este obra está bajo una licencia de Creative Commons Reconocimiento-NoComercial- SinObraDerivada 4.0 Internacional. SISTEMA DE INFORMACIÓN ORIENTADO A LA WEB PARA EL SEGUIMIENTO Y CONTROL DEL CAPITAL VITAL DE LA FUNDACIÓN COLOMBIA SOMOS TODOS HERMES SAMIT CASTAÑO CARDOZO FELIPE ALONSO GALINDO LOZANO ALONSO OYOLA TRUJILLO INFORME FINAL PRODUCTO DE LA PRÁCTICA EMPRESARIAL NO REMUNERADA EN CONVENIO CON LA FUNDACIÓN COLOMBIA SOMOS TODOS ASESOR: ING. DENNIS MARTINEZ DUQUE UNIVERSIDAD COOPERATIVA DE COLOMBIA FACULTAD DE INGENIERÍA DE SISTEMAS IBAGUÉ, TOLIMA 2018 1 2 NOTA DE ACEPTACIÓN 3 DEDICATORIA El proyecto producto de esta pasantía empresarial se la dedicamos a nuestras familias, ya que nuestra carrera sería nada sin su apoyo incondicional, carrera la cual culmina dando como fruto un sistema que reúne años de estudios, práctica, sacrificio, esfuerzo, y compromiso, sin nuestras familias no seríamos los hombres comprometidos a hacer la diferencia con nuestro conocimiento, enfocados al análisis y desarrollo de los sistemas emergentes, cumpliendo así con el Objeto de Estudio de nuestra honorable universidad, siendo el estudio de “La información, su gestión y seguridad, mediante la arquitectura de software y el desarrollo e implementación de aplicaciones informáticas para apoyar los procesos y procedimientos de las organizaciones” 1. Dedicado a todos los profesores que estuvieron en nuestras vidas desde el inicio de nuestros estudios universitarios hasta la entrega de este informe, quienes nos enseñaron sobre la vida, extendieron su conocimiento, nos dieron perspectiva, enseñándonos a tener una amplia visión de nuestro entorno, a dar un paso atrás para ver desde nuevos ángulos, a explorar la creatividad y el ingenio, a observar todo como un sistema analizable y ajustable para hacerlo más eficiente, y nos dieron las herramientas suficientes para agarrar el planeta con las manos, y hacer de este un mundo con soluciones fáciles a problemas complejos. A nuestros amigos y compañeros dentro de la Universidad Cooperativa de Colombia, quienes fueron un apoyo constante en el desarrollo de la pasantía, brindándonos conocimiento, compartiendo sus experiencias en temas relacionados, dándonos apoyo moral y tolerando cuando expresamos nuestras preocupaciones cuando surgían dificultades. Y, por último, pero no menos importante, a los niños de la fundación Colombia Somos Todos, quienes se verán beneficiados con el resultado del proyecto, ellos son el futuro nuestro país, y merecen lo mejor; aportamos el primer ladrillo de lo que podría ser en un futuro con más actualizaciones, el mejor software de seguimiento y control del rendimiento del capital humano aplicado a la fundación ya mencionada, con el que podrán encontrar futuras promesas a nivel deportivo o académico. 1. UNIVERSIDAD COOPERATIVA DE COLOMBIA. (2013). Objeto de estudio del programa de Ingeniería de Sistemas. Recuperado el 3 de agosto del 2018 en: https://goo.gl/AgDws3 CONTENIDO 4 NOTA DE ACEPTACIÓN………………………………………………………………...3 DEDICATORIA……………………………………………………………………………4 RESUMEN…………………………………………………………………………………6 INTRODUCCIÓN …………………………………………………………………………7 LISTA DE FIGURAS ............................................................................................... 8 1. DESCRIPCIÓN DEL PROBLEMA ................................................................... 11 2. OBJETIVO GENERAL ...................................................................................... 12 3. OBJETIVOS ESPECÍFICOS ............................................................................. 13 4. JUSTIFICACIÓN DEL PROBLEMA .................................................................. 14 5. MARCO TEÓRICO ............................................................................................ 15 6. PROCESOS DESARROLLADOS ..................................................................... 20 7. MARCO OPERATIVO DE LA PRÁCTICA EMPRESARIAL ........................... 162 8. CONCLUSIONES ............................................................................................ 166 9. RECOMENDACIONES .................................................................................... 167 10. GLOSARIO .................................................................................................... 168 11. BIBLIOGRAFÍA ............................................................................................. 171 12. ANEXOS ........................................................................................................ 172 12.1 ACTA DE FINALIZACIÓN ........................................................................... 173 5 RESUMEN En este informe se encontrará la descripción detallada del desarrollo de un aplicativo web destinado a una fundación para el seguimiento y control de los niños que integran la misma, teniendo en cuenta diferentes aspectos evaluativos, y basados en los conocimientos básicos adquiridos en la carrera de Ingeniería de Sistemas; se socializa como se desarrolla el aplicativo en sus diferentes fases, haciendo énfasis en el diseño y programación, hablando desde su modelo conceptual, hasta las diferentes capas que se integran en el desarrollo. Se responderán incógnitas como, ¿por qué se realiza el proyecto?, ¿cómo se llegó a la solución sistemática que se plantea?, ¿para quién va dirigido?, ¿quién poseerá los derechos patrimoniales del sistema?, ¿cuál el objetivo principal de la aplicación?, se contarán experiencias personales que se tuvieron durante el proceso, incluyendo dificultades que surgieron desde el inicio, sobre las visitas realizadas a la fundación en la etapa de observación y análisis de los procesos evaluativos, sobre la calidad del trabajo, las adaptabilidad del programa, sobre la seguridad de acceso del sistema, recomendaciones que reflejan el potencial del mismo para la organización que va destinado y documentos anexos que soportan la veracidad de este informe. PALABRAS CLAVE: Ingeniería de Sistemas, Bases de datos, diseño, modelo conceptual, seguridad, front-end, back-end, interfaces, programación, desarrollo, aplicativo, sistema. 6 INTRODUCCIÓN La Fundación sin ánimo de lucro COLOMBIA SOMOS TODOS tiene como objetivo principal la contribución al conglomerado social de las clases menos favorecidas de la población colombiana en algunos sectores del país, vinculando menores de escasos recursos que estén interesados en formarse profesionalmente como futbolistas y llevar una vida sana, apoyando a la infancia colombiana de hoy por medio del deporte y la formación intelectual, buscando comunidades competitivas y líderes del mañana. En este proyecto la fundación sin ánimo de lucro, pretende instaurar un servicio a la comunidad, bajo parámetros de formación integral a los menores desarrollando no solamente sus destrezas deportivas sino también potencializando sus habilidades intelectuales teniendo en cuenta a la familia como acompañante fundamental dentro del proceso. Es por ello que la fundación se propone como estrategia una intervención integral que promueva el desarrollo humano en sus múltiples dimensiones, complementando la práctica del fútbol con herramientas pedagógicas dirigidas a niños y adolescentes que permitan crear la posibilidad del uso del tiempo libre, entrenamiento físico, acompañamiento psicológico, promoviendo los valores humanos y la familia como una parte integral para lograr el desarrollo de mejores seres humanos por intermedio del deporte, creando así los líderes del mañana. En la actualidad la fundación se encuentra en un constante cambio hacia la era de la revolución del conocimiento, representado en los avances tecnológicos en investigación y desarrollo, en lo cual la Fundación COLOMBIA SOMOS TODOS no puede quedar atrás a estos avances; por el contrario, como entidad privada sin ánimo de lucro debe ir a la vanguardia de la implementación y uso de las tecnologías de la información. Se deben realizar seguimientos y medidores de alcances de nuestro capital vital, en donde se identifican los componentes necesarios para un desarrollo integral, y la conformación de las fases del programa de la fundación. 7 LISTA DE FIGURAS Figura 1. W3COUNTER - Web Browser Market Share, Tendencia mensual - 16 Figura 2. W3COUNTER - Web Browser Market Share -17 Figura 3. Caso de uso Fases - 80 Figura 4. Caso de uso Ingreso al Sistema - 81 Figura 5. Caso de uso Notas - 82 Figura 6. Caso de uso Notas de Prueba - 83 Figura 7. Caso de uso Fundación - 84 Figura 8. Caso de uso Periodos - 85 Figura 9. Caso de uso Niño - 86 Figura 10. Caso de uso Caracterización Familiar - 87 Figura 11. Caso de uso Patrocinador - 88 Figura 12. Caso de uso Sede - 89 Figura 13. Caso de uso Área - 90 Figura 14. Caso de uso Indicadores - 91 Figura 15. Caso de uso Pruebas - 92 Figura 16. UML del Ingreso al Sistema - 93 Figura 17. UML de Crear Sede - 94 Figura 18. UML de Eliminar Sede - 95 Figura 19. UML de Lista Sede - 96 Figura 20. UML de Editar Sede - 97 Figura 21. UML de Lista Periodo - 98 Figura 22. UML de Eliminar Periodo - 99 Figura 23. UML de Crear Periodo - 100 Figura 24. UML de Editar Periodos - 101 Figura 25. UML de Crear Fases - 102 Figura 26. UML de Editar Fases - 103 Figura 27. UML de Eliminar Fases - 104 Figura 28. UML de Lista Fases - 105 Figura 29. UML de Crear Fases - 106 Figura
Load more

Recommended publications
  • A Taxonomy and Business Analysis for Mobile Web Applications
    A Taxonomy and Business Analysis for Mobile Web Applications Kevin Hao Liu Working Paper CISL# 2009-01 January 2009 Composite Information Systems Laboratory (CISL) Sloan School of Management, Room E53-320 Massachusetts Institute of Technology Cambridge, MA 02142 A Taxonomy and Business Analysis for Mobile Web Applications By Kevin Hao Liu Ph.D. Computer Science Victoria University Submitted to the System Design and Management Program in Partial Fulfillment of the Requirements for the Degree of Master of Science in Management and Engineering At the Massachusetts Institute of Technology February 2009 © 2009 Kevin H Liu. All rights reserved The author hereby grants to MIT permission to reproduce and to distribute publicly paper and electronic copies of this thesis document in whole or in part in any medium now known or hereafter created. Signature of Author Kevin H Liu System Design and Management Program February 2009 Certified by Stuart E Madnick John Norris Maguire Professor of Information Technology Sloan School of Management Professor of Engineering Systems School of Engineering Massachusetts Institute of Technology Thesis Supervisor Certified by Patrick Hale Director System Design & Management Program Massachusetts Institute of Technology A Taxonomy and Business Analysis for Mobile Web Applications By Kevin Hao Liu Submitted to the System Design and Management Program in February 2009 in Partial Fulfillment of the Requirements for the Degree of Master of Science in Management and Engineering ABSTRACT Mobile web applications refer to web applications on mobile devices, aimed at personalizing, integrating, and discovering mobile contents in user contexts. This thesis presents a comprehensive study of mobile web applications by proposing a new taxonomy for mobile web applications, and conducting a business analysis in the field of mobile web applications.
    [Show full text]
  • HTTP Cookie - Wikipedia, the Free Encyclopedia 14/05/2014
    HTTP cookie - Wikipedia, the free encyclopedia 14/05/2014 Create account Log in Article Talk Read Edit View history Search HTTP cookie From Wikipedia, the free encyclopedia Navigation A cookie, also known as an HTTP cookie, web cookie, or browser HTTP Main page cookie, is a small piece of data sent from a website and stored in a Persistence · Compression · HTTPS · Contents user's web browser while the user is browsing that website. Every time Request methods Featured content the user loads the website, the browser sends the cookie back to the OPTIONS · GET · HEAD · POST · PUT · Current events server to notify the website of the user's previous activity.[1] Cookies DELETE · TRACE · CONNECT · PATCH · Random article Donate to Wikipedia were designed to be a reliable mechanism for websites to remember Header fields Wikimedia Shop stateful information (such as items in a shopping cart) or to record the Cookie · ETag · Location · HTTP referer · DNT user's browsing activity (including clicking particular buttons, logging in, · X-Forwarded-For · Interaction or recording which pages were visited by the user as far back as months Status codes or years ago). 301 Moved Permanently · 302 Found · Help 303 See Other · 403 Forbidden · About Wikipedia Although cookies cannot carry viruses, and cannot install malware on 404 Not Found · [2] Community portal the host computer, tracking cookies and especially third-party v · t · e · Recent changes tracking cookies are commonly used as ways to compile long-term Contact page records of individuals' browsing histories—a potential privacy concern that prompted European[3] and U.S.
    [Show full text]
  • Web Crawler in Mobile Systems
    International Journal of Machine Learning and Computing, Vol. 2, No. 4, August 2012 Web Crawler in Mobile Systems Pavalam S. M., S. V. Kasmir Raja, Jawahar M., and Felix K. Akorli the crawler, Section 3 discusses the different types of Abstract—With the advent of internet technology, data has crawlers, and Section 4 explores the software used in mobile exploded to a considerable amount. Large volumes of data can phones for crawling purposes with Section 5 discusses the be explored easily through search engines, to extract valuable advantages that crawlers can bring in mobile information. Web crawlers are an indispensible part of search communications and section 6 brings out the summary. engine, which are program (proceeds with the search term) that can traverse through the hyperlinks, indexes them, parses the files and adds new links in to its queue and the mentioned process is done several times until search term vanishes from II. ARCHITECTURE OF A CRAWLER those pages. The web crawler looks for updating the links which Web crawler (also known as Spiders or robots) is software has already been indexed. This paper briefly reviews the concepts of web crawler, its architecture and its different types. that can start with a Uniform Resource Locator (known as It lists the software used by various mobile systems and also seed URL), downloads the pages with associated links and explores the ways of usage of web crawler in mobile systems and looks for the updates and stores them for later use. This reveals the possibility for further research. process is done iteratively.
    [Show full text]
  • Iris: Third-Party Authentication Service
    Iris: Third-Party Authentication Service Akshay Padmanabha Kevin Chen [email protected] [email protected] Surya Bhupatiraju Thomas Zhang [email protected] [email protected] ABSTRACT thentication and providing a centralized identification sys- Existing centralized identification systems, such as Facebook tem. To this end, we propose Iris: a web-based, secure, or Google, offer convenient services for authentication and centralized system to allow users to fully control what in- storing user information that third-party services leverage to formation they expose to third-party services, and offer full reduce friction and streamline the process of creating user transparency as to what data is collected and how it is used. profiles and logging in. However, these systems present con- flict of interests, and users may be interested in a third-party 2. PREVIOUS WORK service that focuses exclusively on authentication. To this A notable example of work towards an unbiased, third- end, we present Iris, a web-based, secure solution that re- party identification system is OpenID [6]. OpenID is a bold solves the single-point-of-failure concern and provides secure attempt in this direction, but faced many problems. One of protocols of data transmission and transparency of data us- the primary drawbacks include bad communication; it is not age. clear to end users as to how OpenID works or how it is used. Iris consists of two components: a database that holds This lack of understanding, along with poor implementation, users' information encrypted with their passphrases along security vulenerabilities, and trust issues, eventually led to with a public API to retreive this data, and a client-side OpenID becoming less and less popular.
    [Show full text]
  • Taxonomy of Mobile Web Applications from a Taxonomy and Business Analysis for Mobile Web Applications
    Chapter 3: Taxonomy of Mobile Web Applications from A Taxonomy and Business Analysis for Mobile Web Applications By Kevin Hao Liu Ph.D. Computer Science Victoria University Submitted to the System Design and Management Program in Partial Fulfillment of the Requirements for the Degree of Master of Science in Management and Engineering At the Massachusetts Institute of Technology February 2009 © 2009 Kevin H Liu. All rights reserved The author hereby grants to MIT permission to reproduce and to distribute publicly paper and electronic copies of this thesis document in whole or in part in any medium now known or hereafter created. ABSTRACT Mobile web applications refer to web applications on mobile devices, aimed at personalizing, integrating, and discovering mobile contents in user contexts. This thesis presents a comprehensive study of mobile web applications by proposing a new taxonomy for mobile web applications, and conducting a business analysis in the field of mobile web applications. The thesis reviews the current surrounding environment for mobile web applications, namely, web 2.0 and 3.0, wireless communication technology, and Smartphone platform. The recent entry and success of Apple’s iPhone greatly enhanced the public awareness of the Smartphone technology. Google’s release of open-source Android platform and T-Mobile’s deployment of Android-powered “Dream” Smartphone not only intensify the competition among suppliers, but also provide an open-source foundation for mobile web applications. This thesis introduces a new mobile web application taxonomy to systematically study the values and the groupings of the mobile web applications. By introducing features and categories, the taxonomy provides a framework so the related companies and businesses can be comparatively analyzed and summarized.
    [Show full text]
  • Webkit and Blink: Open Development Powering the HTML5 Revolution
    WebKit and Blink: Open Development Powering the HTML5 Revolution Juan J. Sánchez LinuxCon 2013, New Orleans Myself, Igalia and WebKit Co-founder, member of the WebKit/Blink/Browsers team Igalia is an open source consultancy founded in 2001 Igalia is Top 5 contributor to upstream WebKit/Blink Working with many industry actors: tablets, phones, smart tv, set-top boxes, IVI and home automation. WebKit and Blink Juan J. Sánchez Outline The WebKit technology: goals, features, architecture, code structure, ports, webkit2, ongoing work The WebKit community: contributors, committers, reviewers, tools, events How to contribute to WebKit: bugfixing, features, new ports Blink: history, motivations for the fork, differences, status and impact in the WebKit community WebKit and Blink Juan J. Sánchez WebKit: The technology WebKit and Blink Juan J. Sánchez The WebKit project Web rendering engine (HTML, JavaScript, CSS...) The engine is the product Started as a fork of KHTML and KJS in 2001 Open Source since 2005 Among other things, it’s useful for: Web browsers Using web technologies for UI development WebKit and Blink Juan J. Sánchez Goals of the project Web Content Engine: HTML, CSS, JavaScript, DOM Open Source: BSD-style and LGPL licenses Compatibility: regression testing Standards Compliance Stability Performance Security Portability: desktop, mobile, embedded... Usability Hackability WebKit and Blink Juan J. Sánchez Goals of the project NON-goals: “It’s an engine, not a browser” “It’s an engineering project not a science project” “It’s not a bundle of maximally general and reusable code” “It’s not the solution to every problem” http://www.webkit.org/projects/goals.html WebKit and Blink Juan J.
    [Show full text]
  • Webkit and Blink: Bridging the Gap Between the Kernel and the HTML5 Revolution
    WebKit and Blink: Bridging the Gap Between the Kernel and the HTML5 Revolution Juan J. Sánchez LinuxCon Japan 2014, Tokyo Myself, Igalia and WebKit Co-founder, member of the WebKit/Blink/Browsers team Igalia is an open source consultancy founded in 2001 Igalia is Top 5 contributor to upstream WebKit/Blink Working with many industry actors: tablets, phones, smart tv, set-top boxes, IVI and home automation. WebKit and Blink Juan J. Sánchez Outline 1 Why this all matters 2 2004-2013: WebKit, a historical perspective 2.1. The technology: goals, features, architecture, ports, webkit2, code, licenses 2.2. The community: kinds of contributors and contributions, tools, events 3 April 2013. The creation of Blink: history, motivations for the fork, differences and impact in the WebKit community 4 2013-2014: Current status of both projects, future perspectives and conclusions WebKit and Blink Juan J. Sánchez PART 1: Why this all matters WebKit and Blink Juan J. Sánchez Why this all matters Long time trying to use Web technologies to replace native totally or partially Challenge enabled by new HTML5 features and improved performance Open Source is key for innovation in the field Mozilla focusing on the browser WebKit and now Blink are key projects for those building platforms and/or browsers WebKit and Blink Juan J. Sánchez PART 2: 2004-2013 WebKit, a historical perspective WebKit and Blink Juan J. Sánchez PART 2.1 WebKit: the technology WebKit and Blink Juan J. Sánchez The WebKit project Web rendering engine (HTML, JavaScript, CSS...) The engine is the product Started as a fork of KHTML and KJS in 2001 Open Source since 2005 Among other things, it’s useful for: Web browsers Using web technologies for UI development WebKit and Blink Juan J.
    [Show full text]
  • Building a Browser for Automotive: Alternatives, Challenges and Recommendations
    Building a Browser for Automotive: Alternatives, Challenges and Recommendations Juan J. Sánchez Automotive Linux Summit 2015, Tokyo Myself, Igalia and Webkit/Chromium Co-founder of Igalia Open source consultancy founded in 2001 Igalia is Top 5 contributor to upstream WebKit/Chromium Working with many industry actors: automotive, tablets, phones, smart tv, set-top boxes, IVI and home automation Building a Browser for Automotive Juan J. Sánchez Outline 1 A browser for automotive: requirements and alternatives 2 WebKit and Chromium, a historical perspective 3 Selecting between WebKit and Chromium based alternatives Building a Browser for Automotive Juan J. Sánchez PART 1 A browser for automotive: requirements and alternatives Building a Browser for Automotive Juan J. Sánchez Requirements Different User Experiences UI modifications (flexibility) New ways of interacting: accessibility support Support of specific standards (mostly communication and interfaces) Portability: support of specific hardware boards (performance optimization) Functionality and completeness can be less demanding in some cases (for now) Provide both browser as an application and as a runtime Building a Browser for Automotive Juan J. Sánchez Available alternatives Option 1) Licensing a proprietary solution: might bring a reduced time-to-market but involves a cost per unit and lack of flexibility Option 2) Deriving a new browser from the main open source browser technologies: Firefox (Gecko) Chromium WebKit (Safari and others) Mozilla removed support in their engine for third
    [Show full text]
  • Apache Wookie (Incubating)
    Apache Wookie (Incubating) Creating your first widget Ross Gardler [email protected] http://incubator.apache.org/wookie Objective focussed outline • Creating a widget from the template • Running in developer mode • Modify the widget • Using external libraries • Using external APIs (not via the proxy) • Setting widget properties • Packaging for distribution Task focussed outline • Create a development environment • Create a hello world widget from supplied templates • Run Wookie in standalone mode • Edit the widget • Create a real widget with geo-lookup • Display map of current location • Store settings • Package widget as .wgt Development Environment Create Development Environment • What you need: – Wookie source code – Ant + Ivy – JDK – Your favourite editor • Javascript, HTML, CSS • Java (if you want to hack on the server) Using the Workshop CD • Copy the “wookie” folder to your preferred project location • Copy “apache-ant” into your preferred applications application directory • Install JDK from “java” folder • Configure your environment – Set ANT_HOME – Add $ANT_HOME/bin to your $PATH Your first widget Hello World! Create a Hello World Widget • Wookie comes with a skeleton widget template: cd $WOOKIE_HOME/widgets ant seed-widget • Answer some questions about your widget – Short Name: part1 – Description: Code from first practical session of Wookie training day – Default height: 320 – Default width: 200 • You now have a widget in $WOOKIE_HOME/widgets/[SHORT_NAME] Widget File Structure config.xml index.html <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="pragma" content="no-cache"/> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <title>part1</title> </head> <body> <h1>Hello World...</h1> </body> </html> Running Wookie in Developer Mode Developer mode allows easy building and testing of widgets Developer Mode • Building Wookie auto deploys all widgets in the $WOOKIE_HOME/widgets directory • We can run in development mode with: cd .
    [Show full text]
  • The Mobile Web Handbook Published 2014 by Smashing Magazine Gmbh, Freiburg, Germany
    The Mobile Web Handbook Published 2014 by Smashing Magazine GmbH, Freiburg, Germany. Printed in the EU. ISBN: 978-3-94454093-1. Cover Design, Illustrations and Layout by Stephen Hay. Copyeditor and Proofreader: Owen Gregory. Editing and Quality Control: Vitaly Friedman. eBook Production: Cosima Mielke. Typesetting: Markus Seyfferth. The Mobile Web Handbook was written by Peter-Paul Koch and reviewed by Stephanie and Bryan Rieger and Vasilis van Gemert. Links and updates of this book can be found at http://quirksmode.org/mobilewebhandbook. Get the book. Table of Contents Foreword Introduction 9 Chapter 1 The Mobile World 17 Chapter 2 Browser 45 Chapter 3 Android 67 Chapter 4 Viewports 85 Chapter 5 CSS 131 Chapter 6 Touch and Pointer Events 147 Chapter 7 Becoming a Mobile Web Developer 197 Chapter 8 The Future of the Web on Mobile 219 Introduction Introduction Introduction The Mobile Web Handbook explores the differences between mobile and desktop web development that we should be aware of when creating websites for both. It’s not very technical — there are only a dozen or so simple code examples. It discusses no libraries or tools. It’s about mobile web fundamentals. There is no mobile web distinct from the desktop web. Developing websites for mobile is pretty much the same as developing for desktop, especially now that responsive design techniques allow us to adapt our CSS layouts to both huge desktop screens and tiny mobile ones. Still, there’s “The Mobile Web” in the title of this book, and that’s not an oversight or marketing trick. It serves as a convenient shorthand for “touch-based small-screen web on more browsers than you’ve ever heard of.” Mobile web development is not fundamentally different from desktop, but there are subtle distinctions that may cause you trouble if you’re unaware of them.
    [Show full text]
  • Securegateway Server
    Open Source Used In Secure Gateway 2.26 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-135850904 Open Source Used In Secure Gateway 2.26 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-135850904 Contents 1.1 Apache Commons Codec 1.3. 1.1.1 Available under license 1.2 Apache Commons Configuration 1.6 1.2.1 Available under license 1.3 Apache Commons Lib Apache 2.0 1.3.1 Available under license 1.4 Apache HTTP Server 2.2.9 1.4.1 Available under license 1.5 Apache Jakarta Commons HttpClient 3.1 1.5.1 Available under license 1.6 Apache Jakarta Commons HttpClient 3.1 1.6.1 Available under license 1.7 Apache Log4j 1.2.16 1.7.1 Available under license 1.8 apache-log4j 1.2.15 :DUPLICATE 1.8.1 Available under license 1.9 apache-log4j 1.2.15 1.9.1 Available under license 1.10 bcprov-jdk16 1.36 1.10.1 Available under license 1.11 BouncyCastle 1.46 :ICS 1.11.1 Available under license 1.12 c3p0 0.9.1.2 1.12.1 Available under license 1.13 Codec 1.2 1.13.1
    [Show full text]
  • A Study and Comparison of Multimedia Web Searching: 1997–2006
    A Study and Comparison of Multimedia Web Searching: 1997–2006 Dian Tjondronegoro and Amanda Spink Faculty of Information Technology, Queensland University of Technology, GPO Box 2434, Brisbane, Queensland 4001, Australia. E-mail: {dian, ah.spink}@qut.edu.au Bernard J. Jansen College of Information Science and Technology, The Pennsylvania State University, State College, PA 16802. E-mail: [email protected] Searching for multimedia is an important activity for vast amounts of multimedia information, state-of-the-artWeb users of Web search engines. Studying user’s inter- searching systems need to effectively index the contents actions with Web search engine multimedia buttons, and select the most relevant documents to answer users’ including image, audio, and video, is important for the development of multimedia Web search systems. This queries that are based on the semantic or similarity percep- article provides results from a Weblog analysis study of tion. Content-based image, audio, and video search have been multimedia Web searching by Dogpile users in 2006. The given a lot of attention by researchers due to the grand chal- study analyzes the (a) duration, size, and structure of lenges in bridging the gaps between low-level audiovisual Web search queries and sessions; (b) user demograph- features and high-level semantics to support intuitive search- ics; (c) most popular multimedia Web searching terms; and (d) use of advancedWeb search techniques including ing (Lew, Sebe, Djeraba, & Jain, 2006;Yoshitaka& Ichikawa, Boolean and natural language. The current study find- 1999). ings are compared with results from previous multimedia However, despite promising research results, Web multi- Web searching studies.
    [Show full text]