[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] usage of wind_calc()



søn, 26,.06.2005 kl. 00.51 +0200, skrev Henk Robbers:
> Martin Tarenskeen wrote:
> > 
> > Hi,
> > 
> > What's the point I want to make? I really like the way XaAES is the way 
> > it is. I want an XaAES that is light, stable, and fast. If you want to 
> > add new features - like theme support and even the possibility to change 
> > themes on the fly - go ahead. I don't want to spoil your fun. But please 
> > please be careful. Don't introduce (too many) new bugs, keep things 
> > compatible with older apps that work fine now, and don't create an 
> > oversized XaAES that will use too much processor time and memory on 
> > original Atari machines. (Same story for the FreeMiNT kernel, but that 
> > is not what this thread is about).
> > 
> 
> Very nice and wise words.
> 
> It is my recommendation to #if anything that goes beyond N.AES
> functionality.
> 
> XaAES will come in 2 flavours:
> 1: N.AES compatible. A version that will not grow further. (XaAES)
> 2: A version that may grow and become as powerfull as the developers
>     are willing to make it. (X.AES)
> 
> No developers fun will be spoiled.
> People with older hardware can keep using a very good, fast and fully
> maintained AES
> 
> Needless to say that the 2 flavours are produced from the same
> source tree. Both fully subject to bugfixing and improvements.

 I do not have time to maintain two flavours, so this person is not
gonna be me. N.AES compatibility will ofcourse be maintained. But if one
flavour is going nowhere while the other evolves, I'll be the one
working ONLY on the one that evolves. I think that if this is what is
preferred, we should split the development into two different branches
for this purpose, because otherwise I fear readability/layout of things
quicly becomes #ifdef'ed to death. Furthermore, I do not see the point
of this, as if one dont want more than what N.AES provides, just use
N.AES.


 Best Regards
Odd Skancke