KDE Mobile Oct 6, 2011
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Plasma on Mobile Devices
Plasma on Mobile devices Application Ecosystem MC Bhushan Shah KDE Developer Agenda ● Initial development of the Plasma Mobile ● Basic architecture details ● Advantages to KDE community ● Application ecosystem and development ● Future for Plasma Mobile ● Challenges Introduction ● KDE developer and sysadmin ● Plasma Mobile maintainer and lead developer ● Employed by Bluesystems GmbH ● From Vadodara, India KDE ● Previously known as the K Desktop Environment ● Now community, which creates free software for end users ● Several products including Plasma, KDE Frameworks, KDE applications. Plasma Mobile ● Announced in the July 2015 ● Vision of providing completely free and open-source mobile platform which respects user’s privacy and freedom. ● Initial prototype on the LG Nexus 5. Initial Development ● LGE Nexus 5 as reference device ● Ubuntu Touch 15.04 (vivid) as base system ● Makes use of the Android binary blobs / drivers ● Can also run on the desktop system for development Basic architecture details ● KWin wayland as compositor ● DRM/GBM or hwcomposer backends ● plasmashell and mobile shell package ● QtQuickControls2 and Kirigami for application development Advantages to KDE community ● Several performance improvements ● Better touch input support in applications and shell ● Improvements in Wayland support ● More modular and re-usable user interfaces Application ecosystem and development ● QtQuickControls2 and Kirigami as toolkit ● CMake/QMake as a buildsystem ● Various bundle formats as well as native distribution packaging for the distribution -
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. -
The Kdesvn Handbook
The kdesvn Handbook Rajko Albrecht The kdesvn Handbook 2 Contents 1 Introduction 7 1.1 Terms . .7 2 Using kdesvn 8 2.1 kdesvn features . .8 2.2 Beginning with subversion and kdesvn . .8 2.2.1 Creating a working copy . .9 2.2.2 Committing local changes . .9 2.2.3 Update working copy . .9 2.2.4 Adding and Deleting from working copy . .9 2.2.4.1 Add items . 10 2.2.4.2 Deleting items from working copy and unversion . 10 2.2.5 Displaying logs . 10 2.2.5.1 The log display dialog . 10 2.3 Working on repositories . 11 2.3.1 Restoring deleted items . 11 2.3.2 Importing folders . 11 2.3.2.1 With drag and drop . 11 2.3.2.2 Select folder to import with directory-browser . 11 2.4 Other Operations . 11 2.4.1 Merge . 11 2.4.1.1 Internal merge . 12 2.4.1.2 Using external program for merge . 12 2.4.2 Resolving conflicts . 12 2.5 Properties used by kdesvn for configuration . 13 2.5.1 Bugtracker integration . 13 2.6 The revision tree . 13 2.6.1 Requirements . 14 2.7 Internal log cache . 14 2.7.1 Offline mode . 14 2.7.2 Log cache and revision tree . 14 The kdesvn Handbook 2.8 Meaning of icon overlays . 14 2.9 kdesvn and passwords . 16 2.9.1 Not saving passwords . 16 2.9.2 Saving passwords in KWallet . 16 2.9.3 Saving to subversion’s own password storage . -
KDE Free Qt Foundation Strengthens Qt
How the KDE Free Qt Foundation strengthens Qt by Olaf Schmidt-Wischhöfer (board member of the foundation)1, December 2019 Executive summary The development framework Qt is available both as Open Source and under paid license terms. Two decades ago, when Qt 2.0 was first released as Open Source, this was excep- tional. Today, most popular developing frameworks are Free/Open Source Software2. Without the dual licensing approach, Qt would not exist today as a popular high-quality framework. There is another aspect of Qt licensing which is still very exceptional today, and which is not as well-known as it ought to be. The Open Source availability of Qt is legally protected through the by-laws and contracts of a foundation. 1 I thank Eike Hein, board member of KDE e.V., for contributing. 2 I use the terms “Open Source” and “Free Software” interchangeably here. Both have a long history, and the exact differences between them do not matter for the purposes of this text. How the KDE Free Qt Foundation strengthens Qt 2 / 19 The KDE Free Qt Foundation was created in 1998 and guarantees the continued availabil- ity of Qt as Free/Open Source Software3. When it was set up, Qt was developed by Troll- tech, its original company. The foundation supported Qt through the transitions first to Nokia and then to Digia and to The Qt Company. In case The Qt Company would ever attempt to close down Open Source Qt, the founda- tion is entitled to publish Qt under the BSD license. This notable legal guarantee strengthens Qt. -
Novell Corporate Presentation Template 2009
AD/Linux Desktop Improving the Experience Jim McDonough Novell/SuSE Labs Samba Team Lead [email protected] [email protected] AD Linux Desktop: The Current State Current State: Basic integration • User and group definitions – Trusts – Nested groups • Login authentication • Domain-based password policies • Ticket creation • Offline logins 3 © Novell, Inc. All rights reserved. Current State: User experience • Common Userid and Password • Password policy messages • Authentication through Kerberized applications – Firefox – Commandline utilities • Automatic access to shared folders – Through desktop > Gnome: Nautilus, gvfs, stored in gconf > KDE: Konqueror, kwin, kio – Through text-based logins > Automount > pam_mount 4 © Novell, Inc. All rights reserved. Current State: Admin Experience • User and group definition through AD tools – Common authentication possible for some apps • Secure DNS updates • Application settings for Desktops (and even Linux servers) independent of AD – Combination of text files, XML, LDAP, scripts – Parallel administration of Linux systems 5 © Novell, Inc. All rights reserved. Current State: Examples • Automatic shares – By user: > desktop window managers – By administrator: > Automounter: » stores plaintext passwords » Unmount is timeout based > pam_mount: » Obtain password through pam stack or: » Use kerberos tickets » Unmount on logout 6 © Novell, Inc. All rights reserved. Current State: Examples • Apache + mod_auth_kerb – Net ads keytab create/add HTTP – .htaccess: > AuthType Kerberos > AuthName "Krb5 Auth" > KrbServiceName HTTP > KrbVerifyKDC On > Krb5Keytab /etc/krb5.keytab > KrbAuthRealms EXAMPLE.COM > KrbMethodNegotiate on > KrbMethodK5Passwd on > require valid-user 7 © Novell, Inc. All rights reserved. Current State: Examples • Firefox – about:config or prefs.js: > network-negotiate-auth.delegation-uris > network-negotiate-auth.trusted-uris 8 © Novell, Inc. All rights reserved. Centralizing Administration Centralizing Administration • CIM/WBEM (e.g. -
Why Be a KDE Project? Martin Klapetek David Edmundson
Why be a KDE Project? Martin Klapetek David Edmundson What is KDE? KDE is not a desktop, it's a community „Community of technologists, designers, writers and advocates who work to ensure freedom for all people through our software“ --The KDE Manifesto What is a KDE Project? Project needs more than just good code What will you get as a KDE Project? Git repository Git repository plus „scratch repos“ (your personal playground) Creating a scratch repo git push –all kde:scratch/username/reponame Git repository plus web interface (using GitPHP) Git repository plus migration from Gitorious.org Bugzilla (the slightly prettier version) Review Board Integration of git with Bugzilla and Review Board Integration of git with Bugzilla and Review Board Using server-side commit hooks ● BUG: 24578 ● CCBUG: 29456 ● REVIEW: 100345 ● CCMAIL: [email protected] Communication tools Mailing lists Wiki pages Forums Single sign-on to all services Official IRC channels #kde-xxxxx (on Freenode) IRC cloak me@kde/developer/mklapetek [email protected] email address Support from sysadmin team Community support Development support Translations (71 translation teams) Testing support (Active Jenkins and EBN servers, plus Quality Team) Project continuation (when you stop developing it) KDE e.V. support Financial and organizational help Trademark security Project's licence defense via FLA Promo support Stories in official KDE News site (Got the Dot?) Your blog aggregated at Planet KDE Promo through social channels Web hosting under kde.org domain Association with one of the best -
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.... -
The Kate Handbook
The Kate Handbook Anders Lund Seth Rothberg Dominik Haumann T.C. Hollingsworth The Kate Handbook 2 Contents 1 Introduction 10 2 The Fundamentals 11 2.1 Starting Kate . 11 2.1.1 From the Menu . 11 2.1.2 From the Command Line . 11 2.1.2.1 Command Line Options . 12 2.1.3 Drag and Drop . 13 2.2 Working with Kate . 13 2.2.1 Quick Start . 13 2.2.2 Shortcuts . 13 2.3 Working With the KateMDI . 14 2.3.1 Overview . 14 2.3.1.1 The Main Window . 14 2.3.2 The Editor area . 14 2.4 Using Sessions . 15 2.5 Getting Help . 15 2.5.1 With Kate . 15 2.5.2 With Your Text Files . 16 2.5.3 Articles on Kate . 16 3 Working with the Kate Editor 17 4 Working with Plugins 18 4.1 Kate Application Plugins . 18 4.2 External Tools . 19 4.2.1 Configuring External Tools . 19 4.2.2 Variable Expansion . 20 4.2.3 List of Default Tools . 22 4.3 Backtrace Browser Plugin . 25 4.3.1 Using the Backtrace Browser Plugin . 25 4.3.2 Configuration . 26 4.4 Build Plugin . 26 The Kate Handbook 4.4.1 Introduction . 26 4.4.2 Using the Build Plugin . 26 4.4.2.1 Target Settings tab . 27 4.4.2.2 Output tab . 28 4.4.3 Menu Structure . 28 4.4.4 Thanks and Acknowledgments . 28 4.5 Close Except/Like Plugin . 28 4.5.1 Introduction . 28 4.5.2 Using the Close Except/Like Plugin . -
What's New in Qt 6 on the Desktop?
What’s new in Qt 6 on the desktop? Qt Desktop Days 2020 Giuseppe D’Angelo [email protected] About me ● Senior Software Engineer, KDAB ● Developer & Trainer ● Qt Approver ● Ask me about QtCore, QtGui, QtQuick, ... – And also about Modern C++, 3D graphics 2 The Road to Qt 6 Why Qt 6? ● Do architectural changes that simply cannot be done in Qt 5 ● Binary compatibility break – Applications must be recompiled ● Re-engineer features ● But also do some necessary housecleaning, drop ballast 4 Design Goals ● Keep as much (source) compatibility with Qt 5 as possible ● Add property bindings in C++ ● Improve QML & language bindings – Reduce overhead, increase type safety, compile to C++ ● Tackle the changing landscape in 3D APIs ● Modularize Qt even more 5 Keep the Good Parts! ● Easy to use APIs ● General purpose, cross platform application framework ● Make 90% easy to achieve, and 99.9% possible ● Excellent developer support, documentation, tooling ● Nurture the ecosystem around Qt 6 Looking ahead ● Qt 4: released 2005, EOL 2015 – ~30 modules ● Qt 5: released 2012, EOL 2023 – ~50 modules ● Qt 6: released 2020, EOL 20?? ● How to plan for the next decade? 7 Technical foundations ● C++17 – MSVC 2019, GCC 8, Apple Clang ● CMake buildsystem for Qt – qmake still supported for end user applications ● 3D API abstraction (Qt RHI) 8 Release Plan September 2020 October 2020 November 2020 December 2020 Alpha Beta Release Candidate Qt 6.0 Final Release ● Qt 6.0 feature freeze reached ● Binary weekly snapshots (already) available via the installer ● Reduced -
Engineer in C++/Qt Development ➢ Objectives
Jean-Nicolas ARTAUD 1A Rue du Vignemale 31500 Toulouse +33 (0)6.43.01.51.02 [email protected] 10 octobre 1987 Engineer in C++/Qt development ➢ Objectives ◦ Work in a dynamic environment and collaborate with communities ◦ Undertake challenging problems & take part in innovations ◦ Ensure customer satisfaction via user-centered approaches ➢ Open Source Contributions 2010 – present Calligra (The KDE generation C++/Qt integrated and free software office suite) C++/Qt development, Stage UI design. Community and meeting management. 2008 – 2010 KOffice (The C++/Qt integrated and free software office suite) KOffice development, bug fixing. 2009 – 2010 KOffice & KDE's git Migration Migration plan and script development. ➢ Professional Experience From April 2013 – Present Telespazio – One of the world’s leading players in satellite services Engineer in software development. C++/Qt development Development of a broadcast satellite system ◦ migrate software to new technologies C/C++, Qt5 ◦ UDP Network managements with the Qt Network framework ◦ migration of the database to PostgreSQL 9, SQL, trigger ◦ help in bug fixing on the web GUI in php5, JQuery, Bootstrap, Project continuous integration responsible, installation of jenkins, jobs management on several OS (Windows Server, RedHat, Debian), linux project packaging (RPM, DEB) From Sept 2010 to March 2013 Otonomy-aviation –Leading actor of High Definition entertainment camera and embedded aircraft security systems Engineer in embedded software development. C, postgresql and perl development on CPU to manage the whole system : ◦ features add, code refactoring, database management, ◦ rs232 and rs485 manipulation to make interact several devices, ◦ stand alone mode using perl scripts . PIC24f development (low power mode, sensors management, devices communication). -
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 . -
Engagiert Euch in Open Source Projekten! FOSS Projekte Statt One-Man-Vaporware
Vorteile von etablierten FOSS Projekten KDE Engagiert euch in Open Source Projekten! FOSS Projekte statt One-Man-Vaporware Milian Wolff 13.12.2010 Milian Wolff | Engagiert euch in Open Source Projekten! 1/11 Vorteile von etablierten FOSS Projekten KDE Uber¨ Mich uber¨ sechs Jahre Erfahrung als Webdeveloper mehrere Vaporware Projekte seit ca. zwei Jahren KDE Entwickler (KDevelop, Kate, ...) Milian Wolff | Engagiert euch in Open Source Projekten! 2/11 Vorteile von etablierten FOSS Projekten KDE Ubersicht¨ 1 Vorteile von etablierten FOSS Projekten 2 KDE Milian Wolff | Engagiert euch in Open Source Projekten! 3/11 Vorteile von etablierten FOSS Projekten KDE Infrastruktur VCS (git, svn, cvs, hg,...) Bugtracker Forum Mailing Listen Webseite, Wiki ... Milian Wolff | Engagiert euch in Open Source Projekten! 4/11 Vorteile von etablierten FOSS Projekten KDE Community Support Erfahrung Promo / Marketing Testing / QA Packaging Ubersetzungen¨ (i18n) Finanzielle F¨orderung, Rechtshilfe (KDE e.V.) ... Milian Wolff | Engagiert euch in Open Source Projekten! 5/11 Vorteile von etablierten FOSS Projekten KDE Events Hack Sprints Akademy / GUADEC / DesktopSummit FOSDEM / FrOSCon / LinuxTag / . Google Summer of Code Google Code In ... Milian Wolff | Engagiert euch in Open Source Projekten! 6/11 Vorteile von etablierten FOSS Projekten KDE Nutzen Erfahrung / Qualifikation / Job Freunde / Spass Feedback / Spenden ... Milian Wolff | Engagiert euch in Open Source Projekten! 7/11 Vorteile von etablierten FOSS Projekten KDE Ubersicht¨ 1 Vorteile von etablierten FOSS Projekten