[qub] Re: I just got a Wicked idea...

[Stephan B. <st...@wa...>]

What I completely got off track of saying was:

How feasible/usable does it sound to store the GPiece XML file names
inside the savegame INSTEAD of the GPieces and such?

On Wed, 14 Jun 2000, Stephan Beal wrote:
> Okay, you can now double-click on an XML file which a single GPiece
> node and load that piece, completely intact. Cool. But here's what I
> wanna do:
> 
> Hide the graphics, and just show users the piece files. It's cleaner
> (they don't see the back sides graphics, and we don't have to implement
> that (10-minute-job, I know) filter in DirView).
> Then the graphics can be called whatever, and the pieces can have real
> names and hoverhelp like "This is a GEV Hovertank, MotherFucker!",
> instead of "gev" and "gev-disabled".
> 
> Using xml pieces, instead of (well, as an option) just allowing
> arbitrary graphics to be clicked, the gamesets can be more organized,
> and have nice names for the files, without requiring two files (for
> sides of the piece, as one would "normally" have).
> 
> Ya know, if we make the GPiece's use QMovies instead of QPixmaps, we
> could make them use animated gifs :). But it'd be a pain in the ass to
> do, I think, without breaking many GPiece internals apart.
> 
> I also need to add support for a file containing more pieces (in some
> kind of semi-useless container node, which might store settings like
> "ignore piece positions, and place them at the PlaceMarker instead?").
> This is coming.
> 
> This is not checked in yet, but I'll get to that tonight before I hit
> the hay.
> 
> ----- Stephan Beal
> http://www.wanderinghorse.net
> http://qub.sourceforge.net
> st...@wa...
> ste...@ei...
-- 
----- Stephan Beal
http://www.wanderinghorse.net
http://qub.sourceforge.net
st...@wa...
ste...@ei...