Re: [dink-develop] Suggestions

[Sylvain B. <syl...@li...>]

> I'm the one who asked Seth if I could zip up the default install of 
> dinksmallwood106.exe into dinksmallwood106.zip, and he agreed.
> 
> I'm afraid I have absolutely no idea what you mean, by bz2 and 7z, so 
> I have no purposeful comments on that issue.

We should ask Seth the permission to publish a 1.07 updated version - 
it seems that Nerkus experienced problems because of that. Maybe you 
can update the file without asking him. We may also use the .d 
"decompiler" to update "source.zip" with Seth's bugfixed scripts.

Both bz2 and 7z are compression formats. I refered to Shawn Betts' 
personnal copy of the Dink data he uploaded on his webpage. By the way, 
the fact we cannot repackage the media without asking will have to be 
worked on. Arnaud mentioned Debian distribution, and I am quite sure 
they will not agree to put the data on a CD with such a constraint 
indeed.

> I thought that Merlin's code rewrite was being written with the 
> graphics, sound, etc. calls being abstracted, so porting to a 
> different platform would be relatively easy.  I could be wrong.

I think that the current code uses SDL directly. jameson's advice was 
to be library independant, based on the fact he had to change his 
graphical library over the year in his projects - SDL may not be 
eternal. My comment on portability issue is wrong indeed, since SDL 
should took care of that entirely - though I am not an expert, maybe 
console platforms may need additional specific code. jameson's article 
is there: http://linux.oreillynet.com/lpt/a/3242

-- 
Beuc