Avoiding 'big and complicated' in tRev
If you have not read the Andy Ihnatko (image above) review of Posterous in the Chicago Sun Times, it's worth a read.
Here's the part that pertains to tRev:
It is my firm resolution to develop tRev in such a way that we do NOT make it too big and complicated.
I'm walking my talk with tomorrow's new feature called the decoder. It's simple, performs fast, and goes beyond traditional debugging by doing less.
- The tRev Decoder can be used by people who don't know how to use a debugger. It's simpler that any debugger I've ever used. I'm reluctant to refer to it as a form of debugging.
- Decoder doesn't interfere with Revolution's execution of scripts. It will NOT lock-up Rev. It's dirt simple. New versions of Rev cannot hose it.
- The tRev Decoder is entirely modeless...no more dreaded, modal debugger state. You won't have to hold your breath anymore when you click a step button.
- Decoder lets you step backward or forward to designated places in your code to view its full context at that point in its execution. See what was in each variable, parameter or item delimiter at that exact point in time.
The Decoder deconstructs your code according to your instructions and saves it in a local database. Now, you can look at portions of your code's execution content-and-context (that you designated!) at any time.
Because Decoder's data is stored to a database, you can use it to deconstruct your code the next day or next week. Your Decoder data will be there waiting for you until you delete it.
You should click below to...
Posted by Jerry Daniels
