| cc144c07 |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> |
| 2 | <html> |
| 3 | <head> |
| 4 | <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15"> |
| 5 | <meta name="Author" content="KaiRo - Robert Kaiser"> |
| 6 | <title>SeaMonkey 2 & The Vision Beyond - Vision: Integration</title> |
| 7 | <link rel="stylesheet" type="text/css" href="slides.css"> |
| 8 | <script type="text/javascript" src="slides.js"></script> |
| 9 | <link rel="contents" href="index.html" title="Contents"> |
| 10 | <link rel="index" href="toc.html" title="Overview"> |
| 11 | <link rel="start" href="index.html" title="Start"> |
| 12 | <link rel="first" href="slide_introduction.html" title="First page"> |
| 13 | <link rel="previous" href="slide_quovadis.html" title="Previous page"> |
| 14 | <link rel="next" href="slide_vision2_configurability.html" title="Next page"> |
| 15 | <link rel="last" href="slide_end.html" title="Last page"> |
| 16 | </head> |
| 7cc3f32f |
17 | <body> |
| cc144c07 |
18 | <div id="header"><div id="header-text">SeaMonkey 2 & The Vision Beyond</div> |
| 19 | <img src="template/header-logo.png" height="38" width="260" alt=""> |
| 20 | </div> |
| 21 | <div id="slidenav"><div id="subheader-text">Vision: Integration</div> |
| 22 | <a href="toc.html" accesskey="t">toc</a> || |
| 23 | <a href="index.html" accesskey="s">start</a> || |
| 24 | <a href="slide_quovadis.html" accesskey="p">< prev</a> | |
| 25 | <a href="slide_vision2_configurability.html" id="goNext" accesskey="n">next ></a> |
| 26 | </div> |
| 27 | |
| 28 | <h1>SeaMonkey Vision: Integration</h1> |
| 29 | |
| 30 | <div class="simplebox"> |
| 31 | <ul> |
| 32 | <li>Strengthen and <span class="hilite">improve integration</span> of the |
| 33 | core SeaMonkey components with each other, as well as with optional |
| 34 | components and add-ons |
| 35 | <ul> |
| 36 | <li>Despite the software having a technical split into components, |
| 37 | SeaMonkey should feel as a <span class="hilite">single |
| 38 | application</span> with tightly connected features.</li> |
| 39 | <li>Browsing and messaging are the primary parts that need to be tightly |
| 40 | connected, but optional components/add-ons like web tools, calendaring |
| 41 | and others should also feel like they are an |
| 42 | <span class="hilite">integral part</span> of the application once they |
| 43 | are installed.</li> |
| 5bfe14de |
44 | <li>We should investigate an <span class="hilite">"everything can be a |
| cc144c07 |
45 | tab" metaphor</span> that spans not just websites in the browser, but |
| 46 | messages/conversations, application parts (preferences?) and anything |
| 47 | else that sounds reasonable, possibly all running within a single |
| 48 | SeaMonkey window.</li> |
| 49 | <li>The user experience should be <span class="hilite">consistent</span> |
| 50 | in all parts of the SeaMonkey application, including a set of |
| 51 | preferences that affects all those components at once.</li> |
| 52 | </ul> |
| 53 | </li> |
| 54 | </ul> |
| 55 | </div> |
| 56 | |
| 57 | </body> |
| 58 | </html> |
projects / slides.git / blame