Schuhr Sources / changeset

     1.1 --- a/docs/changelog.txt	Sat Jul 09 09:48:07 2011 +0200
     1.2 +++ b/docs/changelog.txt	Sat Jul 09 19:14:03 2011 +0200
     1.3 @@ -12,6 +12,12 @@
     1.4  
     1.5    00000000  Release version 1.0.0
     1.6  
     1.7 +  20110700  Release version 0.6.2
     1.8 +            Increase delay of hand placement
     1.9 +
    1.10 +  20110708  Release version 0.6.1
    1.11 +            Correct packaging dependencies
    1.12 +
    1.13    20110708  Release version 0.6.0
    1.14              Implement prototype logic
    1.15              Develop build framework

     2.1 --- a/docs/design.txt	Sat Jul 09 09:48:07 2011 +0200
     2.2 +++ b/docs/design.txt	Sat Jul 09 19:14:03 2011 +0200
     2.3 @@ -28,6 +28,19 @@
     2.4    #D.08 To alternate the running subclock, the playing opponent presses
     2.5          anywhere on the UI surface (even in the nonplaying opponent's area.)
     2.6    #D.09 RSS indicated updates are automatically published on project homepage.
     2.7 +  #D.10 Aspect consists of minimal UI pieces arranged statically.
     2.8 +        A vertically (90 degrees rotated) title bar is flush left.
     2.9 +        A system title bar is assumed to be placed above the UI surface.
    2.10 +        Two clockfaces are placed side by side next to the vertical title bar.
    2.11 +        One text label for the opponent name is placed below each clock face.
    2.12 +  #D.11 Consideration is given to devices with several screen resolutions.
    2.13 +        820 X 480 (AppUp requirement)
    2.14 +        854 X 480 (Telephone)
    2.15 +        1024 X 600 (Ideapad)
    2.16 +        1280 X 720 (720p)
    2.17 +        1366 X 768 (WeTab)
    2.18 +  #D.12 Resolutions greater than 1366 X 768 (for example 1280 X 768)
    2.19 +        are to be served with SVG graphics only to maintain asthetics.
    2.20  
    2.21    OPTIONS
    2.22  

     3.1 --- a/docs/requirements.txt	Sat Jul 09 09:48:07 2011 +0200
     3.2 +++ b/docs/requirements.txt	Sat Jul 09 19:14:03 2011 +0200
     3.3 @@ -15,37 +15,42 @@
     3.4  
     3.5    EXTERNAL REQUIREMENTS
     3.6  
     3.7 +  #R.01 Proportions and graphic accuracy is maintained on
     3.8 +        a variety of mobile devices and screen sizes.
     3.9 +
    3.10    FUNCTIONAL REQUIREMENTS
    3.11  
    3.12 -  #R.01 Two opponents use the chess clock to help judge the chess match.
    3.13 -  #R.02 Functions and UI are configurable, persistent in user's homedir.
    3.14 -  #R.03 Each opponent can choose their name, shown on their clock.
    3.15 -  #R.04 Names of well known chess strategists are offered as examples.
    3.16 -  #R.05 The subclock positions can be swapped at any time.
    3.17 -  #R.06 Each opponent can choose one of eight colours for their clock.
    3.18 -  #R.07 Each opponent can choose how many minutes to allocate for their match.
    3.19 -  #R.08 Display of the hour hand is optional.
    3.20 -  #R.09 Display of the second hand is optional.
    3.21 -  #R.10 Display of numbers on the clockfaces is optional.
    3.22 -  #R.11 Optional audio output indicates which subclock is running.
    3.23 -  #R.12 The complete configuration state can be stored and given a name.
    3.24 -  #R.13 The complete configuration can be restored from several stored states.
    3.25 -  #R.14 The initial state optionally restores the last known configuration.
    3.26 -  #R.15 Times of well known chess game types (blitz) are offered as examples.
    3.27 -  #R.16 Static text of the interface is adapted to the user's current locale.
    3.28 -  #R.17 The locale used in translating static text can be chosen in the GUI.
    3.29 -  #R.18 A well visible timer flag falls to indicate each opponent's expiration.
    3.30 -  #R.19 Both subclocks can be paused at the same time during the match.
    3.31 -  #R.20 All user interaction is limited to basic operation for ease of use.
    3.32 -  #R.21 Features can be learned quickly by those knowlegable with game clocks.
    3.33 -  #R.22 Online and offline documentation describes the application.
    3.34 -  #R.23 Built in help aides the user as well as a traditional manpage.
    3.35 -  #R.24 Routinely released updates distribute new features and correct flaws.
    3.36 +  #R.02 Two opponents use the chess clock to help judge the chess match.
    3.37 +  #R.03 Functions and UI are configurable, persistent in user's homedir.
    3.38 +  #R.04 Each opponent can choose their name, shown on their clock.
    3.39 +  #R.05 Names of well known chess strategists are offered as examples.
    3.40 +  #R.06 The subclock positions can be swapped at any time.
    3.41 +  #R.07 Each opponent can choose one of eight colours for their clock.
    3.42 +  #R.08 Each opponent can choose how many minutes to allocate for their match.
    3.43 +  #R.09 Display of the hour hand is optional.
    3.44 +  #R.10 Display of the second hand is optional.
    3.45 +  #R.11 Display of numbers on the clockfaces is optional.
    3.46 +  #R.12 Optional audio output indicates which subclock is running.
    3.47 +  #R.13 The complete configuration state can be stored and given a name.
    3.48 +  #R.14 The complete configuration can be restored from several stored states.
    3.49 +  #R.15 The initial state optionally restores the last known configuration.
    3.50 +  #R.16 Times of well known chess game types (blitz) are offered as examples.
    3.51 +  #R.17 Static text of the interface is adapted to the user's current locale.
    3.52 +  #R.18 The locale used in translating static text can be chosen in the GUI.
    3.53 +  #R.19 A well visible timer flag falls to indicate each opponent's expiration.
    3.54 +  #R.20 Both subclocks can be paused at the same time during the match.
    3.55 +  #R.21 All user interaction is limited to basic operation for ease of use.
    3.56 +  #R.22 Features can be learned quickly by those knowlegable with game clocks.
    3.57 +  #R.23 Online and offline documentation describes the application.
    3.58 +  #R.24 Built in help aides the user as well as a traditional manpage.
    3.59 +  #R.25 Routinely released updates distribute new features and correct flaws.
    3.60  
    3.61    PERFORMANCE REQUIREMENTS
    3.62  
    3.63    DESIGN CONSTRAINTS
    3.64  
    3.65 +  #R.26 UI consists of a vertical titlebar and two clockfaces with text labels.
    3.66 +
    3.67    SOFTWARE SYSTEM ATTRIBUTES
    3.68  
    3.69    OTHER REQUIREMENTS