[Kde-games-devel] Re: Review Request: new libkdegames class KGameBasicWindow to replace KXmlGuiWindow on mobile formfactors

[Aurélien Gâteau]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://svn.reviewboard.kde.org/r/6744/#review10328
-----------------------------------------------------------


I like the idea, but I am not sure about the current look. I would suggest the following:
- Flush the hierarchy buttons to the right (by hierarchy buttons I mean buttons like "Help" or "Settings")
- Instead of adding a "Back" button introduce a "Game" or "Main" hierarchy button which would be the first hierarchy button

The toolbars would thus look like this:

+------------------------------ KDiamond ---------------------------------------+
| New   Show high score   Pause   Hint           [*Game*] [ Settings ] [ Help ] |

+------------------------------ KDiamond ---------------------------------------+
| Configure notifications   Configure KDiamond   [ Game ] [*Settings*] [ Help ] |

+------------------------------ KDiamond ---------------------------------------+
| KDiamond handbook   What's this | Report bug > [ Game ] [ Settings ] [*Help*] |


I believe it would be less surprising because the right part of the toolbar
does not move, making it easier to go back and forth.


- Aurélien


On July 22, 2011, 9:04 p.m., Stefan Majewsky wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://svn.reviewboard.kde.org/r/6744/
> -----------------------------------------------------------
> 
> (Updated July 22, 2011, 9:04 p.m.)
> 
> 
> Review request for KDE Games and usability.
> 
> 
> Summary
> -------
> 
> General outline: Many games present only a small set of menuitems and toolbar actions to the user. Even on mobile form factors, all relevant actions can in many cases easily fit in the toolbar, thus removing the need for the (touch-unfriendly) and redundant menubar. On the implementation side, it would be beneficial to replace KXmlGuiWindow, which provides important features to desktop apps, but overcomplicates the problem for apps as simple as most games.
> 
> Solution: The new KGameBasicWindow class provides a hard-coded toolbar arrangement, in which only one toolbar is created at the top of the window. The most relevant actions are placed here directly, like one expects for a toolbar. Less used actions (like those commonly found in the "Settings" and "Help" menu) can be placed in a hierarchy, but only one level of the hierarchy is made visible at once in the toolbar.
> 
> For example, if the user wants to open the handbook, he finds the "Help" button on the toolbar. Upon clicking it, the toolbar changes and displays all actions in the "Help" group (plus a "Back" button). After selecting the "Handbook" action (and thus opening the handbook), the toolbar automatically returns to its default setup and presents the "important" actions again.
> 
> Implementation: KGameBasicWindow is a new class in libkdegames. Besides this new class, the only change is in KGameDifficulty, whose init() function may now take not only KXmlGuiWindows, but also KGameBasicWindows. This change is trivial because KGameBasicWindow provides an action collection, too. The build of KGameBasicWindow is toggled by the CMake flag "-DKDEGAMESMOBILE=ON", which is "OFF" by default (for all desktop users).
> 
> What's missing? The standard dialog for editing shortcuts could be made available, I do not consider this top priority because keyboard shortcuts are not that relevant on mobile formfactors.
> 
> 
> Diffs
> -----
> 
>   /trunk/KDE/kdegames/CMakeLists.txt 1242082 
>   /trunk/KDE/kdegames/kdiamond/src/CMakeLists.txt 1242082 
>   /trunk/KDE/kdegames/kdiamond/src/mainwindow.h 1242082 
>   /trunk/KDE/kdegames/kdiamond/src/mainwindow.cpp 1242082 
>   /trunk/KDE/kdegames/libkdegames/CMakeLists.txt 1242082 
>   /trunk/KDE/kdegames/libkdegames/includes/CMakeLists.txt 1242082 
>   /trunk/KDE/kdegames/libkdegames/includes/KGameBasicWindow PRE-CREATION 
>   /trunk/KDE/kdegames/libkdegames/kgamebasicwindow.h PRE-CREATION 
>   /trunk/KDE/kdegames/libkdegames/kgamebasicwindow.cpp PRE-CREATION 
>   /trunk/KDE/kdegames/libkdegames/kgamedifficulty.h 1242082 
>   /trunk/KDE/kdegames/libkdegames/kgamedifficulty.cpp 1242082 
> 
> Diff: http://svn.reviewboard.kde.org/r/6744/diff
> 
> 
> Testing
> -------
> 
> As usual, my guinea pig is KDiamond. The needed changes are included in this patch. Everything works fine here. Patch has also been tested on a WeTab tablet (with ToolBarPosition=bottom) and got positive feedback from users.
> 
> 
> Screenshots
> -----------
> 
> Side-by-side comparison of KXmlGuiWindow (back) and KGameBasicWindow (front) for KDiamond (not in screenshot: KActionMenu behind "New" button is now automatically assimilated into the nested toolbar paradigm)
>   http://svn.reviewboard.kde.org/r/6744/s/616/
> Overview of available toolbar states for KDiamond: main category, Settings subcategory, Help subcategory (not in screenshot: nested toolbar behind KActionMenu has replaced popup menu)
>   http://svn.reviewboard.kde.org/r/6744/s/617/
> 
> 
> Thanks,
> 
> Stefan
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-games-devel/attachments/20110723/49280b1a/attachment-0001.htm