Re: Aisleriot ideas
- From: Christian Persch <chpe gnome org>
- To: "Timothy S. Nelson" <wayland wayland id au>
- Cc: games-list gnome org
- Subject: Re: Aisleriot ideas
- Date: Wed, 8 Dec 2010 23:40:17 +0100
Hi;
Am Wed, 8 Dec 2010 11:34:18 +1100 (EST)
schrieb "Timothy S. Nelson" <wayland wayland id au>:
> On Wed, 8 Dec 2010, Christian Persch wrote:
> > Am Mon, 6 Dec 2010 13:40:10 +1100 (EST)
> > schrieb "Timothy S. Nelson" <wayland wayland id au>:
> >> B. Have an XML file for data associated with each game
> > I'm not sure I'd choose xml for that description; a simple .ini
> > style keyfile format would probably be enough.
If we also want to include this data in the help files (e.g. as a
paragraph describing the games), then it would probably need to be xml.
Anyway, that need to be worked out by whoever will implement this :)
> Fine by me. I just figured there are probably already lots
> of XML processing libraries out there already.
The data itself should probably be compiled into a binary gvariant blob
at build time for use in the programme, instead of cluttering the file
system with yet more files.
> >> It would also be useful if there were a Scheme function
> >> that could be called, so that the developers of games could access
> >> the XML data associated with their game.
> >
> > The game itself doesn't need access to that data, as far as I can
> > see? It would be only for use in the UI.
>
> I was thinking of the redeals.
They're not configurable (well, some games have variants with unlimited
redeals), but still I think that data would be descriptive, and
separate from the actual code. Both need to be kept in sync, obviously.
> >> Might it be useful to have the "Aisleriot Solitaire" item
> >> on the Gnome menus be a submenu instead, and then list all the
> >> Solitaire games (categorised, of course) directly on the Gnome
> >> menus?
> >
> > Not opposed to that, but not really convinced either. I think you
> > should put that idea to the gnome-shell design team, since these
> > menus are their area. (It'll be easy to implement for us, in the
> > event that they like the idea.)
>
> I'm not particularly convinced either way either -- just
> thought I'd mention it :).
Still, proposing that to the shell team wouldn't hurt; all they can say
is 'no' :)
> I'm probably not the best UI designer. But as a not-very-UI
> designer, I'd tend to approach it from an incremental point of view
> -- put out something, and improve as we go.
Well, since you're not a C coder, helping with the data, and the design
in conjunction with the design / UI team seems the best ways to
contribute :) Without a design, just starting to code would probably
just lead to bad UI.
Regards,
Christian
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]