switch URLs in all slides from mozdev to kairo.at
[slides.git] / fosdem2009 / slide_vision2_configurability.html
cc144c07 1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
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 &amp; The Vision Beyond - Vision: Configurability</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_vision1_integration.html" title="Previous page">
14 <link rel="next" href="slide_vision3_innovation.html" title="Next page">
15 <link rel="last" href="slide_end.html" title="Last page">
7cc3f32f 17<body>
cc144c07 18<div id="header"><div id="header-text">SeaMonkey 2 &amp; The Vision Beyond</div>
19 <img src="template/header-logo.png" height="38" width="260" alt="">
21<div id="slidenav"><div id="subheader-text">Vision: Configurability</div>
22 <a href="toc.html" accesskey="t">toc</a> ||
23 <a href="index.html" accesskey="s">start</a> ||
24 <a href="slide_vision1_integration.html" accesskey="p">&lt; prev</a> |
25 <a href="slide_vision3_innovation.html" id="goNext" accesskey="n">next &gt;</a>
28<h1>SeaMonkey Vision: Configurability</h1>
30<div class="simplebox">
32 <li>Provide choice to power users through a reasonable set of
33 <span class="hilite">configurable and customizable</span> features paired
34 with extensibility through add-ons
35 <ul>
36 <li>Power users, being one of the main target groups of SeaMonkey, should
37 be able to <span class="hilite">choose what functionality</span> they
38 want to use in what way.</li>
39 <li>At the same time, the amount of options must be kept
3ee78fbb 40 <span class="hilite">comprehensible</span> for users that are not yet
cc144c07 41 accustomed to everything SeaMonkey has to offer and managable for the
42 team writing and maintaining the code.</li>
43 <li>Development of SeaMonkey <span class="hilite">add-ons</span> should
44 be made as easy as possible, for example through providing similar or
45 the same APIs as Firefox and Thunderbird for add-on developers.</li>
46 <li>Everything normal SeaMonkey users need to tweak should be available
47 in <span class="hilite">UI preferences</span>, things only a small
48 minority of very advanced users want to change should not be in
49 standard preferences UI.</li>
50 <li>Add-ons should be able to <span class="hilite">easily extend,
51 configure and customize</span> functionality.</li>
52 </ul>
53 </li>