This forum is for Titan developers (there are so many :)
Any issues regarding the future of Titan should be discussed here.
For instance, I have been thinking about changing the internal structure of Titan, so all the handlers are written on pure C and implemented as plain functions, not object-oriented.
This may seem a step backwards, but it lets pure C programmers use Titan, and generally makes it more accesible. The Image/Anim interface would still be object-oriented, and the API wouldn't change.
This also allows people to use just one handler, at the moment you can comment out handlers, but there is still some overhead involved. this way, just the pcx.cpp and pcx.h files (for example) would be needed. this would allow Titan to be used for 64k intros. Although there is still unnecesary overhead here. Maybe Titan should have extra #defines, such as USE_24_BIT or USE_COMPRESSION that could make handlers even more slimline.
Anyway, any more ideas?
Ideas for examples, new handlers, new types of handler (sound, 3d, etc), new interfaces (i.e. other than OpenPTC)
Until next time...
Dan (_danbrown_@yahoo.com)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
This forum is for Titan developers (there are so many :)
Any issues regarding the future of Titan should be discussed here.
For instance, I have been thinking about changing the internal structure of Titan, so all the handlers are written on pure C and implemented as plain functions, not object-oriented.
This may seem a step backwards, but it lets pure C programmers use Titan, and generally makes it more accesible. The Image/Anim interface would still be object-oriented, and the API wouldn't change.
This also allows people to use just one handler, at the moment you can comment out handlers, but there is still some overhead involved. this way, just the pcx.cpp and pcx.h files (for example) would be needed. this would allow Titan to be used for 64k intros. Although there is still unnecesary overhead here. Maybe Titan should have extra #defines, such as USE_24_BIT or USE_COMPRESSION that could make handlers even more slimline.
Anyway, any more ideas?
Ideas for examples, new handlers, new types of handler (sound, 3d, etc), new interfaces (i.e. other than OpenPTC)
Until next time...
Dan (_danbrown_@yahoo.com)