Feature list : Map Viewing
From Sokoban Wiki
Revision as of 13:54, 2 August 2009
[show all]
2. Game Play |
Map Viewing
Map Viewing | Map Viewing
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
level browser with preview | yes one level at a time | no | yes block graphic miniatures of all loaded levels | no | yes block graphic miniatures of all levels in a collection (customizable miniature size) | level browser with preview | no | yes one level at a time | no | no | |||||||||||||||||||||||||||||||||||||||||||||
resize skin to fit window | yes always | no | yesskin dependent | yes always | yes flaw: Windows has 2 font settings, small (default) and large, and this only works for small fonts | resize skin to fit window | no | yes always | no | yes | |||||||||||||||||||||||||||||||||||||||||||||
resize window to fit map | unnecessary map always fits in window | yesmanually/ automatically depending on skin | no | unnecessary map always fits in window | yes flaw: Windows has 2 font settings, small (default) and large, and this only works for small fonts | resize window to fit map | yes optional | unnecessary handheld applications fill device screen | yes always | no | |||||||||||||||||||||||||||||||||||||||||||||
levels larger than window: scrolling | unnecessary | yes via : mouse: Ctrl + arrows; keyboard: Ctrl + numeric keypad | no | unnecessary | yes via scrollbars. Windows has 2 font settings, small (default) and large, and this only works for small fonts | levels larger than window: scrolling | yes via scrollbars with an option to autofollow (move scrollbars automatically) | yes via scrollbars but only for puzzles so large that graphics would become impossibly small on handheld device screen | unnecessary | unnecessary | |||||||||||||||||||||||||||||||||||||||||||||
one-click browse levels | yes previous, next in all level files in current level directory, with wrap-around | yes previous, next, first, last in currently loaded levels, without wrap-around | yes previous, next in currently loaded levels, without wrap-around | yes previous, next in current collection, with wrap-around | yes previous, next in all loaded level files, with wrap-around | one-click browse levels | yes implementation: keyboard shortcuts for: previous, next, first, last (in current collection, without wrap-around) | yes previous, next in all level files in current collection, without wrap-around | yes next, without wrap-around | yes previous, next in current collection, without wrap-around | |||||||||||||||||||||||||||||||||||||||||||||
one-click browse files | no | yes previous, next additionally, menu and keyboard shortcuts: previous, next, first, last | no | no | yes drop-down list with all level collections | one-click browse files | yes drop-down list with visited level collections | no | no | yes file-list readily available | |||||||||||||||||||||||||||||||||||||||||||||
search for unsolved level | yes previous, next in all level files in current level directory, with wrap-around | yes previous, next, random in currently loaded levels, without wrap-around | yes previous, next, random in currently loaded levels, without wrap-around | yes previous, next in current collection, with wrap-around | yes partial implementation: auto-advance after having solved a level finds an unsolved level if settings is "unsolved levels only" | search for unsolved level | yes previous, next in current collection, without wrap-around | yes previous, next in all level files in current collection, without wrap-around | no | yes previous, next in current collection, without wrap-around flaw: does not restrict the search to the player's own solutions | |||||||||||||||||||||||||||||||||||||||||||||
rotate and mirror level-map | yes persistent, with reset option savegames and solutions are automatically synchronized with current transformation | yes session, with reset optionsavegames and solutions are automatically synchronized with current transformation | yes session (partial implementation: use editor) savegames and solutions are specific to each transformation | yes session, with reset option savegames and solutions are automatically synchronized with current transformation | yes ?Will somebody with a full version check if it is session, with reset option or persistent, with reset option additionally check if savegames and solutions are automatically synchronized with current transformation or savegames and solutions are specific to each transformation | rotate and mirror level-map | yes session, with reset option savegames and solutions are automatically synchronized with current transformation | no | no | yes (session, with reset option) savegames and solutions are automatically synchronized with current transformation | |||||||||||||||||||||||||||||||||||||||||||||
multiple windows, one per level | no | no | no | no | yesvia tabs. multiple levels can be opened in separate tabs. | multiple windows, one per level | no | no | yes | no | |||||||||||||||||||||||||||||||||||||||||||||
multiple views of a level | yes | no | no | no | no | multiple views of a level | no | no | no | no | |||||||||||||||||||||||||||||||||||||||||||||
|
Information
Level scrolling
levels larger than window: scrolling
levels larger than window: scrollbars
Briefly, the first line is there to give a program the chance to tell that it has a scroll feature, and the second line is there to tell if the program does it the right way - with scrollbars.
Since the first graphical user interfaces emerged, scrollbars have been used for depicting the situation where a document doesn't fit in the window, so the user can rightfully expect to find that logic (or something equally user-friendly) in a Sokoban program as well.
Therefore, it's embarrasing for programs that requires scrolling if they don't have scrollbars or something equivalent. The line "levels larger than window: scrollbars" must be listed so readers can see this major design flaw, and so new programmers are reminded that they definitely should do better.
On the other hand, Sokofan deserves credits for at least having a scroll feature, despite the fact that it's not done the right way with scrollbars. The user doesn't get any visible clue that the board is bigger than the window, and the user must read the instructions to find the keyboard and mouse/key combinations that controls the scrolling.
So the line "levels larger than window: scrolling" is there to give Sokofan a chance to tell that it indeed has a scroll feature, even though it's not as user-friendly as the user rightfully can expect from a good Sokoban clone.
-bd
SokRFI - Sokoban Requests for Implementation
Map Viewing : SokRFI - Sokoban Requests for Implementation | |||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Feature | Description | ||||||||||||||||||||||||||||||||||||||||||||||||
full screen | Implemented in SokoStation | ||||||||||||||||||||||||||||||||||||||||||||||||
multiple views of a level | A user often works on several alternative paths at the same time. It would be a great help if each of them was fully visible. For instance, multiple views are beneficial during the process of optimizing existing solutions. This feature is implemented in Sokoban YASC. | ||||||||||||||||||||||||||||||||||||||||||||||||
show/hide redundant walls | It fills jagged wall edges, fills unused "tubes", removes redundant walls, unused boxes, and unused goals. Implemented in Sokoban YASC as 'Normalize board' (edit mode). |