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