Not Logged in.
Login | Register
The spriteZ factory v1.0

File Information
Name: The spriteZ factory v1.0
File: the spritez
Filesize: 86 kB
Downloads: 261
Date added: Aug 28, 2006
Platform: TI-83/+/SE
Language: Basic
File Type: Program
Category: Graphics
Last modified: Aug 28, 2006
TI-83 BASIC Programs
TI-83+/SE BASIC Programs
TI-83/+/SE BASIC Programs
TI-84+/SE BASIC Programs

Shell: None
Rating: 0/10 based on 0 votes.
Rate this file:
Bad 10 Good
File Website:
Author(s): 4ce_labs

File Description:  make sprites for your basic programs/games.

not just 8x8 but any size, you can even make them move!

you can do it all, even with low RAM.

ss     ss

I hope 4ce_labs updates it...
Of 1 person, 1 found this review helpful.
Review by: haveacalc Reviewed on: August 28, 2006 at 06:41:12 PM
Graphics/Interface: 4/10 The opening screen put my eyes in a bad mood.
Playability/Usability: 7/10 It does what it says it will.
Replay Value/Reuse Value: 6/10 There are better ways to go about it.
Controls/Interface: 8/10 Key-choice was very good.
Overall Value: 6/10 I gotta say I'd rather make my own version.
"The spriteZ factory" has good potential. Certain things could be cleared up to make this program worthwile, though.
For starters, the code is completely unoptimized. Lots of space could be saved there. The second thing would be how the output string is compiled. Unnecessary zeroes occur every time coordinates were stored with the x or y value being under 10 (more bytes to be saved). While on the topic of memory, I'll mention that Delvar took a long vacation during this program and never returned. Pixel-activating was very sluggish. If 4ce_labs doesn't mind me saying so, things would work better if coordinates were quickly stored in list elements every time the user pressed [2nd]. Then, the string could be compiled entirely at the end without slowing down the program while it was still in the loop. With the string,"int(J/10)" could be shortened to "int(.1J)". One thing that definitely needs to be fixed is that the pixel-cursor can go out of the bounds of the screen, causing an error. Also, when the program finishes, window and graph settings are NOT restored to what they were before it ran.
The interface needed some work, too. I can't help but wonder why around half the screen was cut from use. On a lighter note, the pixel-cursor ran very smoothly and evenly when arrow keys were held down.
In conclusion, this program can turn into a very useful tool, but needs some work before it's as good as it CAN be, which is very good. I hope in all sincerity that this review will be taken as constructive criticism and will help the author to see areas which need improvement.

[Review This File]

Portal | My Account | Register | Lost Password or Username | TOS | Disclaimer | Help | Site Search | File Archives Copyright © 2002-2019