Re: [dink-develop] Sequence file format

[Francis W. <dea...@va...>]

That's rather over-complicated, isn't it? Plus, we're not actually naming
sequences, etc. - we're sticking with the number/frame referencing system,
as it's clearly the best (especially for things like idle/attack/walk
sequences). Anyway, I think the current dink.ini format is okay...

What I was talking about is where things like which frame of a sequence are
'special' and if so, 'how' special (what their number is for the 'special'
parameter for that frame).

- Francis

----- Original Message -----
From: "Andrew" <ae...@co...>
To: <din...@li...>
Sent: Tuesday, March 09, 2004 6:30 AM
Subject: Re: [dink-develop] Sequence file format


> I would assume that's what he meant.
>
> I'm going for a sorta-human-readable format:
>
> // User Definable objects
> Pack LooseFiles;
> Pack Trees /path/to/pack.wgp;
> Pack Crap /path/to/crap/pack.wgp /path/to/another/pack.wgp;
>
> LooseFiles:1:1 /path/to/graphics/file.png [parameters here];
> LooseFiles:1:2 /path/to/other/graphics/files.png [parameters here];
> ...
> (I think for the pack, you could either include a configure file for the
> first file, or define them yourself)
> [If the config file is not included.]
> Trees:1:1 [parameters];
> Trees:1:2 [parameters];
>
> [If the config file is included, you don't do anything except reference
it.]
> Trees:: ;
> ...
> Crap:1:1 [parameters];
> Crap:1:2 [parameters];
> Crap:2:1 [parameters];
>
> The format is:
> Object : Pack Definition : Number of file in pack (order of file stored
> in tar);
>
> Where pack definition is, take Pack Crap, 1 is /path/to/crap/pack.wgp
> and 2 is /path/to/another/pack.wgp.
>
> --Andrew
>
>
> Dan Walma wrote:
>
> > Uh... why not store it into your dink.ini equivalent file, or wherever
> > hard boxes are defined?
> >
> > Francis Woodhouse wrote:
> >
> >> Okay, I've been digging into all kinds of sequence-related things,
> >> having to suffer the unfortunate pain that is understanding Seth's
> >> godawful code. I was doing some attack stuff today and rememebered
> >> that (obviously) sequences need to store more info than just their
> >> frames (good example being whether a frame's 'special' is set to 1,
> >> meaning that we should smack our bitches up [attack other sprites...]
> >> when that frame is visible). So, we need a format for file's that'll
> >> describe this 'anciliary data' associated with each sequence.
> >>
> >> Any ideas for the format? Should we go for human-readable (caveat:
> >> larger file sizes) or binary-only (caveat: not human-readable,
> >> requires a program to edit in any way)?
> >>
> >> - Francis
> >
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> dink-develop mailing list
> din...@li...
> https://lists.sourceforge.net/lists/listinfo/dink-develop
>