|
thank you, quite right, that's what you get for doing C&P too much :-)
The manifest fix as well as a fix for this bug should now be in the freshly-updated files.
Sooner or later I should upload it to github or Google Code, I think. That will probably happen the coming weekend. I'd like to include some puzzles from the start and maybe link to a suitable pseudo-firmware-update file for including (or even better: appending to) the keystore. Also, a menu item for jumping to a specific puzzle within the current database would be handy, too. And in the longer run, it would be nice if the Kindlet remembers all solutions already done so you have proper state for all puzzles within a certain database. That would be database- and puzzle specific state storage. In the much longer run, some puzzle generators could be included. Maybe some open source code could be re-used for that.
PS: I would be very fond of a public "experimental" developer.keystore that includes all currently known developer keystores and brings the possibility (by including the private key and publishing its password, such as has been done by the kapp-demo-kindlet author) to sign further software. That way we could have _one_ main entry point for users whishing to run custom, non-KDK (i.e. inofficially) built Kindlets.
|