DOCSLIB.ORG

Akonadi-Opensync2008.Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Akonadi-Opensync2008.Pdf Why rewrite the foundation of KDE PIM? KResource ● Designed 10 years ago for small amounts of data ● Synchronous access ● No code sharing ● Hard to extend ● No change notifications ● No shared data ● (Ab-)Used way beyond its capabilities Goals ● Fix all of the above ● Provide a unified API to access PIM data, independent of the actual data source ● Provide flexible cache policies for remote data ● Fast virtual folders, representing search results ● Usable for the whole free desktop Chaos Design Server ● Fully type independent ● Caches remote data ● Change notifications ● Conflict detection ● Based on MySQL ● Depends only on Qt Protocol ● Data access – Based on IMAP – Optimized for high throuput – Data encoded using standard formats ● Change notification, control methods – D-Bus – Optimized for easy use ● Platform and toolkit independent Basic Objects ● Filesystem-like structure – Collections – Items ● Items consist of – A payload, consisting of one or more parts – Arbitrary attributes Client Library ● libakonadi: Qt/KDE based – C++ – Ruby – Python – C# ● Mostly type-independent ● Type-specific plugins API ● Low-level – Job based – Asynchronous ● High-level – Qt Model/View ● Change monitoring and recording/replay Resource Agents ● Connect Akonadi to external data sources – Local files (ical, vcard, maildir,...) – Mail or groupware servers – Web services (facebook, del.ico.us, ...) ● Translate data formats ● Replay offline changes Other Agents ● Implement functionalitry not limited to a single application ● Operate autonomously on PIM data ● Examples – Indexing – Mail threading – Filtering – ... Status ● Server and client library first released with KDE 4.1 ● First users: Mailody, KPilot ● Supported types: – Mail – Contacts – Calendar – RSS feeds – Bookmarks Roadmap for KDE 4.2 ● Use Akonadi for contacts and calendar data for all of KDE PIM ● Limit porting work by using KResource <-> Akonadi bridges – Allows to use KResource based backends with Akonadi – Transparent for old applications .
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]
  • Implementation of Proactive Spam Fighting Te Niques
    Implementation of Proactive Spam Fighting Teniques Masterarbeit von Martin Gräßlin Rupret-Karls-Universität Heidelberg Betreuer: Prof. Dr. Gerhard Reinelt Prof. Dr. Felix Freiling 03. März 2010 Ehrenwörtlie Erklärung I versiere, dass i diese Masterarbeit selbstständig verfasst, nur die angegebenen ellen und Hilfsmiel verwendet und die Grundsätze und Empfehlungen „Verantwortung in der Wissensa“ der Universität Heidelberg beatet habe. Ort, Datum Martin Gräßlin Abstract One of the biggest allenges in global communication is to overcome the problem of unwanted emails, commonly referred to as spam. In the last years many approaes to reduce the number of spam emails have been proposed. Most of them have in common that the end-user is still required to verify the filtering results. ese approaes are reactive: before mails can be classified as spam in a reliable way, a set of similar mails have to be received. Spam fighting has to become proactive. Unwanted mails have to be bloed before they are delivered to the end-user’s mailbox. In this thesis the implementation of two proactive spam fighting teniques is discussed. e first concept, called Mail-Shake, introduces an authentication step before a sender is allowed to send emails to a new contact. Computers are unable to authenticate themselves and so all spam messages are automatically bloed. e development of this concept is discussed in this thesis. e second concept, called Spam Templates, is motivated by the fact that spam messages are generated from a common template. If we gain access to the template we are able to identify spam messages by mating the message against the template.
    [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]
  • Metadata Track Akonadi the Independent Solution for PIM Data
    Akonadi – The independent solution for PIM GCDS 2009 data Metadata track Akonadi the independent solution for PIM data Will Stephenson Will Stephenson Akonadi – The independent solution for PIM GCDS 2009 data Akonadi Topics Akona-what? Design Overview What we give you What you give us Will Stephenson Akonadi – The independent solution for PIM GCDS 2009 data Akonadi The story so far Monolithic apps Own data storage Limited if any external interfaces E-D-S Data storage service Limited range of types supported Will Stephenson Akonadi – The independent solution for PIM GCDS 2009 data Why? Limitations of KDE3 KResource framework limitations: Data is not shared Designed for synchronous access Hard to extend to other data types Basically no shared common code KMail limitations: Only limited backend abstraction Designed for small amounts of local data Will Stephenson Akonadi – The independent solution for PIM GCDS 2009 data Scalability with KDE 3 |Data| = small Contact applet KAddressBook l l KMail Kopete Will Stephenson Akonadi – The independent solution for PIM GCDS 2009 data Scalability in KDE 3 |Data| = large Contact applet KAddressBook l l KMail Kopete Will Stephenson Akonadi – The independent solution for PIM GCDS 2009 data Why? Goals As much as possible shared, type independent functionality Easy to extend to new data types Unified API to access PIM data, independent of the actual data source Scalability Will Stephenson Akonadi – The independent solution for PIM GCDS 2009 data Why? Goals One synchronization point for mobile devices Reliable,
    [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]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • KDE E.V. Quarterly Report 2008Q1/Q2
    KDE e.V. Quarterly Report Q1/2008 & Q2/2008 .init() home for KDE e.V. to call its own but a tremendous asset in Claudia who Dear KDE e.V. member, has rapidly made herself at home in our community providing much needed logistical support and business The first two quarters of 2008 were very busy ones for development effort while diving head-first into the KDE participants. Both the technology project and KDE e.V. community by joining our events and tradeshow teams. We were bustling with activity. are happy to welcome Claudia into our community and our team. The obvious stand-out moment was when KDE 4.0 was released at an immensely successful release event held in In short, the first half of 2008 was busy and full of pleasant Mountain View, California - where Google served as our surprises and achievements. KDE e.V. found ways to be hosts and numerous locations around the world tuned in more efficient and increase our pace to keep up with the to join us live over the Internet. Besides creating new technology project's own escalation. Looking forward to community bonds and bringing together developers from the second half of the year with Akademy 2008 just around various projects and companies in and outside of the KDE the corner, it's safe to say that things aren't about to slow project, it also spawned what will be an annual KDE down, either. Americas event at the beginning of each year. To our membership and partners: thank you for helping Work to ensure Akademy 2008 went off successfully was making the start of 2008 such a positive and productive also in high gear as KDE 4.1 was being readied for release.
    [Show full text]
  • Akonadi – Pimpin' Your PIM Till Adam / Volker Krause Akonadi – Pimpin' Your PIM Foss.In 2007 Akonadi
    Akonadi – Pimpin' your PIM Till Adam / Volker Krause Akonadi – Pimpin' your PIM foss.in 2007 Akonadi Topics ● Akona-what? ● Design Overview ● What we give you ● What you give us Till Adam / Volker Krause Akonadi – Pimpin' your PIM foss.in 2007 Akonadi A bit of history Till Adam / Volker Krause Akonadi – Pimpin' your PIM foss.in 2007 Why? Limitations of KDE3 ● KResource framework limitations: ● Data is not shared ● Designed for synchronous access ● Hard to extend to other data types ● Basically no shared common code ● KMail limitations: ● Only limited backend abstraction ➔ Designed for small amounts of local data Till Adam / Volker Krause Akonadi – Pimpin' your PIM foss.in 2007 Why? Goals ● As much as possible shared, type independent functionality ● Easy to extend to new data types ● Unified API to access PIM data, independent of the actual data source ● Scalability Till Adam / Volker Krause Akonadi – Pimpin' your PIM foss.in 2007 Why? Goals ● One synchronization point for mobile devices ● Reliable, desktop wide notification ● Clean model/view separation (UI-less data access) ● Easy to write access libraries for ➔ Usable for the whole free desktop Till Adam / Volker Krause Akonadi – Pimpin' your PIM foss.in 2007 Why? Enabling new use cases “show me the log of the last IRC chat I had with the person who send me this mail” Till Adam / Volker Krause Akonadi – Pimpin' your PIM foss.in 2007 Why? Enabling new use cases “show me all mails with pdf attachments mentioning my hamster 'cookie' right here inside my IM client, whenever someone mentions chicken curry” Till Adam / Volker Krause Akonadi – Pimpin' your PIM foss.in 2007 Why? Enabling new use cases “tell me when I get new mail in this folder and this other folder, and show it on the desktop, but only if it's not from my mom.
    [Show full text]
  • What's New in KDE SC
    RevieWs KDE SC 4.4 What’s new in KDE SC 4.4 FOUR-IN-HAND fmatte, photocase.com fmatte, Version 4.4 sees the KDE Software Compilation reach a status on par puzzle bench lets you create your own puzzles, giving you a free choice of the with the user friendliness and stability of good old KDE 3.5. On top of number of parts (Figure 3). Palapeli au- tomatically remembers your progress in this, many features are new. BY MARCEL HILZINGER completing the puzzles. You can thus work on multiple puzzles, or new puzzle f you have not looked at an open line feature allows users to compose designs, concurrently. source operating system for a year, postings at any time. iyou probably won’t recognize any- The KDE-Edu educational set includes New system Components thing. Projects disappear and new ones two new programs: Cantor and Rocs. KDE always had an address book, but take their place; a tool or library that is The Cantor math tool (Figure 2) lets you the tool that comes with KDE SC 4.4 is today’s buzz can be obsolete tomorrow. compose math worksheets. By default, practically a new program. Its author is KDE users experienced this situation Cantor relies on the internal KAlgebra KDE PIM developer Tobias König, who is when the desktop warped from version back end, although it 3.x to 4.x. Early 4.x releases showed supports the free Maxima promise, but none could achieve the sta- [3] and Sage [4] educa- Online. Easy. Secure. Reliable bility and versatility of the late 3.x se- tional systems.
    [Show full text]
  • Kmail 2 Be Released?
    Why do we need Akonadi in KMail? What is Akonadi? How will KMail be ported? When will KMail 2 be released? KMail 2 The Road to Akonadi Thomas McGuire July 5th 2009 Thomas McGuire – KMail 2 – 1/23 Why do we need Akonadi in KMail? What is Akonadi? How will KMail be ported? When will KMail 2 be released? Outline 1 Why do we need Akonadi in KMail? 2 What is Akonadi? 3 How will KMail be ported? 4 When will KMail 2 be released? Thomas McGuire – KMail 2 – 2/23 Why do we need Akonadi in KMail? What is Akonadi? How will KMail be ported? When will KMail 2 be released? About Me About Me Student of computer science at the University of Siegen KDE developer since 2007 KMail Maintainer since 2008 KDAB employee Thomas McGuire – KMail 2 – 3/23 Why do we need Akonadi in KMail? What is Akonadi? How will KMail be ported? When will KMail 2 be released? Outline 1 Why do we need Akonadi in KMail? 2 What is Akonadi? 3 How will KMail be ported? 4 When will KMail 2 be released? Thomas McGuire – KMail 2 – 4/23 Why do we need Akonadi in KMail? What is Akonadi? How will KMail be ported? When will KMail 2 be released? About KMail About KMail Official KDE Mail Client, part of Kontact Now over 12 years old Geared towards power users Second highest bug count on bugs.kde.org High Bug Count? Many bugs caused by the aging storage layer Bug count also reflects popularity KMail works OK except for corner cases Thomas McGuire – KMail 2 – 5/23 Why do we need Akonadi in KMail? What is Akonadi? How will KMail be ported? When will KMail 2 be released? History of KMail A look into
    [Show full text]
  • Red Hat Enterprise Linux 7 7.9 Release Notes
    Red Hat Enterprise Linux 7 7.9 Release Notes Release Notes for Red Hat Enterprise Linux 7.9 Last Updated: 2021-08-17 Red Hat Enterprise Linux 7 7.9 Release Notes Release Notes for Red Hat Enterprise Linux 7.9 Legal Notice Copyright © 2021 Red Hat, Inc. 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. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. 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. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [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]