That's probably a good, simple approach. If I were doing it, I'd be tempted to use the function loop and to use Types to hold whether each character is a 1 or 0, its cycle rate, and its current alpha/color level. But you mentioned that you prefer simple (and big <g>) code. So if it works, and you enjoy writing it, then that's how you should proceed.
I think that programming is sort of personal that way. Sometimes I'll look at examples written by others and realize that the approaches used are supposedly more efficient or "standard" than mine, but that they're not what I'd be comfortable with. I'm a big believer in making code human-readable first (whatever that means to each individual programmer) and machine-efficient second. I only optimize for speed in case some area is too slow for my target machine. So I think that you should program whatever way makes the most sense to you.
Good luck, and have fun!
I think that programming is sort of personal that way. Sometimes I'll look at examples written by others and realize that the approaches used are supposedly more efficient or "standard" than mine, but that they're not what I'd be comfortable with. I'm a big believer in making code human-readable first (whatever that means to each individual programmer) and machine-efficient second. I only optimize for speed in case some area is too slow for my target machine. So I think that you should program whatever way makes the most sense to you.
Good luck, and have fun!