DOCSLIB.ORG

Threadvis for Thunderbird: a Thread Visualisation Extension for The

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Threadvis for Thunderbird: a Thread Visualisation Extension for The ThreadVis for Thunderbird A Thread Visualisation Extension for the Mozilla Thunderbird Email Client Alexander C. Hubmann-Haidvogel ThreadVis for Thunderbird A Thread Visualisation Extension for the Mozilla Thunderbird Email Client Master’s Thesis at Graz University of Technology submitted by Alexander C. Hubmann-Haidvogel Institute for Information Systems and Computer Media (IICM), Graz University of Technology A-8010 Graz, Austria 2nd September 2008 c Copyright 2008 by Alexander C. Hubmann-Haidvogel Advisor: Ao.Univ.-Prof. Dr. Keith Andrews, Graz University of Technology Co-Advisor: Dr. Matthew Chalmers, University of Glasgow ThreadVis f ¨urThunderbird Eine Thread-Visualisierungs-Erweiterung fur¨ das Mozilla Thunderbird Email-Programm Masterarbeit an der Technischen Universitat¨ Graz vorgelegt von Alexander C. Hubmann-Haidvogel Institut fur¨ Informationssysteme und Computer Medien (IICM), Technische Universitat¨ Graz A-8010 Graz 2. September 2008 c Copyright 2008, Alexander C. Hubmann-Haidvogel Diese Arbeit ist in englischer Sprache verfasst. Begutachter: Ao.Univ.-Prof. Dr. Keith Andrews, TU Graz Mitbetreuer: Dr. Matthew Chalmers, University of Glasgow Abstract Good ideas from the field of information visualisation sometimes fail to make it into everyday in- terfaces used by real people. ThreadVis incorporates the idea of a Thread Arcs visualisation of email conversations (or threads) into the popular Mozilla Thunderbird email client. Implemented as a Thunderbird add-on in JavaScript and XUL, the ThreadVis extension displays all messages in an email or newsgroup discussion in a compact visual map. The chronology of and contrib- utors to a discussion can be easily identified. The visualisation supports user interaction in navigating between messages in a thread and is synchronised with the main Thunderbird application. It is also possible to export the visual thread map in scalable vector graphics (SVG) format. Two forms of usability evaluation were used during ThreadVis development. A usage study gathered log data from 25 test participants and analysed user behaviour patterns with the software. A thinking aloud test with six test users was run to provide formative feedback. Kurzfassung Gute Ideen aus dem Feld der Informations-Visualisierung scheitern manchmal daran, in alltagliche¨ Benutzeroberflachen¨ integriert zu werden, die von echten Personen verwendet werden. ThreadVis bindet die Idee einer Thread Arcs Visualisierung von Email-Konversationen (oder Threads) in das populare¨ Email-Programm Mozilla Thunderbird ein. Als Thunderbird Add-On in JavaScript und XUL implementiert, stellt die ThreadVis Erweiterung alle Nachrichten einer Email- oder Newsgruppen-Diskussion in einer kompakten Karte dar. Die Chro- nologie und die Beteiligten einer Diskussion konnen¨ leicht identifiziert werden. Die Visualisierung un- terstutzt¨ Benutzer-Interaktion fur¨ das Navigieren zwischen Nachrichten eines Threads und ist mit der Thunderbird-Applikation synchronisiert. Es ist ebenso moglich,¨ die Thread-Abbildung im Scalable Vec- tor Graphics (SVG) Format zu exportieren. Zwei Arten von Usability-Evaluierung wurden wahrend¨ der Entwicklung von ThreadVis verwendet. Eine Benutzer-Studie sammelte Log-Daten von 25 Test-Personen und analysierte Muster im Benutzer- verhalten mit der Software. Ein Thinking-Aloud Test mit sechs Test-Personen wurde durchgefuhrt,¨ um formative Ruckmeldungen¨ zu bekommen. Pledge of Integrity I hereby certify that the work presented in this thesis is my own, that all work performed by others is appropriately declared and cited, and that no sources other than those listed were used. Place: Date: Signature: Ich versichere ehrenwortlich,¨ dass ich diese Arbeit selbstandig¨ verfasst habe, dass samtliche¨ Arbeiten von Anderen entsprechend gekennzeichnet und mit Quellenangaben versehen sind, und dass ich keine anderen als die angegebenen Quellen benutzt habe. Ort: Datum: Unterschrift: Contents Contents i Acknowledgements xiii Credits xv 1 Introduction 1 2 Information Visualisation3 2.1 Linear . .4 2.2 Hierarchies . .8 2.3 Networks . 15 2.4 Multidimensional Metadata . 17 2.5 Feature-Based Vector Spaces . 20 3 Email Readers 23 3.1 Microsoft Outlook Express and Windows Mail . 23 3.2 Microsoft Outlook . 24 3.3 Mozilla Thunderbird . 24 3.4 KMail . 25 3.5 Evolution . 25 3.6 GNUMail.app . 26 3.7 Google Mail . 26 3.8 Windows Live Hotmail . 28 3.9 Conclusion . 30 4 Email Visualisation 31 4.1 ReMail . 31 4.2 eArchivarius . 33 4.3 EzMail . 33 4.4 Social Networks . 35 4.5 faMailiar . 36 4.6 Themail . 37 4.7 Email Conversations . 39 4.8 Conclusion . 40 i 5 Thread Arcs 43 5.1 Qualities . 43 5.2 Visualisation . 44 5.3 Existing Visualisation Techniques . 45 5.4 Interaction . 47 5.5 Study . 47 5.6 Conclusion . 49 6 Thunderbird Extensions 51 6.1 XML User Interface Language (XUL) . 52 6.2 XML Binding Language (XBL) . 60 6.3 Chrome . 60 6.4 Cross Platform Component Object Model (XPCOM) . 62 6.5 Scriptable Components (XPConnect) . 64 6.6 JavaScript . 65 6.7 Package Management . 66 6.8 Updating Extensions . 69 6.9 Localisation . 70 6.10 Conclusion . 72 7 ThreadVis for Mozilla Thunderbird 73 7.1 Overview . 73 7.2 Using the Extension . 73 7.3 User Settings . 74 7.4 Implementation . 79 7.5 Goals . 79 7.6 Obstacles . 80 7.7 Caching . 80 7.8 The ThreadVis Visualisation . 80 7.9 Conclusion . 83 8 Selected Details of the Implementation 85 8.1 Threading . 85 8.2 Visualisation using XUL and Cascading Style Sheets . 86 8.3 Time Scaling . 88 8.4 Caching . 90 8.5 Conclusion . 93 9 Usage Study 95 9.1 ThreadVis Log Files . 95 9.2 Evaluation . 95 9.3 Selected Quotes . 99 9.4 Feedback . 99 9.5 Conclusion . 100 ii 10 Usability Study 101 10.1 Test Procedure . 101 10.2 Tasks . 101 10.3 Test Environment . 104 10.4 Interview Questions . 105 10.5 Discussion and Analysis . 105 10.6 Positive Findings . 106 10.7 List of Recommendations . 108 10.8 Interviews . 110 10.9 Feedback Questionnaires . 111 10.10Conclusion . 112 11 Outlook 113 12 Concluding Remarks 115 A Original Materials 117 A.1 Vertraulichkeits- und Einverstandniserkl¨ arung¨ . 117 A.2 Hintergrundbefragung . 118 A.3 Feedback Formular . 120 A.4 Test Tasks . 121 A.5 Orientation Script . ..
Load more

Recommended publications
  • 2010 Survey Results
    IT SERVICES 2010 Client Satisfaction Survey March, 2010 Acknowledgements The Stanford IT Services Client Satisfaction Team consisted of the following: Jan Cicero, Client Support Alvin Chew, Communication Services Liz Goesseringer, Business Services Tom Goodrich, Client Support Jim Knox, Facilitator, Client Support Phil Reese, Research Computing Nancy Ware, Strategic Planning Bryan Wear, Computing Services Brian McDonald, MOR Associates Chris Paquette, MOR Associates Alexis Bywater, MOR Associates MOR Associates, an external consulting firm, acted as project manager for this effort, analyzing the data and preparing this report. MOR Associates specializes in continuous improvement, strategic thinking and leadership development. MOR Associates has conducted a number of large-scale satisfaction surveys for IT organizations in higher education, including MIT, Northeastern University, the University of Chicago, and others. MOR Associates, Inc. 462 Main Street, Suite 300 Watertown, MA 02472 tel: 617.924.4501 fax: 617.924.8070 morassociates.com Brian McDonald, President [email protected] Contents Introduction. a1 Methodology . a2 Overview.of.the.Results . 1 Reading.the.Charts. 25 Customer.Service.and.Service.Attributes. 29 Research.Computing.and.IT.Services.Priorities. .33 General.Support. .41 Data.Storage.Services .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..51 Email.and.Webmail. 59 Calendaring. 63 Network.Services. 67 Telecommunications.Services. 73 Remote.Access . 83 Mobile.Devices . 87 Software. .89 Security. 93 Web.Services. 99 Appendix.A:.The.Full.Text.of.Written.Comments. .A-1 Appendix.B:.The.Survey.Instrument. B-. 1 Appendix.C:.Other.Observations . .C-1 Stanford Information Technology Services 2010 Client Survey • Introduction | a1 Introduction This report provides a summary of the purposes, the methodology and the results of the client satisfaction survey sponsored by Stanford Information Technology Services in March, 2010.
    [Show full text]
  • SMTP Protocol
    CS 280 Lecture 4: Application Layer, Email, DNS, P2P John Magee 21 September 2016 Most slides adapted from Kurose and Ross, Computer Networking 7/e Source material copyright 1996-2016 1 J.F Kurose and K.W. Ross Chapter 2: outline Last Class: 2.1 principles of network Next Class: applications 2.6 video streaming and 2.2 Web and HTTP content distribution networks Today: 2.7 socket programming with UDP and TCP 2.3 electronic mail • SMTP, POP3, IMAP 2.4 DNS 2.5 P2P applications Application Layer 2-2 outgoing Electronic mail message queue user mailbox Three major components: user agent . user agents . mail servers mail user server . simple mail transfer agent protocol: SMTP SMTP mail user server agent User Agent SMTP . a.k.a. “mail reader” SMTP user agent . composing, editing, reading mail server mail messages user . e.g., Outlook, Thunderbird, agent iPhone mail client user . outgoing, incoming agent messages stored on server Application Layer 2-3 Electronic mail: mail servers mail servers: user agent . mailbox contains incoming messages for user mail user server . message queue of outgoing agent (to be sent) mail messages SMTP mail user . SMTP protocol between server agent mail servers to send email SMTP messages SMTP user agent • client: sending mail mail server server • “server”: receiving mail user server agent user agent Application Layer 2-4 Electronic Mail: SMTP [RFC 2821] . uses TCP to reliably transfer email message from client to server, port 25 . direct transfer: sending server to receiving server . three phases of transfer • handshaking (greeting) • transfer of messages • closure . command/response interaction (like HTTP) • commands: ASCII text • response: status code and phrase .
    [Show full text]
  • Mailsite Fusion SP 10
    DATA SHEET ® MailSite Fusion SP 10 MailSite WHAT IS IT? Fusion is a low MailSite Fusion is a messaging and cost collaboration server that delivers email, calendars and contacts to Microsoft Outlook. alternative to MailSite Fusion also pushes email, calendars Hosted and contacts over-the-air to iPhone, iPad, WHAT’S NEW? Exchange that BlackBerry, Android, Windows and Nokia delivers email, smartphones. MailSite has been voted among MailSite Fusion comes bundled with a new Sync Server calendars and the top 3 mail server products by readers of that provides full support for Microsoft Outlook 2013 Windows IT Pro Magazine four times. contacts to for email, calendar and contacts. MailSite Sync Server allows you to sync multiple mobile devices with the same Microsoft HOW IS IT DIFFERENT FROM HOSTED email account, allowing you to give all your sales team Outlook, EXCHANGE? access to the sales inbox. iPhone, iPad, MailSite Fusion can scale to millions of BlackBerry, subscribers on a fully active cluster of low cost FEATURES servers. MailSite Fusion costs less than 50% of Android, Email, calendar and contact server that works great the price of Microsoft Exchange and MailSite Windows and with Microsoft Outlook Fusion can run on low cost hardware. Shared calendar server that works with Microsoft Nokia Outlook, Google Calendar, Apple iCal and Mozilla Users can access the same email, calendars smartphones Sunbird and contacts from their desktop, a web browser Customizable AJAX Web Client that works with or on the road from whichever smartphone they
    [Show full text]
  • Statement from Directtrust Regarding the EFAIL Vulnerability
    Statement from DirectTrust regarding the EFAIL Vulnerability Summary EFAIL is a set of attacks used to exploit vulnerabilities in email clients that decrypt and display PGP and S/MIME encrypted messages by coercing them into sending the decrypted text of the emails to an attacker. Properly implemented, Direct is NOT vulnerable. However, we recommend that if you are exchanging with anyone outside of the DirectTrust Network, you will want to understand at a reasonable depth how their implementation protects against EFAIL. How does EFAIL work? EFAIL consists of two different attack scenarios that create “backchannels” to send the decrypted text to an attacker. Both require an attacker to first obtain the encrypted message. 1. The attacker “wraps” the encrypted body with carefully crafted markup that can result in an email client decrypting the message and sending the decrypted body to the attacker. 2. The attacker manipulates the encrypted body of the message using well known S/MIME weaknesses that produce a message that can send the decrypted body to the attacker once rendered in the email client. Although the attacks are different, the end result is the same: a vulnerable email client sends the decrypted text to the attacker. How is this relevant to Direct? Direct uses S/MIME to encrypt messages, so in theory every Direct message could be vulnerable to this attack. However, Direct, when implemented correctly, is NOT vulnerable. The vulnerability is only applicable if decryption and rendering of the message are done in certain email clients like Thunderbird, iOS, Apple Mail, and some versions of Outlook.
    [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]
  • Electronic Evidence Examiner
    2 Table of Contents About Electronic Evidence Examiner How To .......................................................................12 How to Work with Cases .........................................................................................................13 How to Create New Case .......................................................................................................13 How to Enable Automatic Case Naming .................................................................................14 How to Define Case Name During Automatic Case Creation .................................................14 How to Open Existing Case....................................................................................................15 How to Save Case to Archive .................................................................................................16 How to Change Default Case Location ...................................................................................16 How to Add Data to Case ........................................................................................................17 How to Add Evidence .............................................................................................................18 How to Acquire Devices .........................................................................................................20 How to Import Mobile Data .....................................................................................................21 How to Import Cloud Data ......................................................................................................22
    [Show full text]
  • Leveraging Open Source Software
    1 Leveraging Open Source Software (Text of talk delivered by Justice Yatindra Singh Judge Allahabad High Court at the 9th e- Governance conference on 3rd February 2006 at Kochi, Kerala) FUD is an abbreviation of fear, uncertainty and doubt; it is often a salesman's strategy: spreading false rumours regarding others' products. Open source software (OSS) is its victim. In our country FUD for OSS arises out of ignorance. I am glad that, we are discussing OSS as it has crucial role to play in the IT world. WHAT IS OSS? A computer programme consists of two parts: Source Code and Object Code. Nowadays, computer programmes are written in high level computer languages using compact English words. This part is known as source code. These languages also have a programme called compiler and with their help, source code is compiled into machine language so that computers may understand it. When it is so done, it is called object code or machine code. Description―if it complies with certain conditions―is protected as a Copyright. Source code is a kind of description and can be protected as copyright provided it is published or disclosed. In the proprietery software, source code is generally not disclosed and in such a situation it is protected as a trade secret or undisclosed information. There was a debate whether object code is protected as a copyright or not but after TRIPS, it has to be protected as a copyright and now object code is so protected. Everyone is not using copyrights to have rights in computer programme.
    [Show full text]
  • [Hal-00744922, V1] Improving Content Availability in the I2P Anonymous
    Improving Content Availability in the I2P Anonymous File-Sharing Environment Juan Pablo Timpanaro, Isabelle Chrisment*, Olivier Festor INRIA Nancy-Grand Est, France *LORIA - ESIAL, Universit´ede Lorraine Email: fjuanpablo.timpanaro, [email protected] Email: [email protected] Abstract. Anonymous communication has gained more and more inter- est from Internet users as privacy and anonymity problems have emerged. Dedicated anonymous networks such as Freenet and I2P allow anony- mous file-sharing among users. However, one major problem with anony- mous file-sharing networks is that the available content is highly reduced, mostly with outdated files, and non-anonymous networks, such as the BitTorrent network, are still the major source of content: we show that in a 30-days period, 21648 new torrents were introduced in the BitTor- rent community, whilst only 236 were introduced in the anonymous I2P network, for four different categories of content. Therefore, how can a user of these anonymous networks access this varied and non-anonymous content without compromising its anonymity? In this paper, we improve content availability in an anonymous environment by proposing the first internetwork model allowing anonymous users to access and share content in large public communities while remaining anonymous. We show that our approach can efficiently interconnect I2P users and public BitTorrent swarms without affecting their anonymity nor their performance. Our model is fully implemented and freely usable. 1 Introduction Peer-to-peer file-sharing has always been one of the major sources of the Internet hal-00744922, version 1 - 24 Oct 2012 traffic, since its early beginnings in 2000. It has been moving from semi-central approaches (eDonkey2000, for example), to semi-decentralized approaches (Kazaa, for instance) to fully decentralized file-sharing architectures (like the KAD net- work).
    [Show full text]
  • Security with SSH.Pdf
    Security with SSH Network Startup Resource Center http://www.nsrc.org/ These materials are licensed under the Creative Commons Attribution-NonCommercial 4.0 International license (http://creativecommons.org/licenses/by-nc/4.0/) Topics • What is SSH • Where to get SSH • How to enable and configure SSH • Where to get SSH clients for Windows • Host keys: authentication of server to client • Issues to do with changing of the host key • Password authentication of client to server • Cryptographic authentication client to server • hostkey exchange, scp, and sftp labs What is SSH? From Wikipedia: Secure Shell (SSH) is a cryptographic network protocol for secure data communication, remote command-line login, remote command execution, and other secure network services between two networked computers that connects, via a secure channel over an insecure network, a server and a client (running SSH server and SSH client programs, respectively). i.e., ssh gives you a secure command line interface on remote machines… Topics • Where SSH applies directly to dealing with these two areas of security: - Confidentiality - Keeping our data safe from prying eyes • Authentication and Authorization - Is this person who they claim to be? - With keys alternative method to passwords Where to get SSH • First see if SSH is installed on your system and what version. Easiest way is: $ ssh ±V • Commonly used SSH in Linux and FreeBSD is OpenSSH. You can find the home page here: http://www.openssh.org/ • You can install OpenSSH via packages on Linux and FreeBSD. Ubuntu 12.04.3 LTS currently installs version 5.9p1 of OpenSSH. Obtain SSH Client for Windows There are several free, shareware, and commercial ssh clients for Windows.
    [Show full text]
  • Mozilla Sunbird Le Calendrier
    Mozilla Sunbird le calendrier Installation de Sunbird Dernière version traduite : SunbirdFr 0.2 finale http://frenchmozilla.sourceforge.net/calendar/#sunbird Version Windows (20/2/2005) Attention! avant d'installer la version Windows de SunbirdFr , veuillez désinstaller l'ancienne version et n'oubliez pas de supprimer également le dossier profil nommé Sunbird : • Sur Windows XP dans C:\Documents and Settings\nom utilisateur\Application Data\Mozilla ; • sur Windows 9x dans C:\Windows\Application Data\Mozilla. Si vous souhaitez conserver votre (vos) calendrier(s) veuillez sauvegarder le(s) fichier(s) *.ics se trouvant dans le dossier ...\Application Data \Mozilla \Sunbird \Profiles \xxxxxx.default \Calendar puis, après installation de la nouvelle version de SunbirdFr, replacez-les dans ce dossier. Démarrez SunbirdFr, et dans l'onglet Calendriers clic droit puis Nouveau calendrier. Recherchez le(s) fichier(s) *.ics que vous venez de replacer dans l'arborescence, sélectionnez- les l'un après l'autre et validez (même si une boîte vous signale que le fichier existe déjà !). Fichiers à télécharger au choix • Fichier *.exe (setup) permettant une installation simplifiée et personnalisable : Installeur (4,43 Mo) • Fichier *.zip à décompresser dans le dossier Program Files : Archive (5,45 Mo) Version Linux (20/2/2005) • l inuxGTK2+XFT (ne fonctionne pas avec 2.6 à moins de repasser à la version 2.4 ou inférieure, information donnée par Merinos) • l inuxGTK1 Version Mac OSX(20/2/2005) • i ci Patch affichage des mois (7/03/2005) Pour résoudre le problème d'affichage des mois de mars à août, veuillez télécharger le fichier calendar.jar (2 Mo) et le placer dans le dossier C:\Program Files\sunbird\chrome (acceptez l'écrasement du fichier en place).
    [Show full text]
  • Imail V12 Web Client Help
    Ipswitch, Inc. Web: www.imailserver.com 753 Broad Street Phone: 706-312-3535 Suite 200 Fax: 706-868-8655 Augusta, GA 30901-5518 Copyrights ©2011 Ipswitch, Inc. All rights reserved. IMail Server – Web Client Help This manual, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by such license, no part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the expressed prior written consent of Ipswitch, Inc. The content of this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Ipswitch, Inc. While every effort has been made to assure the accuracy of the information contained herein, Ipswitch, Inc. assumes no responsibility for errors or omissions. Ipswitch, Inc. also assumes no liability for damages resulting from the use of the information contained in this document. Ipswitch Collaboration Suite (ICS), the Ipswitch Collaboration Suite (ICS) logo, IMail, the IMail logo, WhatsUp, the WhatsUp logo, WS_FTP, the WS_FTP logos, Ipswitch Instant Messaging (IM), the Ipswitch Instant Messaging (IM) logo, Ipswitch, and the Ipswitch logo are trademarks of Ipswitch, Inc. Other products and their brands or company names are or may be trademarks or registered trademarks, and are the property of their respective companies. Update History December 2011 v12 April 2011 v11.5 October 2010 v11.03 May 2010 v11.02 Contents CHAPTER 1 Introduction to IMail Web Client About Ipswitch Web Messaging Help ..................................................................................................................
    [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]