docs/design.txt

Sun, 10 Jul 2011 10:44:49 +0200

author
Michael Schloh von Bennewitz <michael@schloh.com>
date
Sun, 10 Jul 2011 10:44:49 +0200
changeset 11
f83d5d4b7088
parent 0
ff1b43f833a9
permissions
-rw-r--r--

Modify icon to be square as most windowing systems expect icons to be.

michael@0 1 ____ _ _ _ _ _
michael@0 2 / ___| ___ | |__ __ _ ___ | |__ | | | || |__ _ __
michael@0 3 \___ \ / __|| '_ \ / _` | / __|| '_ \ | | | || '_ \ | '__|
michael@0 4 ___) || (__ | | | || (_| || (__ | | | || |_| || | | || |
michael@0 5 |____/ \___||_| |_| \__,_| \___||_| |_| \___/ |_| |_||_|
michael@0 6
michael@0 7 Europalab SchachUhr - Game clock graphical user interface client
michael@0 8
michael@0 9 DESIGN (IEEE 1016)
michael@0 10
michael@0 11 #D.01 SVG format is given preference...
michael@0 12 ...unless underlying software components fail to properly display it.
michael@0 13 #D.02 Two subclocks are displayed side by side like physical game clocks.
michael@0 14 #D.03 UI surface is layout optimized for mobile or semimobile devices.
michael@0 15 #D.04 Target surface size resembles the size of a phyical game clock.
michael@0 16 ...however all UI components scale to fill the entire screen.
michael@0 17 ...this conflicts with #D.01, but can be solved by maximizing
michael@0 18 use of scalable vector formats and fonts while programatically
michael@0 19 choosing the size of nonvector UI components.
michael@0 20 #D.05 UI occupies the full screen and no window decorations are shown.
michael@0 21 #D.06 The application starts by showing the initial screen, in which
michael@0 22 both subclocks are active but not running. This is due to the
michael@0 23 application now knowing which opponent will begin moving first.
michael@0 24 #D.07 To start, an opponent presses their clockface in the initial screen.
michael@0 25 This indicates which player moves first. After this exceptional
michael@0 26 step, the running subclock alternates regardless of which part
michael@0 27 of the UI surface is pressed.
michael@0 28 #D.08 To alternate the running subclock, the playing opponent presses
michael@0 29 anywhere on the UI surface (even in the nonplaying opponent's area.)
michael@0 30 #D.09 RSS indicated updates are automatically published on project homepage.
michael@8 31 #D.10 Aspect consists of minimal UI pieces arranged statically.
michael@8 32 A vertically (90 degrees rotated) title bar is flush left.
michael@8 33 A system title bar is assumed to be placed above the UI surface.
michael@8 34 Two clockfaces are placed side by side next to the vertical title bar.
michael@8 35 One text label for the opponent name is placed below each clock face.
michael@8 36 #D.11 Consideration is given to devices with several screen resolutions.
michael@8 37 820 X 480 (AppUp requirement)
michael@8 38 854 X 480 (Telephone)
michael@8 39 1024 X 600 (Ideapad)
michael@8 40 1280 X 720 (720p)
michael@8 41 1366 X 768 (WeTab)
michael@8 42 #D.12 Resolutions greater than 1366 X 768 (for example 1280 X 768)
michael@8 43 are to be served with SVG graphics only to maintain asthetics.
michael@0 44
michael@0 45 OPTIONS
michael@0 46
michael@0 47 #O.01 Main window is scalable and provides window decorations.
michael@0 48 ...this conflicts with #D.05 and must be implemented by
michael@0 49 scaling UI components as well as the UI surface.
michael@0 50 #O.02 Online update detection alerts user to pending new releases.
michael@0 51 ...this complements #D.09 but must be implemented separately.

mercurial