[Kde-games-devel] kbattleship and welcome screen

[Eugene Trounev]

Well, I don't really understand what the problem is here.
The welcome screen the way it is now is very good, except for a few little
problems.
First - when player selects "You" button and system asks for a
nickname, it's hard to
imagine how to submit it. I spent a few minutes trying to figure that
one out :) before realised I had to press enter there.
It's not very intuitive since up to this point the entire control is mouse
driven. The second problem
is the absence of any indication that the game has started and player
has to place the ships on the field
(some kind of indicator telling what to do and how to do that would be nice
at this point).
As for the network settings - I don't think creating a custom GUI would be
wise. Actually a regular QT4/KDE4 driven and color managed pop
up settings window would be quite sufficient here. That's what I would
expect as a player. And no it does not create any inconsistency. It
comes there logically and naturally.
Hope I'm being helpful.

it-s


On 6/12/07, Paolo Capriotti <p.capriotti at gmail.com> wrote:
>
> After a number of failed attempts and experiment, I'm starting to be a bit
> dubious about the whole 'welcome screen' thing [1] [2].
> The idea is good, in principle: after the game has started, the user
> should be
> given all the information on the existing types of play. A nice welcome
> screen, integrated with the game graphics, just seems like the right thing
> to
> display.
> However, many games (including kbattleship) require to user to enter
> additional information before the game can actually be started. For
> example,
> in kbattleship, when playing over the network, one has to pick a nickname,
> and enter the tcp connection parameters.
> All these additional things tend to complicate the welcome screen
> interface,
> pushing it to the point where normal gui controls are needed, thus
> breaking
> the integration with the game graphics, making flicker-free animations
> practically impossible and requiring a lot of programming effort, which is
> essentially wheel reinvention in many aspects (resizing, layouting,
> handling
> mouse events...).
> Plus, the controls are inconsistent with the kde style, and do not use
> system
> colors. I agree that this may not be a problem for a game, but in this
> particular case, we're not strictly dealing with a game, but with
> the 'initial configuration' needed for a game to be started, which is imho
> quite a different context, and I think that in this case fancy graphics,
> albeit nice, probably get in the way.
> On a side note, I've tried a particular approach (double menu, see the
> screenshot in [2]) while integrating KWelcomeScreen in kbattleship, and it
> resulted in a gross failure: even one of our game developers had troubles
> figuring out how to start a network game!
> That's not the main point of my rambling, though. The interface can be
> simplified, and we already started working on this, but imho even a
> simplified interface will have the flaws I've tried to describe here.
> My proposal is to forget about integrated welcome screens, at least for
> kbattleship, and to add a normal dialog acting as a welcome screen (like
> ksudoku, iirc).
> I hope to hear some comments about this, so that I can finally decide an
> approach and follow it. I've been experimenting with this menu for quite
> some
> time, and I must say I'm a bit tired. I'd like to have all this stuff
> settled
> down, so I can move on to more interesting things.
>
> Paolo
>
> [1] http://johann.pwsp.net/2007/04/09/a-new-game-starter/
> [2] http://commit-digest.org/issues/2007-04-15/
> _______________________________________________
> kde-games-devel mailing list
> kde-games-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kde-games-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-games-devel/attachments/20070612/cc3aafd0/attachment.html