DOCSLIB.ORG

Carmedia Technical Documentation Updated 15/01/2011 SVN Revision N° 466

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Carmedia Technical Documentation Updated 15/01/2011 SVN Revision N° 466 CarMedia Technical Documentation Updated 15/01/2011 SVN Revision n° 466 Summary 1. Introduction ...................................................................................................................................... 3 2. Get the source code .......................................................................................................................... 3 2.1. Data Structure ........................................................................................................................... 3 3. Source code documentation ............................................................................................................. 4 4. Compile the source code .................................................................................................................. 4 4.1. Mandatory ................................................................................................................................ 4 4.2. Compile on GNU/Linux ........................................................................................................... 4 4.2.1. Get the Qt dev libraries ..................................................................................................... 4 4.2.2. Compile ............................................................................................................................ 4 4.3. Compile on Windows ............................................................................................................... 5 4.3.1. Mandatory ......................................................................................................................... 5 4.3.2. Compile ............................................................................................................................ 5 5. Design .............................................................................................................................................. 5 5.1. Car -> Arduino -> CarMedia .................................................................................................... 5 5.2. Events ....................................................................................................................................... 5 5.3. Sensors ..................................................................................................................................... 6 5.3.1. Classes .............................................................................................................................. 6 5.3.2. Communication with the car ............................................................................................. 7 5.4. Plugins ...................................................................................................................................... 7 5.4.1. Create a plugin .................................................................................................................. 8 6. Bugs ................................................................................................................................................. 9 1. Introduction CarMedia is a software application designed to be embedded in a car become the dashboard and/or multimedia center. The application core can retrieve and display real time values from the censors of the car (fuel, speed, number of turns/second, etc...). It is also possible with the API displayed in this document to add others plugins. CarMedia is developed in C++ with Nokia's Qt framework (http://qt.nokia.com/). QtCore, QtGui and QtNetwork plugins are used. For the multimedia part, we use the Phonon framework (http://fr.wikipedia.org/wiki/Phonon_(KDE)), which is cross-platform multimedia framework written for KDE who relies on Qt. CarMedia is designed to be cross-platform, we use it on Windows & GNU/Linux. Note: This documentation is intended to the SVN revision that you can find on the first page. 2. Gets the source code Given that no stable version has been released actually, you have to retrieve the source code with the SVN at this URL: https://labeip.epitech.net/svn/2011/carmedia/. On GNU/Linux, you can download the data with this command line: svn checkout https://labeip.epitech.net/svn/2011/carmedia/trunk carmedia On Windows you can use a SVN client like TortoiseSVN (http://fr.wikipedia.org/wiki/Comparaison_des_clients_pour_Subversion). 2.1. Data Structure Structure of the main folder: • arduino/ => Source code that the Arduino run. • carmedia/ => Source code of the sofware. ◦ core/ => Folder with source code of the application core. ▪ images/ => Folder with the pictures used by the application. ▪ Locales/ => Folder with language files of the application. ▪ src/ => C++ source code of the application. ▪ core.pro => Qmake project file. Used to compil the application. ▪ core.qrc => File used to link images and binary. ◦ doc/ => Folder with documentation. ◦ plugins/ => Folder with source codes of the plugins. ◦ carmedia.dox => Configuration file for Doxygen. ◦ carmedia.pro => Qmake project file. Calls core/core.pro and plugins/*/*.pro. 3. Source code documentation The most important classes of CarMedia are documented with Doxygen (http://www.stack.nl/~dimitri/doxygen/). Doxygen is a documentation generator, it parses the source code, extract the comments generates documentation in HTML, LaTeX, PDF, etc... We will produce that documentation at each release. It is advised to create it once you have downloaded the data on the SVN. 4. Compile the source code 4.1. Mandatory To create a CarMedia binary you need to have: • A C++ compilator • The Qt framework >= 4.6 4.2. Compiling on GNU/Linux 4.2.1. Get the Qt dev libraries Each GNU/Linux distribution comes with a package manager. On Fedora: yum install gcc-c++ qt4-devel On Debian: apt-get install qt4-dev-tools 4.2.2. Compiling The Qt framework is cross platforms, The Qt program generates a platform-specific project file. On GNU/Linux it will be a Makefile. Run the commands below into the carmedia/ folder. Qmake # Generates the Makefile. make # Run the compilation. ./carmedia # Run the application binary. 4.3. Compiling on Windows 4.3.1. Mandatory The simplest way to create a CarMedia binary on Windows is to use Qt Creator. Download the Qt SDK (Software Development Kit) at the url: http://qt.nokia.com/downloads/sdk- windows-cpp. Then install it with the defaults options. 4.3.2. Compiling To create a CarMedia binary, run Qt Creator and open the file carmedia/carmedia.pro. It will load the project (the application core and plugins). Choose « Compiler » on the Start Menu then « Runs » (or CTRL+R). 5. Architecture 5.1. Car -> Arduino -> CarMedia To retrieve the values of the sensors in the car, we use a programmable hardware piece called Arduino (http://www.arduino.cc). The source code run by the Arduino is located in the folder arduino/. In this documentation, we only focus on the core of CarMedia, how to add plugins and how to get values form the censors. 5.2. Events The CarMedia application works by events. It uses the Qt signalx/slots and especially an object called EventBus. The event bus is designed to communicate the informations between objects unreferenced to each other. An object subscribes for an event, and then when it occurs, the object is automatically notified when the event happens. Below the object EventBus: class EventBus { public: EventBus(); ~EventBus(); private: EventBus(const EventBus&); EventBus& operator=(const EventBus&); public: void addHandler(QEvent::Type type, QObject* pHandler); void removeHandler(QEvent::Type type, QObject* pHandler); void emitEvent(Event* pEvent); void emitEventRightNow(Event* pEvent); private: static QMap<QEvent::Type,QList<QObject*> > msHandlers; static QReadWriteLock msHandlersLock; }; The addHandler() and removeHandler() methods are called for subscribe and unsubscribe to an events. Both methods take as parameters an event type and an object. Event types are described in carmedia/core/src/events/eventtypes.h. The object must inherit QObject class and is notified of the event by the method event(). There are many examples in the plugins and especially in plugins/videoplayerplugin. The emitEvent() method allow to emit an event in the application. The event passed as parameter is sent to all handlers. It is sent by the Qt event system, thus in the Qt main scope. Th emitEventRightNow() method works like emitEvent() but the events are not sent in the Qt main scope. They are immediately sent to theirs handlers 5.3. Sensors CarMedia allows to display the values from differents censors of the car. At this time we support two modes and one norm. It means that we are able to generate random values or get the censor values with the network. Both ways the CarMedia application will receive the same data format. In a near future it will be possible to add others modes and norms with the plugins. 5.3.1. Classes Below the classes used by the sensors. • IDevice => Device Interface. ◦ DefaultDevice => Creates a Thread. ▪ SerialPortDevice => To handle the devices on serial port. ▪ NetworkDevice => To handle the networked devices. • ISensors => Interface to stack the censors values. ◦ DefaultSensors => Implements Isensors, with the list of cesnsors. • IProtocol => To handle the evolutions of the communication protocol with the Arduino. ◦ CarmediaProtocolV0001 => First version of protocol. ◦ CarmediaProtocolV0002 => Second version of protocol. Here is a schema about the classes : IDevice IProtocol ISensor Parses that data Get the data from Verifies the values the device and send and send
Load more

Recommended publications
  • Red Hat Enterprise Linux 6 Developer Guide
    Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Dave Brolley William Cohen Roland Grunberg Aldy Hernandez Karsten Hopp Jakub Jelinek Developer Guide Jeff Johnston Benjamin Kosnik Aleksander Kurtakov Chris Moller Phil Muldoon Andrew Overholt Charley Wang Kent Sebastian Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Edition 0 Author Dave Brolley [email protected] Author William Cohen [email protected] Author Roland Grunberg [email protected] Author Aldy Hernandez [email protected] Author Karsten Hopp [email protected] Author Jakub Jelinek [email protected] Author Jeff Johnston [email protected] Author Benjamin Kosnik [email protected] Author Aleksander Kurtakov [email protected] Author Chris Moller [email protected] Author Phil Muldoon [email protected] Author Andrew Overholt [email protected] Author Charley Wang [email protected] Author Kent Sebastian [email protected] Editor Don Domingo [email protected] Editor Jacquelynn East [email protected] 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/. 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.
    [Show full text]
  • Kde-Guide-De-Developpement.Web.Pdf
    KDE Published : 2017-06-26 License : GPLv2+ 1 KDE DU POINT DE VUE D'UN DÉVELOPPEUR 1. AVEZ-VOUS BESOIN DE CE LIVRE ? 2. LA PHILOSOPHIE DE KDE 3. COMMENT OBTENIR DE L'AIDE 2 1. AVEZ-VOUS BESOIN DE CE LIVRE ? Vous devriez lire ce livre si vous voulez développer pour KDE. Nous utilisons le terme développement très largement pour couvrir tout ce qui peut conduire à un changement dans le code source, ce qui inclut : Soumettre une correction de bogue Écrire une nouvelle application optimisée par la technologie KDE Contribuer à un projet existant Ajouter de la fonctionnalité aux bibliothèques de développement de KDE Dans ce livre, nous vous livrerons les bases dont vous avez besoin pour être un développeur productif. Nous décrirons les outils que vous devrez installer, montrer comment lire la documentation (et écrire la vôtre propre, une fois que vous aurez créé la nouvelle fonctionnalité !) et comment obtenir de l'aide par d'autres moyens. Nous vous présenterons la communauté KDE, qui est essentielle pour comprendre KDE parce que nous sommes un projet « open source », libre (gratuit). Les utilisateurs finaux du logiciel n'ont PAS besoin de ce livre ! Cependant, ils pourraient le trouver intéressant pour les aider à comprendre comment les logiciels complexes et riches en fonctionnalités qu'ils utilisent ont vu le jour. 3 2. LA PHILOSOPHIE DE KDE Le succès de KDE repose sur une vue globale, que nous avons trouvée à la fois pratique et motivante. Les éléments de cette philosophie de développement comprennent : L'utilisation des outils disponibles plutôt que de ré-inventer ceux existants : beaucoup des bases dont vous avez besoin pour travailler font déjà partie de KDE, comme les bibliothèques principales ou les « Kparts », et sont tout à fait au point.
    [Show full text]
  • KDE Galaxy 4.13
    KDE Galaxy 4.13 - Devaja Shah About Me ●3rd Year Alienatic Student at DA- !"# Gandhinagar ●Dot-editor %or KDE &romo "ea' ●Member of KDE e.(. ●&a))ion for Technology# Literature ●+un the Google Developer Group in !olle$e ●-rganizin$ Tea' of KDE Meetup# con%./de.in 14 -/ay, sooooo....... ●Ho1 many of you are %an) of Science Fiction3 ●Astronomy3 ● 0o1 is it Related to KDE3 ●That i) precisely 1hat the talk is about. ●Analogy to $et you to kno1 everythin$ that you should about ● “Galaxy KDE 4.13” 4ait, isn't it 4.14? ●KDE5) late)t ver)ion S! 4.14 6 7ove'ber 8914 ●KDE Soft1are !o',ilation ::.xx ●Significance o% +elea)e) ●- -r$ani.ed# )y)te'atic co',ilation o% %eature) < develo,'ent) ●- 2ive )erie) of relea)e) till date. ●7o Synchronized +elea)e) Any lon$er: ● - KDE 2ra'e1ork) > ?'onthly@ ● - KDE &la)'a > ?3 'onth)@ ● - KDE Ap,lication) ?date ba)ed@ ●Au)t *i/e Ap, (er)ion) But, 1hat am I to do o% the Galaxy 7umber? ●4ork in a "eam ●4ork acros) a Deadline ●-%;ce Space Si'ulation ●Added 'petus %or Deliverin$ your 2eature) ●You 1ork a) a ,art of the C!oreD Developer "ea' ● nstils Discipline ●Better +e),onse# Better 2eedbac/ ●Better Deliverance ●Synchronized 1ork with other C)ea)onedD developer) Enough of the bore....... ●Ho1 do $et started3 ● - Hope you didn't )nooze yesterday ● +!# Subscribe to Mailing Lists ●Mentoring Progra') ●GsoC# Season of KDE, O2W Progra') ●Bootstra,pin$ Training Session) Strap yourself onto the Rocket ●And Blast O%%......... ● ● ● Entered A 4ormhole and Ea,ped into the KDE Galaxy ●No1 what? ●Pick a Planet to nhabit ●But....
    [Show full text]
  • Kdesrc-Build Script Manual
    kdesrc-build Script Manual Michael Pyne Carlos Woelz kdesrc-build Script Manual 2 Contents 1 Introduction 8 1.1 A brief introduction to kdesrc-build . .8 1.1.1 What is kdesrc-build? . .8 1.1.2 kdesrc-build operation ‘in a nutshell’ . .8 1.2 Documentation Overview . .9 2 Getting Started 10 2.1 Preparing the System to Build KDE . 10 2.1.1 Setup a new user account . 10 2.1.2 Ensure your system is ready to build KDE software . 10 2.1.3 Setup kdesrc-build . 12 2.1.3.1 Install kdesrc-build . 12 2.1.3.2 Prepare the configuration file . 12 2.1.3.2.1 Manual setup of configuration file . 12 2.2 Setting the Configuration Data . 13 2.3 Using the kdesrc-build script . 14 2.3.1 Loading project metadata . 14 2.3.2 Previewing what will happen when kdesrc-build runs . 14 2.3.3 Resolving build failures . 15 2.4 Building specific modules . 16 2.5 Setting the Environment to Run Your KDEPlasma Desktop . 17 2.5.1 Automatically installing a login driver . 18 2.5.1.1 Adding xsession support for distributions . 18 2.5.1.2 Manually adding support for xsession . 18 2.5.2 Setting up the environment manually . 19 2.6 Module Organization and selection . 19 2.6.1 KDE Software Organization . 19 2.6.2 Selecting modules to build . 19 2.6.3 Module Sets . 20 2.6.3.1 The basic module set concept . 20 2.6.3.2 Special Support for KDE module sets .
    [Show full text]
  • CALL for SPONSORS for the KDE Developers and Contributors Conference 2006 (In Dublin, Ireland, 23Th to 30Th of September)
    CALL FOR SPONSORS for the KDE Developers and Contributors Conference 2006 (in Dublin, Ireland, 23th to 30th of September) About KDE KDE is one of the largest and most active projects in the Free Software world. For almost ten years it has delivered a powerful and easy-to-use graphical desktop environment and spplications for Linux and other UNIX systems. Be- hind KDE there is a vibrant community of software developers, translators, ar- KDE is a graphical desktop environment tists, usability experts and committed users, a community that continually pro- aimed at both home and professional ves that Free Software can be of world-class quality. use. Under constant development since its founding in 1996, KDE has evolved into an integrated workplace with lots of About aKademy Developing KDE 4 applications working together, and regu- larly receives user awards. Since KDE is aKademy is the name of the yearly KDE This year‘s aKademy will focus on get- Open Source software, anyone interes- world summit. This conference is a ting KDE 4 into shape. ted can download its source code and unique opportunity for many KDE cont- KDE 4 is the next major release of KDE have a look at how particular features ributors to meet each other in person. and will raise the bar for desktop devel- are implemented. Due to KDE being At aKademy, they can share quality time opers by providing unique frameworks Open Source software, KDE relies on discussing various KDE related issues, for the storage of personal information the contribution of volunteers. Having working together on KDE, and last but (Akonadi [http://pim.kde.org/akonadi/]), the source code available, together with not least, strengthening the hardware abstraction (Solid [http:// extensive documentation, allows develo- community.
    [Show full text]
  • Qt Quick – Overview and Basic GUI SERIOUS ABOUT SOFTWARE Timo Strömmer, Jan 3, 2011 1 Contents
    Qt Quick – Overview and basic GUI SERIOUS ABOUT SOFTWARE Timo Strömmer, Jan 3, 2011 1 Contents • Quick start • Environment installation, • Hello world • Qt Quick overview • Qt Quick components • QML language overview • Qt modules overview • Programming with QML • Basic concepts and GUI elements Creating a hello world project with QtCreator QUICK START 3 Installation • Qt SDK mess • http://qt.nokia.com/downloads/downloads • Latest Qt meant for desktop • http://www.forum.nokia.com/Develop/Qt/ • Meant for mobile devices (but not desktop) • Only ”preliminary support for Qt 4.7” • Will be merged into one product in the future 4 Installation • Install Qt 4.7 from Ubuntu repositories • Needed, for running in desktop • sudo apt-get install build-essential libqt4-dev qt4-qmlviewer • Download and install the forum Nokia version of Nokia Qt SDK • Run qtcreator • ~/NokiaQtSDK/QtCreator/bin/qtcreator 5 Installation • Select Help / About plugins from menu • Enable QmlDesigner and re-start qtcreator 6 Installation • Check Tools / Options that Qt libraries exist • Rebuild debug helper for C++ development 7 Quick start • Select File / New File or Project 8 Quick start 9 Quick start 10 Quick start 11 Quick start • Run the program with Ctrl+R 12 Excercise • Try it out, create and run a QML application project • Add some other text entries • Optional: Add an image 13 Overview QT QUICK 14 What is Qt Quick • QML – a language for UI design and development • Qt declarative – Module for integrating QML and Qt C++ libraries • Qt Creator tools – Complete development
    [Show full text]
  • Migrating from Qt 4 to Qt 5
    Migrating from Qt 4 to Qt 5 Nils Christian Roscher-Nielsen Product Manager, The Qt Company David Faure Managing Director and migration expert, KDAB France 2 © 2015 Moving to Qt 5 Motivation • New user interface requirements • Embedded devices • New technologies available • 7 years of Qt 4 • Time to fix many smaller and larger issues with a new major release 3 © 2015 QML / Qt Quick Age of the new User Interfaces • New industry standards • More devices than ever • 60 frames per seconds • Multi modal interaction • Enter the SceneGraph • Powerful QML User Interfaces • Full utilization of OpenGL hardware • Full control of your User Interface on all devices 4 © 2015 Embedded Devices Qt powers the world • Qt Platform Abstraction • Enables easy porting to any platform or operating system • Modular architecture • Easier to tailor for embedded HW • Boot to Qt • Premade embedded Linux based stack for device creation • Device deployment • Greatly improved tooling • On device debugging and profiling 5 © 2015 Wide Platform support • Seamless experiences across all major platforms • Windows, Mac, Linux • Windows Phone, iOS and Android • Jolla, Tizen, Ubuntu Touch, BB10, and more • VxWorks and QNX • High DPI Support • Dynamic GL switching • Simplified deployment process • Charts and 3D Visualization • Location and positioning 6 © 2015 Increased speed of development For your own applications and for Qt itself • Qt Creator 3 • Stable Plugin API • Qt Quick Designer • QML Profiler • Modularization • More stable and reliable Qt code base • Faster module development • Easier to create and maintain new modules • Qt Open Governance model 7 © 2015 Qt UI Offering – Choose the Best of All Worlds Qt Quick Qt Widgets Web / Hybrid C++ on the back, declarative UI Customizable C++ UI controls for Use HTML5 for dynamic web design (QML) in the front for traditional desktop look-and-feel.
    [Show full text]
  • Glossary.Pdf
    2 Contents 1 Glossary 4 3 1 Glossary Technologies Akonadi The data storage access mechanism for all PIM (Personal Information Manager) data in KDE SC 4. One single storage and retrieval system allows efficiency and extensibility not possible under KDE 3, where each PIM component had its own system. Note that use of Akonadi does not change data storage formats (vcard, iCalendar, mbox, maildir etc.) - it just provides a new way of accessing and updating the data.</p><p> The main reasons for design and development of Akonadi are of technical nature, e.g. having a unique way to ac- cess PIM-data (contacts, calendars, emails..) from different applications (e.g. KMail, KWord etc.), thus eliminating the need to write similar code here and there.</p><p> Another goal is to de-couple GUI applications like KMail from the direct access to external resources like mail-servers - which was a major reason for bug-reports/wishes with regard to perfor- mance/responsiveness in the past.</p><p> More info:</p><p> <a href=https://community.kde.org/KDE_PIM/Akonadi target=_top>Akonadi for KDE’s PIM</a></p><p> <a href=https://en.wikipedia.org/wiki/Akonadi target=_top>Wikipedia: Akonadi</a></p><p> <a href=https://techbase.kde.org/KDE_PIM/Akonadi target=_top>Techbase - Akonadi</a> See Also "GUI". See Also "KDE". Applications Applications are based on the core libraries projects by the KDE community, currently KDE Frameworks and previously KDE Platform.</p><p> More info:</p><p> <a href=https://community.kde.org/Promo/Guidance/Branding/Quick_Guide/ target=_top>KDE Branding</a> See Also "Plasma".
    [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]
  • * His Is the Original Ubuntuguide. You Are Free to Copy This Guide but Not to Sell It Or Any Derivative of It. Copyright Of
    * his is the original Ubuntuguide. You are free to copy this guide but not to sell it or any derivative of it. Copyright of the names Ubuntuguide and Ubuntu Guide reside solely with this site. This guide is neither sold nor distributed in any other medium. Beware of copies that are for sale or are similarly named; they are neither endorsed nor sanctioned by this guide. Ubuntuguide is not associated with Canonical Ltd nor with any commercial enterprise. * Ubuntu allows a user to accomplish tasks from either a menu-driven Graphical User Interface (GUI) or from a text-based command-line interface (CLI). In Ubuntu, the command-line-interface terminal is called Terminal, which is started: Applications -> Accessories -> Terminal. Text inside the grey dotted box like this should be put into the command-line Terminal. * Many changes to the operating system can only be done by a User with Administrative privileges. 'sudo' elevates a User's privileges to the Administrator level temporarily (i.e. when installing programs or making changes to the system). Example: sudo bash * 'gksudo' should be used instead of 'sudo' when opening a Graphical Application through the "Run Command" dialog box. Example: gksudo gedit /etc/apt/sources.list * "man" command can be used to find help manual for a command. For example, "man sudo" will display the manual page for the "sudo" command: man sudo * While "apt-get" and "aptitude" are fast ways of installing programs/packages, you can also use the Synaptic Package Manager, a GUI method for installing programs/packages. Most (but not all) programs/packages available with apt-get install will also be available from the Synaptic Package Manager.
    [Show full text]
  • Towards Left Duff S Mdbg Holt Winters Gai Incl Tax Drupal Fapi Icici
    jimportneoneo_clienterrorentitynotfoundrelatedtonoeneo_j_sdn neo_j_traversalcyperneo_jclientpy_neo_neo_jneo_jphpgraphesrelsjshelltraverserwritebatchtransactioneventhandlerbatchinsertereverymangraphenedbgraphdatabaseserviceneo_j_communityjconfigurationjserverstartnodenotintransactionexceptionrest_graphdbneographytransactionfailureexceptionrelationshipentityneo_j_ogmsdnwrappingneoserverbootstrappergraphrepositoryneo_j_graphdbnodeentityembeddedgraphdatabaseneo_jtemplate neo_j_spatialcypher_neo_jneo_j_cyphercypher_querynoe_jcypherneo_jrestclientpy_neoallshortestpathscypher_querieslinkuriousneoclipseexecutionresultbatch_importerwebadmingraphdatabasetimetreegraphawarerelatedtoviacypherqueryrecorelationshiptypespringrestgraphdatabaseflockdbneomodelneo_j_rbshortpathpersistable withindistancegraphdbneo_jneo_j_webadminmiddle_ground_betweenanormcypher materialised handaling hinted finds_nothingbulbsbulbflowrexprorexster cayleygremlintitandborient_dbaurelius tinkerpoptitan_cassandratitan_graph_dbtitan_graphorientdbtitan rexter enough_ram arangotinkerpop_gremlinpyorientlinkset arangodb_graphfoxxodocumentarangodborientjssails_orientdborientgraphexectedbaasbox spark_javarddrddsunpersist asigned aql fetchplanoriento bsonobjectpyspark_rddrddmatrixfactorizationmodelresultiterablemlibpushdownlineage transforamtionspark_rddpairrddreducebykeymappartitionstakeorderedrowmatrixpair_rddblockmanagerlinearregressionwithsgddstreamsencouter fieldtypes spark_dataframejavarddgroupbykeyorg_apache_spark_rddlabeledpointdatabricksaggregatebykeyjavasparkcontextsaveastextfilejavapairdstreamcombinebykeysparkcontext_textfilejavadstreammappartitionswithindexupdatestatebykeyreducebykeyandwindowrepartitioning
    [Show full text]
  • Ubuntu:Precise Ubuntu 12.04 LTS (Precise Pangolin)
    Ubuntu:Precise - http://ubuntuguide.org/index.php?title=Ubuntu:Precise&prin... Ubuntu:Precise From Ubuntu 12.04 LTS (Precise Pangolin) Introduction On April 26, 2012, Ubuntu (http://www.ubuntu.com/) 12.04 LTS was released. It is codenamed Precise Pangolin and is the successor to Oneiric Ocelot 11.10 (http://ubuntuguide.org/wiki/Ubuntu_Oneiric) (Oneiric+1). Precise Pangolin is an LTS (Long Term Support) release. It will be supported with security updates for both the desktop and server versions until April 2017. Contents 1 Ubuntu 12.04 LTS (Precise Pangolin) 1.1 Introduction 1.2 General Notes 1.2.1 General Notes 1.3 Other versions 1.3.1 How to find out which version of Ubuntu you're using 1.3.2 How to find out which kernel you are using 1.3.3 Newer Versions of Ubuntu 1.3.4 Older Versions of Ubuntu 1.4 Other Resources 1.4.1 Ubuntu Resources 1.4.1.1 Unity Desktop 1.4.1.2 Gnome Project 1.4.1.3 Ubuntu Screenshots and Screencasts 1.4.1.4 New Applications Resources 1.4.2 Other *buntu guides and help manuals 2 Installing Ubuntu 2.1 Hardware requirements 2.2 Fresh Installation 2.3 Install a classic Gnome-appearing User Interface 2.4 Dual-Booting Windows and Ubuntu 1 of 212 05/24/2012 07:12 AM Ubuntu:Precise - http://ubuntuguide.org/index.php?title=Ubuntu:Precise&prin... 2.5 Installing multiple OS on a single computer 2.6 Use Startup Manager to change Grub settings 2.7 Dual-Booting Mac OS X and Ubuntu 2.7.1 Installing Mac OS X after Ubuntu 2.7.2 Installing Ubuntu after Mac OS X 2.7.3 Upgrading from older versions 2.7.4 Reinstalling applications after
    [Show full text]