# HG changeset patch # User Michael Schloh von Bennewitz # Date 1310231643 -7200 # Node ID 6fe6d3548766922234060203b6f9bba5e7e74185 # Parent 10758789e5728eb704303cd024d9e4e1a687a249 Remember changed logic in release and refine requirements and design. diff -r 10758789e572 -r 6fe6d3548766 docs/changelog.txt --- a/docs/changelog.txt Sat Jul 09 09:48:07 2011 +0200 +++ b/docs/changelog.txt Sat Jul 09 19:14:03 2011 +0200 @@ -12,6 +12,12 @@ 00000000 Release version 1.0.0 + 20110700 Release version 0.6.2 + Increase delay of hand placement + + 20110708 Release version 0.6.1 + Correct packaging dependencies + 20110708 Release version 0.6.0 Implement prototype logic Develop build framework diff -r 10758789e572 -r 6fe6d3548766 docs/design.txt --- a/docs/design.txt Sat Jul 09 09:48:07 2011 +0200 +++ b/docs/design.txt Sat Jul 09 19:14:03 2011 +0200 @@ -28,6 +28,19 @@ #D.08 To alternate the running subclock, the playing opponent presses anywhere on the UI surface (even in the nonplaying opponent's area.) #D.09 RSS indicated updates are automatically published on project homepage. + #D.10 Aspect consists of minimal UI pieces arranged statically. + A vertically (90 degrees rotated) title bar is flush left. + A system title bar is assumed to be placed above the UI surface. + Two clockfaces are placed side by side next to the vertical title bar. + One text label for the opponent name is placed below each clock face. + #D.11 Consideration is given to devices with several screen resolutions. + 820 X 480 (AppUp requirement) + 854 X 480 (Telephone) + 1024 X 600 (Ideapad) + 1280 X 720 (720p) + 1366 X 768 (WeTab) + #D.12 Resolutions greater than 1366 X 768 (for example 1280 X 768) + are to be served with SVG graphics only to maintain asthetics. OPTIONS diff -r 10758789e572 -r 6fe6d3548766 docs/requirements.txt --- a/docs/requirements.txt Sat Jul 09 09:48:07 2011 +0200 +++ b/docs/requirements.txt Sat Jul 09 19:14:03 2011 +0200 @@ -15,37 +15,42 @@ EXTERNAL REQUIREMENTS + #R.01 Proportions and graphic accuracy is maintained on + a variety of mobile devices and screen sizes. + FUNCTIONAL REQUIREMENTS - #R.01 Two opponents use the chess clock to help judge the chess match. - #R.02 Functions and UI are configurable, persistent in user's homedir. - #R.03 Each opponent can choose their name, shown on their clock. - #R.04 Names of well known chess strategists are offered as examples. - #R.05 The subclock positions can be swapped at any time. - #R.06 Each opponent can choose one of eight colours for their clock. - #R.07 Each opponent can choose how many minutes to allocate for their match. - #R.08 Display of the hour hand is optional. - #R.09 Display of the second hand is optional. - #R.10 Display of numbers on the clockfaces is optional. - #R.11 Optional audio output indicates which subclock is running. - #R.12 The complete configuration state can be stored and given a name. - #R.13 The complete configuration can be restored from several stored states. - #R.14 The initial state optionally restores the last known configuration. - #R.15 Times of well known chess game types (blitz) are offered as examples. - #R.16 Static text of the interface is adapted to the user's current locale. - #R.17 The locale used in translating static text can be chosen in the GUI. - #R.18 A well visible timer flag falls to indicate each opponent's expiration. - #R.19 Both subclocks can be paused at the same time during the match. - #R.20 All user interaction is limited to basic operation for ease of use. - #R.21 Features can be learned quickly by those knowlegable with game clocks. - #R.22 Online and offline documentation describes the application. - #R.23 Built in help aides the user as well as a traditional manpage. - #R.24 Routinely released updates distribute new features and correct flaws. + #R.02 Two opponents use the chess clock to help judge the chess match. + #R.03 Functions and UI are configurable, persistent in user's homedir. + #R.04 Each opponent can choose their name, shown on their clock. + #R.05 Names of well known chess strategists are offered as examples. + #R.06 The subclock positions can be swapped at any time. + #R.07 Each opponent can choose one of eight colours for their clock. + #R.08 Each opponent can choose how many minutes to allocate for their match. + #R.09 Display of the hour hand is optional. + #R.10 Display of the second hand is optional. + #R.11 Display of numbers on the clockfaces is optional. + #R.12 Optional audio output indicates which subclock is running. + #R.13 The complete configuration state can be stored and given a name. + #R.14 The complete configuration can be restored from several stored states. + #R.15 The initial state optionally restores the last known configuration. + #R.16 Times of well known chess game types (blitz) are offered as examples. + #R.17 Static text of the interface is adapted to the user's current locale. + #R.18 The locale used in translating static text can be chosen in the GUI. + #R.19 A well visible timer flag falls to indicate each opponent's expiration. + #R.20 Both subclocks can be paused at the same time during the match. + #R.21 All user interaction is limited to basic operation for ease of use. + #R.22 Features can be learned quickly by those knowlegable with game clocks. + #R.23 Online and offline documentation describes the application. + #R.24 Built in help aides the user as well as a traditional manpage. + #R.25 Routinely released updates distribute new features and correct flaws. PERFORMANCE REQUIREMENTS DESIGN CONSTRAINTS + #R.26 UI consists of a vertical titlebar and two clockfaces with text labels. + SOFTWARE SYSTEM ATTRIBUTES OTHER REQUIREMENTS