--- /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: Configurability</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_vision1_integration.html" title="Previous page">
+ <link rel="next" href="slide_vision3_innovation.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: Configurability</div>
+ <a href="toc.html" accesskey="t">toc</a> ||
+ <a href="index.html" accesskey="s">start</a> ||
+ <a href="slide_vision1_integration.html" accesskey="p">< prev</a> |
+ <a href="slide_vision3_innovation.html" id="goNext" accesskey="n">next ></a>
+</div>
+
+<h1>SeaMonkey Vision: Configurability</h1>
+
+<div class="simplebox">
+<ul>
+ <li>Provide choice to power users through a reasonable set of
+ <span class="hilite">configurable and customizable</span> features paired
+ with extensibility through add-ons
+ <ul>
+ <li>Power users, being one of the main target groups of SeaMonkey, should
+ be able to <span class="hilite">choose what functionality</span> they
+ want to use in what way.</li>
+ <li>At the same time, the amount of options must be kept
+ <span class="hilite">comprehensible</span> for users that not yet
+ accustomed to everything SeaMonkey has to offer and managable for the
+ team writing and maintaining the code.</li>
+ <li>Development of SeaMonkey <span class="hilite">add-ons</span> should
+ be made as easy as possible, for example through providing similar or
+ the same APIs as Firefox and Thunderbird for add-on developers.</li>
+ <li>Everything normal SeaMonkey users need to tweak should be available
+ in <span class="hilite">UI preferences</span>, things only a small
+ minority of very advanced users want to change should not be in
+ standard preferences UI.</li>
+ <li>Add-ons should be able to <span class="hilite">easily extend,
+ configure and customize</span> functionality.</li>
+ </ul>
+ </li>
+</ul>
+</div>
+
+</body>
+</html>
projects / slides.git / blobdiff