--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+ <meta name="Author" content="KaiRo - Robert Kaiser">
+ <title>SeaMonkey 2 & The Vision Beyond - Vision: Integration</title>
+ <link rel="stylesheet" type="text/css" href="slides.css">
+ <script type="text/javascript" src="slides.js"></script>
+ <link rel="contents" href="index.html" title="Contents">
+ <link rel="index" href="toc.html" title="Overview">
+ <link rel="start" href="index.html" title="Start">
+ <link rel="first" href="slide_introduction.html" title="First page">
+ <link rel="previous" href="slide_quovadis.html" title="Previous page">
+ <link rel="next" href="slide_vision2_configurability.html" title="Next page">
+ <link rel="last" href="slide_end.html" title="Last page">
+</head>
+<body onLoad="document.body.onclick = docClicked;">
+<div id="header"><div id="header-text">SeaMonkey 2 & The Vision Beyond</div>
+ <img src="template/header-logo.png" height="38" width="260" alt="">
+</div>
+<div id="slidenav"><div id="subheader-text">Vision: Integration</div>
+ <a href="toc.html" accesskey="t">toc</a> ||
+ <a href="index.html" accesskey="s">start</a> ||
+ <a href="slide_quovadis.html" accesskey="p">< prev</a> |
+ <a href="slide_vision2_configurability.html" id="goNext" accesskey="n">next ></a>
+</div>
+
+<h1>SeaMonkey Vision: Integration</h1>
+
+<div class="simplebox">
+<ul>
+ <li>Strengthen and <span class="hilite">improve integration</span> of the
+ core SeaMonkey components with each other, as well as with optional
+ components and add-ons
+ <ul>
+ <li>Despite the software having a technical split into components,
+ SeaMonkey should feel as a <span class="hilite">single
+ application</span> with tightly connected features.</li>
+ <li>Browsing and messaging are the primary parts that need to be tightly
+ connected, but optional components/add-ons like web tools, calendaring
+ and others should also feel like they are an
+ <span class="hilite">integral part</span> of the application once they
+ are installed.</li>
+ <li>We should investigate a <span class="hilite">"everything can be a
+ tab" metaphor</span> that spans not just websites in the browser, but
+ messages/conversations, application parts (preferences?) and anything
+ else that sounds reasonable, possibly all running within a single
+ SeaMonkey window.</li>
+ <li>The user experience should be <span class="hilite">consistent</span>
+ in all parts of the SeaMonkey application, including a set of
+ preferences that affects all those components at once.</li>
+ </ul>
+ </li>
+</ul>
+</div>
+
+</body>
+</html>
projects / slides.git / blobdiff