Re: [dink-develop] Sequence file format

[Andrew <ae...@co...>]

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
>