Fascinating. An interesting concept.
I am going to assume that, the addition of the "spritesheet" data stored within the main program itself, could possibly reduce time in "reading" the sheet.
I am however left with two questions.
1. Is there an overall saving of disc space by having the data stored withing the main program? ie: Core program + external datasheet or Combined.
2. If the user wanted to edit a sprite, just how could that be done, without an "external" file?
Do not misunderstand. I do not oppose the use of such a program. This is an interesting concept. I would be understandably curious, at some point in time, to see an application or game created by using this method. This program is quite good. I look forward to witnessing its progress.
Well done.
J
I am going to assume that, the addition of the "spritesheet" data stored within the main program itself, could possibly reduce time in "reading" the sheet.
I am however left with two questions.
1. Is there an overall saving of disc space by having the data stored withing the main program? ie: Core program + external datasheet or Combined.
2. If the user wanted to edit a sprite, just how could that be done, without an "external" file?
Do not misunderstand. I do not oppose the use of such a program. This is an interesting concept. I would be understandably curious, at some point in time, to see an application or game created by using this method. This program is quite good. I look forward to witnessing its progress.
Well done.
J
May your journey be free of incident. Live long and prosper.