Calling For Ideas: dwProgressBar and Typewriter
Just wanted to throws this out there quick. I'm looking for ideas from you on how to enhance my dwProgressBar and Typewriter classes. I appreciated the compliments but I know there's always room for improvement. I need your ideas!! Here's what I have so far:
- "Stepping Mode" -- Instead of constant set() calls, why not step a specified number each time?
- More examples
- "Character Deletion" -- Everyone makes typos, right? Now the typewriter can go backward!
- "Character Delay Variation" -- Now the pace at which the typewriter displays characters can vary.
Can you think of anything else? Please let me know!
I work with an awesome cast of developers at Mozilla, and one of them in Daniel Buchner. Daniel's shared with me an awesome strategy for detecting when nodes have been injected into a parent node without using the deprecated DOM Events API.
Kids these days, I tell ya. All they care about is the technology. The video games. The bottled water. Oh, and the texting, always the texting. Back in my day, all we had was...OK, I had all of these things too. But I still don't get...
Note: All credit for Fx.Explode goes to Jan Kassens.
One of the awesome pieces of code in MooTools Core Developer Jan Kassens' sandbox is his Fx.Explode functionality. When you click on any of the designated Fx.Explode elements, the elements "explode" off of the...