aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorChristopher Michael <cpmichael1@comcast.net>2010-02-06 18:50:15 +0000
committerChristopher Michael <cpmichael1@comcast.net>2010-02-06 18:50:15 +0000
commitdd6d2d16e93b7b5e72a987d159206108894d6647 (patch)
tree4ebf8d27893a502d494fcbbd026ee17558bfa8f5 /doc
parentStart of documentation for illume2. (diff)
downloadenlightenment-dd6d2d16e93b7b5e72a987d159206108894d6647.tar.gz
More documentation for illume2.
Fix typo in E doc. SVN revision: 45939
Diffstat (limited to 'doc')
-rw-r--r--doc/documentation.html2
-rw-r--r--doc/illume2.html136
2 files changed, 137 insertions, 1 deletions
diff --git a/doc/documentation.html b/doc/documentation.html
index be308e600..158f90be9 100644
--- a/doc/documentation.html
+++ b/doc/documentation.html
@@ -102,7 +102,7 @@ code consistent and easy to follow - make it follow the style of the
rest in function naming, variable naming, access functions etc. Use
existing infrastructures - or extend them cleanly as needed. Just
because an infrastructure or system doesn't provide an accessor or
-way of doing something does NOT mean you can't or chouldn't add it.
+way of doing something does NOT mean you can't or couldn't add it.
Choose a clean “correct” implementation over a nasty hack, all
the time. You get the idea. Now, on to the style guide.</font></p>
<p style="font-family: sans-serif;" class="western"><font
diff --git a/doc/illume2.html b/doc/illume2.html
index cc7483179..d2a1c8725 100644
--- a/doc/illume2.html
+++ b/doc/illume2.html
@@ -57,11 +57,147 @@ It combines an application launcher interface along with an application
manager and switcher, as well as forcing certain simple layout policies on
applications (such as making their main windows borderless and fullscreen
except for Illume's control bar).</font></p>
+<p style="font-family: sans-serif;" class="western">
+ <font style="font-size: 8pt;">
+ <b>Please be aware that illume2 code and documentation is subject to change as ideas evolve.</b>
+ </font>
+</p>
</td>
</tr>
</tbody>
</table>
<hr style="font-family: sans-serif;">
+<p style="font-family: sans-serif;" class="western">
+ <font style="font-size: 8pt;"><b>First, let's define some terms</b>
+ </font>
+</p>
+
+<p class="western" style="margin-left: 0.79in; font-family: sans-serif;">
+ <font style="font-size: 8pt;"><b>Status Bar</b>
+ </font>
+</p>
+<p class="western" style="margin-left: 1.68in; font-family: sans-serif;">
+ <font style="font-size: 8pt;">
+ Also known as the Indicator window, this is the bar across the top of the screen that is mostly thin and holds gadgets like the battery charge, signal strength etc.
+ </font>
+</p>
+
+<p class="western" style="margin-left: 0.79in; font-family: sans-serif;">
+ <font style="font-size: 8pt;"><b>Softkey</b>
+ </font>
+</p>
+<p class="western" style="margin-left: 1.68in; font-family: sans-serif;">
+ <font style="font-size: 8pt;">
+ This is the bar at the bottom of applications that almost always has the back-button on the bottom-right and possibly other buttons for actions.
+ </font>
+</p>
+
+<p class="western" style="margin-left: 0.79in; font-family: sans-serif;">
+ <font style="font-size: 8pt;"><b>Basic App</b>
+ </font>
+</p>
+<p class="western" style="margin-left: 1.68in; font-family: sans-serif;">
+ <font style="font-size: 8pt;">
+ This is an app that has minimal or no effort made to use toolkits that support the target or the programmer just wanted to avoid writing the code to use the API’s to support it. These API’s currently draw the “status bar” and ‘softkey” at the bottom for example. These apps will not have “softkeys” or “status bars” in them. They will be simply like xterm, or for that matter any other normal linux gui app. It will work, and controls will be provided outside of the app window.
+ </font>
+</p>
+
+<p class="western" style="margin-left: 0.79in; font-family: sans-serif;">
+ <font style="font-size: 8pt;"><b>Conformant App</b>
+ </font>
+</p>
+<p class="western" style="margin-left: 1.68in; font-family: sans-serif;">
+ <font style="font-size: 8pt;">
+ This is an application that either uses the toolkits provided AND uses them appropriately to provide and/or account for controls that conform to the UI designs/standards desired for the platform.
+ </font>
+</p>
+
+<p class="western" style="margin-left: 0.79in; font-family: sans-serif;">
+ <font style="font-size: 8pt;"><b>Fullscreen App</b>
+ </font>
+</p>
+<p class="western" style="margin-left: 1.68in; font-family: sans-serif;">
+ <font style="font-size: 8pt;">
+This is a mode that any application can request for its window. This mode intends to get ALL (or as much of the screen without interference) as possible. This is useful for watching movies, games and anything else that needs screen real-estate as losing it is a major loss to the application functionality, look and feel. An application, when fullscreen, should always provide an easy/obvious way to exit or exit fullscreen mode (without requiring a keyboard).
+ </font>
+</p>
+
+<p class="western" style="margin-left: 0.79in; font-family: sans-serif;">
+ <font style="font-size: 8pt;"><b>Focused Window</b>
+ </font>
+</p>
+<p class="western" style="margin-left: 1.68in; font-family: sans-serif;">
+ <font style="font-size: 8pt;">
+This is the window that is the one that receives all keyboard input (from a physical or virtual keyboard). In X11 there can be only 1 window that has focus (ignoring MPX here).
+ </font>
+</p>
+
+<p class="western" style="margin-left: 0.79in; font-family: sans-serif;">
+ <font style="font-size: 8pt;"><b>Multihead</b>
+ </font>
+</p>
+<p class="western" style="margin-left: 1.68in; font-family: sans-serif;">
+ <font style="font-size: 8pt;">
+This is a mode of X11 display where you can have 2 root windows on 2 screens. They can be different sizes (resolutions) even different screen depths (one 8bit, one 16bit for example). Input is managed with each root window having mouse input sent as if it were a stand-alone xserver screeen except that the mouse and keyboard can only be active on 1 of the root windows at once, and the mouse exits the other root window screen when it enders the current one.
+ </font>
+</p>
+
+<p class="western" style="margin-left: 0.79in; font-family: sans-serif;">
+ <font style="font-size: 8pt;"><b>Xinerama</b>
+ </font>
+</p>
+<p class="western" style="margin-left: 1.68in; font-family: sans-serif;">
+ <font style="font-size: 8pt;">
+ This is a modern multi-screen display system for X11 where you have a single framebuffer (a single root window) where 1 or more screens “view” regions of that root window. This means all screens have the same depth (all 16bit or all 32bit or all 8bit), but they can be different resolutions. The single keyboard and mouse input is handled as if it were 1 big screen with 2 input regions and 1 keyboard attached.
+ </font>
+</p>
+
+<p class="western" style="margin-left: 0.79in; font-family: sans-serif;">
+ <font style="font-size: 8pt;"><b>Policy</b>
+ </font>
+</p>
+<p class="western" style="margin-left: 1.68in; font-family: sans-serif;">
+ <font style="font-size: 8pt;">
+ Illume2 allows for layout code to be seperated into a 'policy'. Policies are modularized code (very similiar to Enlightenment modules) that handle arranging windows on screen. Illume2 allows for dynamic switching of the active policy.
+ </font>
+</p>
+
+
+<p style="font-family: sans-serif;" class="western">
+ <font style="font-size: 8pt;"><b>Policies</b>
+ </font>
+</p>
+<p class="western" style="margin-left: 0.79in; font-family: sans-serif;">
+ <font style="font-size: 8pt;"><b>Requirements</b> (please note that these requirements are subject to change)
+ </font>
+</p>
+<p class="western" style="margin-left: 1.68in; font-family: sans-serif;">
+ <font style="font-size: 8pt;">
+ A policy is <b>required</b> to implement 2 basic functions so that illume2 may dynamically load it:
+ <ul>
+ <li><b>init</b> - This is the function that illume2 will call to initialize the policy. It is expected that in here the policy will assign any other functions it handles.</li>
+ <li><b>shutdown</b> - This function will be called by illume2 when the policy is being unloaded. This occurs when policy is changed to a different one, or when illume2 module is unloaded. This is the ideal place for a policy to do any cleanup it needs to.</li>
+ </ul>
+ </font>
+</p>
+<p class="western" style="margin-left: 1.68in; font-family: sans-serif;">
+ <font style="font-size: 8pt;">
+ A policy may <b>optionally</b> implement the following functions:
+ <ul>
+ <li><b>border_add</b> - This function gets called by illume2 when a border is added to the screen.</li>
+ <li><b>border_del</b> - This function gets called by illume2 when a border is removed from the screen.</li>
+ <li><b>border_focus_in</b> - This function gets called by illume2 when a border receives focus.</li>
+ <li><b>border_focus_out</b> - This function gets called by illume2 when a border losses focus.</li>
+ <li><b>border_activate</b> - This function gets called by illume2 when a border is activated (usually from a NETWM ACTIVATE request).</li>
+ <li><b>border_property_change</b> - This function gets called by illume2 when a property on any given border changes. This is ideal for handling events like a border changing between fullscreen and non-fullscreen.</li>
+ <li><b>zone_layout</b> - This function gets called by illume2 when the actual screen layout needs updating. Typically used to position windows.</li>
+ <li><b>zone_move_resize</b> - This function gets called by illume2 when a zone gets moved or resized. Typically called when the screen resolution changes.</li>
+ <li><b>drag_start</b> - This function gets called by illume2 when the indicator window gets moved by the user.</li>
+ <li><b>drag_end</b> - This function gets called by illume2 when the indicator window is finished moving (in response to the user moving it).</li>
+ </ul>
+ </font>
+</p>
+
</body>
</html>