chess would be just amazing! I love chess and I play regularly, but playing against the camera would be (speachless)....
just counted the rough size of sokoban & reversi: about 1800 lines of code. thats alot, more than most of any others modules's sources of chdk. in my guess, games will play a really small tiny role in future releases of chdk, and i'm pretty sure at least sokoban will be deleted from trunk soon because of lack of memory (it's level database is huge).
GrAnd....But it can be at least packed or separated to an external file.
Ah ! This has turned into an interesting and fundamental discussion - reminds me of computer history, with fixed, non-expandable RAM ...QuoteGrAnd....But it can be at least packed or separated to an external file.That will provide some 'breathing space' for the memory load, but what about the future ? As more and more people comeup with usefull and/or nice additions, problems will most likely increase.It seems inevitable in the long run, that some mechanism must be implemented to load executable code dynamically;that would require heavy duty ARM assembly coding (just guessing - far beyond my reach anyway).In a simpler approach, games and/or other non-photo related functions could be integrated into a stripped CHDK core, if necessary (memorywise) on a per game/function basis.The stripped core would contain only the boot and the gui functions (that is, all photo related stuff stripped out). The main 'photo CHDK' would then be able to boot straight into each of these alternative bins/firs.As a beneficial side effect, you could of course also boot into other CHDK versions/configurations.wim